https://bugs.kde.org/show_bug.cgi?id=433293
--- Comment #18 from Weng Xuetian <wen...@gmail.com> --- I'm on arch and I kinda aware of this issue for some time. 1. Qt would capture wayland error upon logout, and it triggers SIGABRT, because it will call qFatal(). 2. This SIGABRT would trigger drkonqi, but drkonqi would likely to freeze at this point because wayland compositor is quiting. 3. The "crashed" app would simply wait for drkonqi for the instruction. I also observed two different kind of drkonqi freeze a. it stucked in Qt wayland for querying some font settings, potentially a bug in Qt. When this happens, it will also hog the CPU. b. it stucked in KIdleTime's wayland plugin. In order to avoid this, following approaches may be tried 1. Fix Qt wayland by not triggering abort. While the wayland error is "fatal", it doesn't seems to be worth to use qFatal and leave some coredump, something like _exit might just work. At least we know that XIOError on X11 won't trigger qFatal. 2. don't install drkonqi (not so good resolution but an easy workaround for current user) 3. Fix drkonqi to make it not do anything related to GUI upon logout. I noticed that drkonqi has code that monitoring ksmserver, but apparently it doesn't work in this wayland logout case. 4. Fix kidletime's wayland plugin and fix qt wayland for the freeze issue. -- You are receiving this mail because: You are watching all bug changes.
