https://bugs.kde.org/show_bug.cgi?id=374538
--- Comment #26 from [email protected] --- (In reply to David Edmundson from comment #25) > Thanks. > > Backtrace shows kwin isn't frozen. It's happily polling as expected. > The fact that killing it didn't fix anything also implies kwin isn't at > fault. > > One other possibility is that nothing is frozen, and something has an input > grab: > DISPLAY=:0 xdotool key "XF86LogGrabInfo" > > from a TTY should hopefully show that. Perhaps a misunderstanding on my side. I took those backtraces when kwin was *not* hung. Shortly thereafter it did hang. Here's an excerpt from the backtrace: [...] [?2004h(gdb) thread apply all backtrace [?2004l Thread 11 (LWP 10570 "FreezeDetector"): #0 0x00007fd0bc9778c6 in __ppoll (fds=0x7fd084075f28, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:48 #1 0x00007fd0bd1e6679 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /opt/qt5/lib/libQt5Core.so.5 #2 0x00007fd0bd1e7b53 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/qt5/lib/libQt5Core.so.5 #3 0x00007fd0bd194f3b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/qt5/lib/libQt5Core.so.5 #4 0x00007fd0bcfb843e in QThread::exec() () from /opt/qt5/lib/libQt5Core.so.5 #5 0x00007fd0bcfb9451 in ?? () from /opt/qt5/lib/libQt5Core.so.5 #6 0x00007fd0be3f7d5e in start_thread (arg=0x7fd08ec03640) at pthread_create.c:473 #7 0x00007fd0bc98220f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (LWP 9600 "QSGRenderThread"): [...] It also happened with XRender. Full backtrace attached. -- You are receiving this mail because: You are watching all bug changes.
