Summary: | deadlock in QXcbConnection::xi2SetupDevices | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | SinClaus <tomsk_interface> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | bhush94, plasma-bugs, simonandric5 |
Priority: | NOR | ||
Version: | 5.4.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: |
https://bugreports.qt.io/browse/QTBUG-42738 https://bugs.freedesktop.org/show_bug.cgi?id=59361 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
SinClaus
2015-10-06 04:52:24 UTC
Thanks, this is a bug in Xlib, known also to Qt. Since you claim you can prevent this by suspending the compositor, I could assume we cause an X error (what's not a bug per se, but can maybe avoided) in the compositor. I'm frankly not sure whether Xlib stores to ~/.xsession-errors or journald, but it's printing to konsole if you run "kwin_x11 --replace &" from there ;-) iow: if we can spot an X error caused by kwin compositing in this condition, we *may* be able to avoid the deadlocking condition. Hm.... kwin_x11 --replace answers "FATAL ERROR while trying to open display". I'm running this from Vt2 on the local comp. kwin_x11 is in a Sl state. To interact with the X server from outside the X server you need to tell programs where to find it. Just run export DISPLAY=:0 export DISPLAY=:0 and kwin_x11 --replace reanimane KDE session, but composer is dead or don't catch buttons pressing. What do you mean by "don't catch buttons pressing"? Either way, I assume kwin does not effectively restart, but only the running instance gets killed and you're left with an unmanged desktop (windows don't have decorations etc.)? |