https://bugs.kde.org/show_bug.cgi?id=514326
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=514443 --- Comment #9 from michaelk83 <[email protected]> --- (In reply to Christian Hacker from comment #8) > However, shouldn't specifically in the case of the locked Kde desktop a X11 > display :0 be available for applications? > If this is a security issue in connection with the crashed ksecretd, can > drkonqi be made to safely recover it's operation? I don't think this has to do with ksecretd. The only connection that I'm aware of is that DrKonqi likely needed a GUI environment to report the ksecretd crash (but couldn't get one, in this case). The kded6 failure is the same, though I'm not sure why it needed a GUI. Maybe it was also trying to display some error dialog? The display :0 not being available may have to do with being logged out. I'm not sure how the display server is managed in those cases. But I can surmise that a fully initialized and active session may be required for a display to be available. Your error logs also suggest that you may be missing xcb-cursor0 or libxcb-cursor0. That's also worth a check. -- You are receiving this mail because: You are watching all bug changes.
