https://bugs.kde.org/show_bug.cgi?id=374538
--- Comment #48 from imagina...@mailbox.org --- (In reply to Jeffrey Rocchio from comment #47) > (In reply to imaginator from comment #46) > > > ....But I'm pretty sure > > that if you manually shut down *all* programs you can see in the taskbar > > before trying to log out etc., it will always succeed. However, this is > > impractical for normal use. > > HTH. > Just fyi - shutting down all programs before attempting the logout does not > work for me. Too bad - makes it even harder for you. ;) But this may offer a little relief: can you still log into a virtual terminal via Ctrl + Alt + F2 when you encounter the problem? If you can, entering ps -e | grep plas should output something like this: 32002 ? 00:00:00 startplasma-x11 32136 ? 00:00:12 plasmashell You could then kill the Plasma-session by kill [process-number for startplasma-x11] This would spare you a full reboot and should bring you back to the login-screen. > > In my case once I'm done configuring my system after the new install, I only > rarely need to do a logout/re-login; so I'll just live with it. I did > inspect the system log for the time span where I invoked the logout; but I > can't claim to be able to make enough sense of it to truly confirm it is > this particular bug I have been experiencing. I do see quite a bit of > warnings and errors; most seem 'normal' to me. However there are three lines > that show: > > Dec 28 17:59:25 jeffFedora kscreen_backend_launcher[1535]: The X11 > connection broke (error 1). Did the X11 server die? > Dec 28 17:59:25 jeffFedora kdesud[50170]: kf.su.kdesud: Fatal IO error, > exiting... > Dec 28 17:59:25 jeffFedora systemd[1168]: > dbus-:1.2-org.kde.KScreen@0.service: Main process exited, code=exited, > status=1/FAILURE I've had the problem a few times lately (when I forgot to close that particular program mentioned earlier) but cannot find any of those lines in my system-log. It's a system-V-system, though. > > (If it matters, due to a few Wayland issues I just now always login to X11; > but, again I experience this issue independent of Wayland or X). This seems to be independent of X or Wayland. And as I see it, it's pretty clear when and where the problem was introduced (see comment #40). -- You are receiving this mail because: You are watching all bug changes.
