https://bugs.kde.org/show_bug.cgi?id=423889
Bug ID: 423889
Summary: Kwin hangs in KWin::WindowPixmap::create() /
xcb_request_check
Product: kwin
Version: 5.12.9
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: core
Assignee: kwin-bugs-n...@kde.org
Reporter: nathanielmbea...@gmail.com
Target Milestone: ---
Created attachment 129907
--> https://bugs.kde.org/attachment.cgi?id=129907&action=edit
Output of qdbus org.kde.KWin /KWin supportInformation
SUMMARY
Kwin hangs in KWin::WindowPixmap::create() / xcb_request_check
STEPS TO REPRODUCE
I cannot consistently reproduce.
I would estimate these occur roughly monthly with regular use, and occur during
mundane activities such as switching windows or typing in a textbox.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5
Kernel Version: 5.3.0-61-generic
ADDITIONAL INFORMATION
After several days using the KDE Plasma desktop, I suddenly found that all of
the windows had become unresponsive. I could still move the mouse, but clicking
didn't do anything. I could no longer change the volume with the volume
buttons. Also, the panel clock stopped ticking upward. Fortunately, I could
still use the keyboard to access a tty.
This normally works from a tty:
DISPLAY=:0 xdpyinfo
but during these episodes it would hang indefinitely, even after switching back
to the graphical display with Ctrl-Alt-F1 and then back again with Ctrl-Alt-F2.
I believe this would also hang after running and switching back to the
graphical window:
DISPLAY=:0 qdbus org.kde.KWin /KWin supportInformation
but I don't recall for sure.
This also hung:
DISPLAY=:0 kwin --replace
and showed an error:
qt.qpa.screen: QXcbConnection: Could not connect to display :0
Next tried this:
DISPLAY=:0 kquitapp5 plasmashell && kstart5 plasmashell
Got a different error after a timeout:
"Quitting application plasmashell failed. Error reported was:\n\n
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bug security
policy blocked the reply, the reply timeout expired, or the network connection
was broken."
In a later instance, I was able to revive the system like this:
kill -USR1 $(pgrep kwin_x11)
DISPLAY=:0 kwin --replace
I found this sufficiently convincing that is was an issue with Kwin and not
another component, so I thought I should report this bug. Backtraces and strace
logs are attached, as is my ~/.config/kwinrc and the output of the "qdbus
org.kde.KWin /KWin supportInformation" when it is in a responsive state.
--
You are receiving this mail because:
You are watching all bug changes.
