[konsole] [Bug 370231] New: dynamic line wrap not working when window is resized
https://bugs.kde.org/show_bug.cgi?id=370231 Bug ID: 370231 Summary: dynamic line wrap not working when window is resized Product: konsole Version: 16.04.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: hon...@hotmail.com In konsole version 15.12.3 (Kubuntu 16.04, Linux (x86_64) release 4.4.0-38-generic) the dynamic line wrap is not working when the window is resized. Additionally is I copy paste a wrapped line it will introduce an enter in the wrapped line. This behavior was not present in konsole in Kubuntu 14.04. Please add option to restore to previous dynamic line wrapping with the option when line is selected is not broken in two lines. Reproducible: Always Steps to Reproduce: A) 1. Open konsole 2. Write a line longer than the size of the window 3. Select and Copy whole line 4. Paste in a text editor 5. Line will be broken in two lines B) 6. Repeat steps 1 to 2 7. Resize windows width Actual Results: A) Line will be broken in two lines B) Line will not be re-wrapped to fit the new window width Expected Results: A) Wrapped copied Line should be a single line not two B) Line should be re-wrapped to fit the new window width -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370231] dynamic line wrap not working when window is resized
https://bugs.kde.org/show_bug.cgi?id=370231 Pablo changed: What|Removed |Added CC||hon...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370231] dynamic line wrap not working when window is resized
https://bugs.kde.org/show_bug.cgi?id=370231 --- Comment #1 from Pablo --- Kubuntu 16.04 was upgraded from 14.04 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369299] krunner display big list elements
https://bugs.kde.org/show_bug.cgi?id=369299 Pablo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Pablo --- openSUSE snapshot 20161006 upgraded kde plasma to version 5.8. All seems fine now. I'm closing this bug. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366318] New: No transparency, blur or shadows in plasmashell at startup
https://bugs.kde.org/show_bug.cgi?id=366318 Bug ID: 366318 Summary: No transparency, blur or shadows in plasmashell at startup Product: kwin Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: pablow.1...@gmail.com When login into my session plasmashell taskbar, kickoff menu and krunner have neither transparency with blur nor shadows. "killall plasmashell && plasmashell" from konsole fixes it. Reproducible: Always Steps to Reproduce: 1. Login into a plasma session. Actual Results: Plasmashell apparently has no compositing (other types of windows seems fine, so other effects like "slide" for plasma widgets). Expected Results: Plasmashell panel, kickoff, etc, should have transparency, blur, and shadows. I'm running openSUSE tumbleweed up to date. My system has an AMD Radeon 7750 with opensource mesa drivers. I'll happily provide any needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366318] No transparency, blur or shadows in plasmashell at startup
https://bugs.kde.org/show_bug.cgi?id=366318 --- Comment #1 from Pablo --- Created attachment 100402 --> https://bugs.kde.org/attachment.cgi?id=100402&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366318] No transparency, blur or shadows in plasmashell at startup
https://bugs.kde.org/show_bug.cgi?id=366318 --- Comment #2 from Pablo --- Created attachment 100403 --> https://bugs.kde.org/attachment.cgi?id=100403&action=edit Screenshot of the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366318] No transparency, blur or shadows in plasmashell at startup
https://bugs.kde.org/show_bug.cgi?id=366318 --- Comment #3 from Pablo --- Created attachment 100404 --> https://bugs.kde.org/attachment.cgi?id=100404&action=edit Screenshot after killing and restarting plasmashell -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369299] New: krunner display big list elements
https://bugs.kde.org/show_bug.cgi?id=369299 Bug ID: 369299 Summary: krunner display big list elements Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: pablow.1...@gmail.com After upgrading plasma 5.7.3 --> 5.7.4 on openSUSE (tubleweed) krunner is showing bigger list elements of the search performed. I've tried a new user session and it's the same. Reproducible: Always Steps to Reproduce: 1. Open krunner 2. Hit some key so a search is performed 3. See how the search results are listed, but the height of each element list it's bigger than usual (plasma 5.7.3). Actual Results: krunner search results are presented in a list whose elements are bigger. Expected Results: krunner should present the search results with smaller list elements size. openSUSE tumbleweed, packages up to date (2016-9-24) KDE plasma: 5.7.4 KDE frameworks 5.26.0 Qt: 5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369299] krunner display big list elements
https://bugs.kde.org/show_bug.cgi?id=369299 --- Comment #1 from Pablo --- Created attachment 101262 --> https://bugs.kde.org/attachment.cgi?id=101262&action=edit krunner in 5.7.3 I have managed to "workaround" this (as seen in the screenshot) by setting the "dialogs" icon size in system settings to 22, but all icons in regular windows are affected by this change. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369299] krunner display big list elements
https://bugs.kde.org/show_bug.cgi?id=369299 --- Comment #2 from Pablo --- Created attachment 101263 --> https://bugs.kde.org/attachment.cgi?id=101263&action=edit krunner in 5.7.4 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368665] New: krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or type something)
https://bugs.kde.org/show_bug.cgi?id=368665 Bug ID: 368665 Summary: krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or type something) Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: pablow.1...@gmail.com krunner crash by presing alt+f2 key combination, or by typing something in its textbox when the krunner widget appears. Reproducible: Always Steps to Reproduce: 1. Press Alt+F2 combination key so krunner shows up 2. Start typing something, erase that, type something again. 3. Repeat step 2 till krunner crash itself. Actual Results: krunner crashes when using it. Expected Results: krunner should not crash when using it. Last lines in standard output (I typed "jaja" in the textbox before the crash happened): QuerySYNONYM WILDCARD OR NAjaja) OR NAjaja@1) OR ((SYNONYM WILDCARD OR jaja) OR jaja@1))) QtWebEngine::initialize() must be called from the Qt gui thread. KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 75 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 23 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 24 and type 'Exception', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... radeon: Failed to allocate a buffer: radeon:size : 4096 bytes radeon:alignment : 4096 bytes radeon:domains : 4 theese for lines repeat itself with the same buffer size or 8192 bytes. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)
https://bugs.kde.org/show_bug.cgi?id=368665 Pablo changed: What|Removed |Added Summary|krunner crash: radeon: |krunner crash: radeon: |failed to allocate buffer |failed to allocate buffer |(by just presing alt+f2 or |(by just presing alt+f2 or |type something) |typing something) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)
https://bugs.kde.org/show_bug.cgi?id=368665 --- Comment #1 from Pablo --- Created attachment 101167 --> https://bugs.kde.org/attachment.cgi?id=101167&action=edit krunner crash A short video of krunner crashing when trying to do a simple sum. This crash situation happens always. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)
https://bugs.kde.org/show_bug.cgi?id=368665 --- Comment #2 from Pablo --- Created attachment 101168 --> https://bugs.kde.org/attachment.cgi?id=101168&action=edit The output from konsole -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner
https://bugs.kde.org/show_bug.cgi?id=364342 Pablo changed: What|Removed |Added CC||pablow.1...@gmail.com --- Comment #20 from Pablo --- *** Bug 368665 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)
https://bugs.kde.org/show_bug.cgi?id=368665 Pablo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Pablo --- Sorry for wasting your time. I've found the Bug Report "https://bugs.kde.org/show_bug.cgi?id=364342"; which didn't come up in my first google search. If I disable the Contacts Plugin, krunner won't crash anymore. I'll be waiting the 16.04.2 update. Thanks for your hard work! *** This bug has been marked as a duplicate of bug 364342 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 --- Comment #19 from Pablo --- I'm not seeing this anymore, at least on openSUSE Tumbleweed (plasma 5.7.3, Qt 5.6.1, KDE Frameworks 5.24). Neither on cable nor on wifi (two different PCs). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 --- Comment #21 from Pablo --- Maybe it's another thing. What version of KDE Frameworks and Qt are installed on your system? and what about NetworkManager version? In mine, for instance, are 5.24; 5.6.1 and 1.0.12, respectively. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 360107] New: Crash when removing the batery
https://bugs.kde.org/show_bug.cgi?id=360107 Bug ID: 360107 Summary: Crash when removing the batery Product: kdelibs Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: ystgu...@hotmail.com Application: kded4 (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-38-generic x86_64 Distribution: Linux Mint 17.2 Rafaela -- Information about the crash: - What I was doing when the application crashed: I just removed the battery (with the cord connected) when the crash window appeared on the screen. This is the first time I see that error. -- Backtrace: Application: Servicio de KDE (kded4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6c3dd527c0 (LWP 2605))] Thread 7 (Thread 0x7f6c2206d700 (LWP 2607)): #0 0x7f6c3b5bb12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6c386b9fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6c386ba0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c3c9f47be in QEventDispatcherGlib::processEvents (this=0x7f6c1c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f6c3c9c60af in QEventLoop::processEvents (this=this@entry=0x7f6c2206ce20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6c3c9c63a5 in QEventLoop::exec (this=this@entry=0x7f6c2206ce20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6c3c8c2c5f in QThread::exec (this=) at thread/qthread.cpp:537 #7 0x7f6c3c8c532f in QThreadPrivate::start (arg=0x11cf8f0) at thread/qthread_unix.cpp:349 #8 0x7f6c38d9c182 in start_thread (arg=0x7f6c2206d700) at pthread_create.c:312 #9 0x7f6c3b5c847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f6c14f15700 (LWP 2626)): #0 0x7f6c38d9f7ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x13ef590) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x13ef590) at pthread_mutex_unlock.c:310 #2 0x7f6c386fb9b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c386b9f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6c386ba30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6c1541e336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f6c386def05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6c38d9c182 in start_thread (arg=0x7f6c14f15700) at pthread_create.c:312 #8 0x7f6c3b5c847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f6c0700 (LWP 2627)): #0 0x7f6c386b7459 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6c386b962b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6c386b9f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c386ba0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6c3c9f47be in QEventDispatcherGlib::processEvents (this=0x7f6bf8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7f6c3c9c60af in QEventLoop::processEvents (this=this@entry=0x7f6c0fffede0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6c3c9c63a5 in QEventLoop::exec (this=this@entry=0x7f6c0fffede0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6c3c8c2c5f in QThread::exec (this=) at thread/qthread.cpp:537 #8 0x7f6c1b77c027 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #9 0x7f6c3c8c532f in QThreadPrivate::start (arg=0x12d3b10) at thread/qthread_unix.cpp:349 #10 0x7f6c38d9c182 in start_thread (arg=0x7f6c0700) at pthread_create.c:312 #11 0x7f6c3b5c847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f6c0f7fe700 (LWP 2628)): #0 __libc_enable_asynccancel () at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7f6c3b5bb122 in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x7f6c386b9fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c386ba0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6c3c9f47be in QEventDispatcherGlib::processEvents (this=0x7f6bfc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7f6c3c9c60af in QEventLoop::processEvents (this=this@entry=0x7f6c0f7fde20, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6c3c9c63a5 in QEventLoop::exec (this=this@entry=0x7f6c0f7fde20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6c3c8c2c5f in QThread::exec (this=) at thread/qthread.cpp:537 #8 0x7f6c3c8c532f in QThreadPrivate::start (arg=0x1327940) at thread/qthread_unix.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 Pablo changed: What|Removed |Added CC||pablow.1...@gmail.com --- Comment #11 from Pablo --- Same here. openSUSE tumbleweed KF5 5.21. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 --- Comment #12 from Pablo --- (In reply to Pablo from comment #11) > Same here. openSUSE tumbleweed KF5 5.21. And kubuntu 16.06 live image. KF5 5.18 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 --- Comment #13 from Pablo --- Created attachment 98731 --> https://bugs.kde.org/attachment.cgi?id=98731&action=edit Kubuntu 16.04, plasma 5.5.5, Qt 5.5.1, KDE Frameworks 5.18 Just to picture the behavior. This happens both with wired or wifi conection. It just dissapears for the active conection. -- You are receiving this mail because: You are watching all bug changes.
