[Discover] [Bug 386160] New: Discover Crashes when Clicking on Updates-Available Icon
https://bugs.kde.org/show_bug.cgi?id=386160 Bug ID: 386160 Summary: Discover Crashes when Clicking on Updates-Available Icon Product: Discover Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Application: plasma-discover (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-37-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Clicked on the Updates are available button, got a pop-up dialog saying that 3 updates were available. Clicked on Update. Discover started (window outline visible, but doesn't seem to have painted any contents), then crashed. Using the Ubuntu Backports Landing PPA. Happened a second time when I did the same set of operations. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9269240440 (LWP 15776))] Thread 10 (Thread 0x7f92212d4700 (LWP 15789)): #0 0x7f925f45f5a1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f925f461a0b in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f925f46249b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f925f46268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f926540e0bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f92653b7bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f92651e5f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f92651eac38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f92615c56da in start_thread (arg=0x7f92212d4700) at pthread_create.c:456 #9 0x7f92647eed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7f9221eea700 (LWP 15787)): #0 0x7f92647e2d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f925f462576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f925f462902 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9223ae2476 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f925f489f65 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f92615c56da in start_thread (arg=0x7f9221eea700) at pthread_create.c:456 #6 0x7f92647eed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7f92226eb700 (LWP 15786)): #0 0x7f92647e2d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f925f462576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f925f46268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f925f4626d1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f925f489f65 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f92615c56da in start_thread (arg=0x7f92226eb700) at pthread_create.c:456 #6 0x7f92647eed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7f9234653700 (LWP 15783)): #0 0x7f92615cb510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f92651ebaeb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f92651e49c3 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f92653e59fe in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f92636e2858 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f92637742dd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f92653e5789 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f92636a5176 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f92636a562d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f92653e5789 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9263760e06 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f92637647d3 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f92637651de in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f9263750a31 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7f92653e5789 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f92637242f5 in () at
[kwin] [Bug 385705] New: KWin crash when opening Eric IDE
https://bugs.kde.org/show_bug.cgi?id=385705 Bug ID: 385705 Summary: KWin crash when opening Eric IDE Product: kwin Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-37-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: Saw a KWin crash when opening Eric (Python IDE) on a large project. Machine is running nVidia proprietary drivers on a desktop NVIDIA Corporation GP104 [GeForce GTX 1080] with all packages up-to-date with the kubuntu `backports-landing` ppa on Kubuntu 17.04. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ff70b9900 (LWP 2934))] Thread 5 (Thread 0x7f4fb4aa8700 (LWP 3212)): #0 0x7f4ff01cd510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4ff34f12c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f4ff34f1309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f4ff01c76da in start_thread (arg=0x7f4fb4aa8700) at pthread_create.c:456 #4 0x7f4ff6af3d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f4fb7815700 (LWP 3161)): #0 0x7f4ff6ae7e51 in __GI_ppoll (fds=0x7f4fbac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f4ff43903e1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f4ff4391cda in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f4ff433ebea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4ff416cf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4feef34df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f4ff4171c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4ff01c76da in start_thread (arg=0x7f4fb7815700) at pthread_create.c:456 #8 0x7f4ff6af3d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f4fcdc81700 (LWP 3103)): #0 0x7f4ff6ae7e51 in __GI_ppoll (fds=0x7f4fcac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f4ff43903e1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f4ff4391cda in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f4ff433ebea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4ff416cf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4feef34df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f4ff4171c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4ff01c76da in start_thread (arg=0x7f4fcdc81700) at pthread_create.c:456 #8 0x7f4ff6af3d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f4fe009f700 (LWP 2942)): #0 0x7f4ff6ae7d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4feb78f576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4feb78f68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ff43950bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4ff433ebea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4ff416cf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4fee1035d5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f4ff4171c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4ff01c76da in start_thread (arg=0x7f4fe009f700) at pthread_create.c:456 #9 0x7f4ff6af3d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f4ff70b9900 (LWP 2934)): [KCrash Handler] #6 0x4190b1bb in () #7 0x7f4fbf20a4a4 in () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.66 #8 0x7f4fbf20f768 in () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.66 #9 0x7f4fbede2468 in () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.66 #10 0x7f4ff4b9ba64 in QOpenGLTextureGlyphCache::resizeTextureData(int, int) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f4ff4b3c8a6 in QTextureGlyphCache::fillInPendingGlyphs() () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f4fef5e5dc7 in
[kwin] [Bug 381141] New: Crash of KWin when opening Chrome on nVidia Proprietary
https://bugs.kde.org/show_bug.cgi?id=381141 Bug ID: 381141 Summary: Crash of KWin when opening Chrome on nVidia Proprietary Product: kwin Version: 5.10.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Application: kwin_x11 (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.10.0-22-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Clicked a chrome launcher in the plasma panel. Chrome launched normally and loaded tabs, but kwin crashed/restarted. Kubuntu 17.04 up to date with current packages from the backports-landing ppa. Package: kwin-x11 Version: 4:5.10.1-0ubuntu1~ubuntu17.04~ppa1 -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0451c03900 (LWP 2341))] Thread 6 (Thread 0x7f0417fff700 (LWP 5772)): #0 0x7f044ad0c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f044ecb5b4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044a13d495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f044a13dd8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f044ad066da in start_thread (arg=0x7f0417fff700) at pthread_create.c:456 #6 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f04237ff700 (LWP 3429)): #0 0x7f045162d251 in __GI_ppoll (fds=0x7f0418000b38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f044eed4251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044eed5b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0449a73df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f044ad066da in start_thread (arg=0x7f04237ff700) at pthread_create.c:456 #8 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f041682a700 (LWP 2478)): #0 0x7f044ad0c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f044e0342c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f044e034309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f044ad066da in start_thread (arg=0x7f041682a700) at pthread_create.c:456 #4 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f042889f700 (LWP 2470)): #0 0x7f045162d251 in __GI_ppoll (fds=0x7f041c000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f044eed4251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044eed5b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0449a73df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f044ad066da in start_thread (arg=0x7f042889f700) at pthread_create.c:456 #8 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f043abda700 (LWP 2349)): #0 0x7f045162d18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f04462ce576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f04462ce68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f044eed8f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0448c425c5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f044ecb4c98 in () at
[kde] [Bug 222428] Wish for KDE recognize/compute DPI settings by different plugged screens
https://bugs.kde.org/show_bug.cgi?id=222428 Mike C. Fletcher <mcfle...@vrplumber.com> changed: What|Removed |Added CC||mcfle...@vrplumber.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379041] New: KWin crashes shortly after resume
https://bugs.kde.org/show_bug.cgi?id=379041 Bug ID: 379041 Summary: KWin crashes shortly after resume Product: kwin Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-19-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: * opened the laptop * display came back, a number of dialogs popped up telling me that the network manager connections had refreshed (bug in eric ide), I pressed down on esc to close them * display froze, panel at bottom of the screen went dark/grey, as though the kwin compositor was restarting * no display updates * kwin finally restarted (15-20s later) and all of the input (alt-tabs mostly) suddenly displayed Kubuntu 17.04 packages Dell XPS 9550 Nvidia proprietary drivers -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 [Current thread is 1 (Thread 0x7f70d1bfa900 (LWP 9014))] Thread 7 (Thread 0x7f7009cd8700 (LWP 20122)): #0 0x7f70d1626251 in __GI_ppoll (fds=0x7f6fe4000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f70ceeed251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f70cb4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f70cee9b88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f70cecc8fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f70c9a93df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f70ceccdc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f70cad266da in start_thread (arg=0x7f7009cd8700) at pthread_create.c:456 #8 0x7f70d163217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f70b1e8f700 (LWP 15725)): #0 0x7f70cad2c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f70cecceb4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f70ca15d495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f70ca15dd8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f70ceccdc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f70cad266da in start_thread (arg=0x7f70b1e8f700) at pthread_create.c:456 #6 0x7f70d163217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f709bfff700 (LWP 14150)): [KCrash Handler] #6 0x7f70d155f77f in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x7f70d156137a in __GI_abort () at abort.c:89 #8 0x7f70cecb4451 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f70b26ce6a4 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #10 0x7f70ceec981e in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f70ceed5e38 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f70ceeca313 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f70cfb7535c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f70cfb7cb11 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f70cee9d8a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f70ceef0eae in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f70cdba in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f70cee9b88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f70cecc8fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f70ceccdc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f70cad266da in start_thread (arg=0x7f709bfff700) at pthread_create.c:456 #22 0x7f70d163217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f709b7fe700 (LWP 9089)): #0 0x7f70cad2c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[kwin] [Bug 378960] New: Block around cursor does not update with nvidia proprietary
https://bugs.kde.org/show_bug.cgi?id=378960 Bug ID: 378960 Summary: Block around cursor does not update with nvidia proprietary Product: kwin Version: 5.9.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Created attachment 105096 --> https://bugs.kde.org/attachment.cgi?id=105096=edit Screenshot showing the cursor block (scrolled down while mouse was on bug-list above) When rendering the screen, a block of pixels maybe 64x64 (might be 32x32 up-scaled, hard to tell with the high-res screen) around the mouse cursor does not update in response to scrolling, content changes (e.g.typing text where you click, buttons doing click animations), etc. I can scroll quite a way and then leave the cursor sitting with an out-of-sync content background for a long period (at least 15s) without the background being updated to match the current background. If I move the mouse after the background freezes, the background seems to be selectively updating in the direction I move, which looks like a cache-invalidation update that's taking the position and motion and only updating that part of the cursor-box that should be getting changed. Platform: Dell XPS 9550 (Early 2016) Graphics: GeForce GTX 960M OS: Kubuntu 17.04 (up to date) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows
https://bugs.kde.org/show_bug.cgi?id=366651 --- Comment #4 from Mike C. Fletcher <mcfle...@vrplumber.com> --- (In reply to Martin Gräßlin from comment #3) > waiting for debug output https://paste.kde.org/p3jrxca0u has the output from a different machine showing the same behaviour. When the information was captured the Eric IDE was "stuck" such that I could edit/change/scroll etc the source window, but nothing else would update. As noted, hitting Alt+Shift+F12 a couple times does eliminate the condition. Frequency seems to have dropped off significantly at this point, I see the effect once every few weeks now, instead of many times/day. Likely that is due to an OS update on Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366651] New: Kwin Compositor Stops Updating Windows
https://bugs.kde.org/show_bug.cgi?id=366651 Bug ID: 366651 Summary: Kwin Compositor Stops Updating Windows Product: kwin Version: 5.6.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com This is a fairly frequent (many times/day) situation, so I can reproduce within a few hours (this is my daily driver machine, unfortunately), but I'm not sure what information to gather when it's in this state to aid in debugging. Basically the problem is that Kwin will stop updating windows after a while. In particular it's commonly seen while using Google Chrome, Chromium and The Eric Python IDE but it seems to affect e.g. Konsole as well. The windows are responsive to *input*, but their display does not get updated without an alt-tab away and back (at which point all of the changes the application has made are visible). If I go to the compositor kcm and select a different rendering backend (e.g. OpenGL 2.0 to OpenGL 3.1 or vice-versa) and apply, then the windows start rendering again for a while, so I'm assuming this is likely an unhandled event where the corrupt state is reset on compositor backend reset. I realize this likely isn't useful as a bug report yet, I'm mostly looking for advice as to how to produce a useful bug-report for the condition. Reproducible: Sometimes Steps to Reproduce: 1. General usage, chrome, Eric, Konsole 2. Lots of window switching, scrolling, editing (development workflow) Actual Results: After a few hours (or so), the compositor stops getting updates from applications. * nVidia Proprietary driver * Dell XPS 15 * Kubuntu 16.04 (up to date) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362668] Dolphin crash because Home/.config/katerc NOT writeable
https://bugs.kde.org/show_bug.cgi?id=362668 --- Comment #3 from Mike C. Fletcher <mcfle...@vrplumber.com> --- Created attachment 100519 --> https://bugs.kde.org/attachment.cgi?id=100519=edit New crash information added by DrKonqi dolphin (15.12.3) using Qt 5.5.1 - What I was doing when the application crashed: Just saw this happen when browsing to a (remote, slow) smb server. Clicked the address bar, typed in the *wrong-cased* next segment of the URL I wanted to visit. When replicating there was a dialog displayed saying that the wrong-cased version of the path didn't exist before Dolphin crashed. That is, it may not just be permissions causing the issue, it may be simply "missing" directories. -- Backtrace (Reduced): #8 0x7f3200968b99 in KDialogJobUiDelegate::Private::next() () from /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5 #9 0x7f31fd145ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f31fdc1905c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f31fdc1e516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f31fd11662b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362668] Dolphin crash because Home/.config/katerc NOT writeable
https://bugs.kde.org/show_bug.cgi?id=362668 Mike C. Fletcher <mcfle...@vrplumber.com> changed: What|Removed |Added CC||mcfle...@vrplumber.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366253] New: When clicking "i" button in plasma pop-up Android displays "Found" button, but button doesn't cancel ringer
https://bugs.kde.org/show_bug.cgi?id=366253 Bug ID: 366253 Summary: When clicking "i" button in plasma pop-up Android displays "Found" button, but button doesn't cancel ringer Product: kdeconnect Version: 0.8 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: mcfle...@vrplumber.com If you click on the (i) button in the KDE connect window that appears when you click the plasma icon the paired phone begins ringing and shows a big button saying "Found", which means, I suppose that this is supposed to be a "find my phone" button. Unfortunately, while clicking the button dismisses the "Found" dialog it doesn't turn off the audio/ringing, so the phone keeps ringing without any visible way to turn it off other than restarting the phone. Reproducible: Didn't try Steps to Reproduce: 1. Click on the plasma button 2. Click on the (i) button next to your paired device 3. Click on "Found" on the paired device Actual Results: Phone continues audio ringing (and vibrating). Expected Results: Stop ringing. Kubuntu 16.04, Nexus 5 w/ Android 6.0.1 all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366101] New: Show Desktop | Add Widgets => Desktop is hidden behind other windows
https://bugs.kde.org/show_bug.cgi?id=366101 Bug ID: 366101 Summary: Show Desktop | Add Widgets => Desktop is hidden behind other windows Product: plasmashell Version: 5.6.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: mcfle...@vrplumber.com The use case is this following: * Add a widget to the desktop from a machine with lots of running applications When you click "Show Desktop" the desktop is displayed and you can right click to select "Add Widgets", but as soon as the "Add Widgets" window opens the desktop is hidden behind the previously hidden windows. This seems like it may be the idea of the "Show Desktop" widget being closer to "Peek at Desktop for a Moment" than what a user would expect from "Show Desktop". That is, the effect of "Peek at Desktop" is a momentary "reveal" that should be replaced as soon as you do anything, while "Show Desktop" in the user's mind is closer to "Minimise all Windows". Reproducible: Always Steps to Reproduce: 1. Open some applications 2. Click Show Desktop 3. Right click on Desktop 4. Click Add Widgets Actual Results: All windows previously hidden "pop back" so that you can no longer see the desktop. Expected Results: Allow the user to complete selection and placement of widgets. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360605] New: oxygen5-icon-theme upgrade broken on conflict with player-volume-muted.png in dragonplayer
https://bugs.kde.org/show_bug.cgi?id=360605 Bug ID: 360605 Summary: oxygen5-icon-theme upgrade broken on conflict with player-volume-muted.png in dragonplayer Product: neon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: unstable packaging Assignee: n...@kde.org Reporter: mcfle...@vrplumber.com Same basic issue as in #360510 . This time the conflict is with Dragon Player. Unpacking oxygen5-icon-theme (5.18.0+git20160316.1310+15.10-0) over (5.18.0+git20160314.1628+15.10-0) ... dpkg: error processing archive /var/cache/apt/archives/oxygen5-icon-theme_5.18.0+git20160316.1310+15.10-0_all.deb (--unpack): trying to overwrite '/usr/share/icons/oxygen/22x22/actions/player-volume-muted.png', which is also in package dragonplayer 4:15.08.2-0ubuntu1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Errors were encountered while processing: /var/cache/apt/archives/oxygen5-icon-theme_5.18.0+git20160316.1310+15.10-0_all.deb Reproducible: Always Steps to Reproduce: 1. Configure a Kubuntu 15.10 machine to neon 2. Continue to update daily Actual Results: Conflicts in the png file. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360510] oxygen5-icon-theme error processing archive
https://bugs.kde.org/show_bug.cgi?id=360510 Mike C. Fletcher <mcfle...@vrplumber.com> changed: What|Removed |Added CC||mcfle...@vrplumber.com --- Comment #1 from Mike C. Fletcher <mcfle...@vrplumber.com> --- The error on the attached log indicates that both the oxygen5-icon-theme and libkdepim5 plugins are providing: /usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png This is seen on my (neon) machine as well. -- You are receiving this mail because: You are watching all bug changes.
