Twice now, once while out, and last night, while sleeping, the KDE desktop, all of the KDE apps, like konsole, and discord just vanish. I;m left with just firefox & chromium, which can be accessed with alt-tab. KDE COnnect is still connected, so the background services are still running. If I crtl-alt-F2; loginctl unlock-session; then return with ctrl-alt-F7 I get the SDDM login screen, but it is fully hung. The password box is visible with blanked out password dots already present, there is a text cursor, but it can't be moved and text can't be entered nor deleted. Since my system has been stable before the last KDE upgrade, I'm suspecting a KDE problem. After rebooting plasma came up okay except for konsole, it didn't start like normal, and starting manually shows my settings for it have been deleted. This has me suspecting a disk problem.
Created attachment 903476 [details] emerge --info
I've updated the kernel to the latest I have: 6.6.47 After rebooting on the new kernel, konsole still did not start, so despite starting it to rebuild and install the kernel, KDE is still not bringing it back on start, like it used to, but it did remember the window size. I did not find anything useful in dmesg, I'll capture that as soon as I notice this has happened again. If could take 2-3 days.
(In reply to Daiajo Tibdixious from comment #0) > Twice now, once while out, and last night, while sleeping, the KDE desktop, > all of the KDE apps, like konsole, and discord just vanish. I;m left with > just firefox & chromium, which can be accessed with alt-tab. KDE COnnect is > still connected, so the background services are still running. What exactly happened? Did plasmashell also vanish (no more task manager/panel, widgets), which I would have expected to read about from your $summary? (In reply to Daiajo Tibdixious from comment #0) > If I crtl-alt-F2; loginctl unlock-session; then return with ctrl-alt-F7 > I get the SDDM login screen, but it is fully hung. Why did you do that, your desktop wasn't locked from the above description at least? (In reply to Daiajo Tibdixious from comment #0) > After rebooting plasma came up okay except for konsole, it didn't start like > normal, and starting manually shows my settings for it have been deleted. > This has me suspecting a disk problem. In Plasma Wayland sessions, there is no "real" restore session support yet, so no need to try and debug that further.
(In reply to Andreas Sturmlechner from comment #3) > (In reply to Daiajo Tibdixious from comment #0) > > Twice now, once while out, and last night, while sleeping, the KDE desktop, > > all of the KDE apps, like konsole, and discord just vanish. I;m left with > > just firefox & chromium, which can be accessed with alt-tab. KDE COnnect is > > still connected, so the background services are still running. > What exactly happened? Did plasmashell also vanish (no more task > manager/panel, widgets), which I would have expected to read about from your > $summary? To clarify, imo your applications were still present, just minimised, so you could not access them anymore with your mouse, but Alt + F2 would have brought up krunner and there you could have started plasmashell again. That kind of phenomenon is not special to Plasma 6, it could have happened in 5 already.
(In reply to Andreas Sturmlechner from comment #3) > (In reply to Daiajo Tibdixious from comment #0) > > Twice now, once while out, and last night, while sleeping, the KDE desktop, > > all of the KDE apps, like konsole, and discord just vanish. I;m left with > > just firefox & chromium, which can be accessed with alt-tab. KDE COnnect is > > still connected, so the background services are still running. > What exactly happened? Did plasmashell also vanish (no more task > manager/panel, widgets), which I would have expected to read about from your > $summary? Yes the task bar is also gone, I implied that from "only firefox & chromium" left. > (In reply to Daiajo Tibdixious from comment #0) > > If I crtl-alt-F2; loginctl unlock-session; then return with ctrl-alt-F7 > > I get the SDDM login screen, but it is fully hung. > Why did you do that, your desktop wasn't locked from the above description > at least? > > (In reply to Daiajo Tibdixious from comment #0) > > After rebooting plasma came up okay except for konsole, it didn't start like > > normal, and starting manually shows my settings for it have been deleted. > > This has me suspecting a disk problem. > In Plasma Wayland sessions, there is no "real" restore session support yet, > so no need to try and debug that further.
(In reply to Andreas Sturmlechner from comment #3) > (In reply to Daiajo Tibdixious from comment #0) > > Twice now, once while out, and last night, while sleeping, the KDE desktop, > > all of the KDE apps, like konsole, and discord just vanish. I;m left with > > just firefox & chromium, which can be accessed with alt-tab. KDE COnnect is > > still connected, so the background services are still running. > What exactly happened? Did plasmashell also vanish (no more task > manager/panel, widgets), which I would have expected to read about from your > $summary? > > (In reply to Daiajo Tibdixious from comment #0) > > If I crtl-alt-F2; loginctl unlock-session; then return with ctrl-alt-F7 > > I get the SDDM login screen, but it is fully hung. > Why did you do that, your desktop wasn't locked from the above description > at least? Because this is the second time it has happened, I was wondering what would happen. I was surprised to see SDDM. > (In reply to Daiajo Tibdixious from comment #0) > > After rebooting plasma came up okay except for konsole, it didn't start like > > normal, and starting manually shows my settings for it have been deleted. > > This has me suspecting a disk problem. > In Plasma Wayland sessions, there is no "real" restore session support yet, > so no need to try and debug that further.
(In reply to Daiajo Tibdixious from comment #6) > > (In reply to Daiajo Tibdixious from comment #0) > > > If I crtl-alt-F2; loginctl unlock-session; then return with ctrl-alt-F7 > > > I get the SDDM login screen, but it is fully hung. > > Why did you do that, your desktop wasn't locked from the above description > > at least? > > Because this is the second time it has happened, I was wondering what would > happen. I was surprised to see SDDM. SDDM is not a lockscreen. It will only come back into focus when you log in as another user. I have linked to a number of upstream bugs with similar descriptions to your symptoms, although you haven't fully explained the scenario yet.
Before going to sleep, I turn off the monitor with it's button. I have KDE connect set to prevent screen blanking on it's own. I woke up, pressed the button on the monitor to wake it up, then I see just 2 windows: Firefox & chromium. Nothing else is visible. If I minimize the browsers there is a blank desktop, can't even see the minimized browsers. 484687 looks similiar, but mentions it's reproducible. The others talk about hibernation, I'm not doing that, the screen wasn't locked this time. The other time when I was out, it was locked, but exact same symtoms. My issue may be related to the memory issue that is mentioned, in that simply running over several days may be eventually triggering a memory leak.
Next time this happens, as I said, please fire up krunner and just start plasmashell anew from your existing session.
But also, please upgrade to newly stabilised 6.1.5.
Yesterday, since I saw an advisory to update portage, I forced an extra sync & upgraded to KDE 6.1.5 at the same time, and rebooted. This morning I woke up to find plasmashell has crashed again. alt+F2 doesn't do anything, I can't see anyway to start anything.
Sorry konsoles are still there. krunner in my user session just quits. In root I just get: # krunner QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kf.config.core: Created a KConfigGroup on an inaccessible config location "/etc/xdg/mimeapps.list" "Added Associations" kf.config.core: Created a KConfigGroup on an inaccessible config location "/etc/xdg/mimeapps.list" "Removed Associations" kf.config.core: Created a KConfigGroup on an inaccessible config location "/etc/xdg/mimeapps.list" "Added KDE Service Associations" kf.config.core: Created a KConfigGroup on an inaccessible config location "/etc/xdg/mimeapps.list" "Removed KDE Service Associations" kf.config.core: Created a KConfigGroup on an inaccessible config location "/etc/xdg/mimeapps.list" "Default Applications" kf.kunitconversion: currency conversion table data obtained via network Then nothing more.
Created attachment 903595 [details] ps -aef
Sorry for my ignorance, I was able to get the control bar back by "plasmashell" in krunner.
(In reply to Daiajo Tibdixious from comment #14) > Sorry for my ignorance, I was able to get the control bar back by > "plasmashell" in krunner. This time, did you lose any applications opened previously or did they reappear as minimised in your task panel? Do you have a multimonitor system?
(In reply to Andreas Sturmlechner from comment #15) > (In reply to Daiajo Tibdixious from comment #14) > > Sorry for my ignorance, I was able to get the control bar back by > > "plasmashell" in krunner. > This time, did you lose any applications opened previously or did they > reappear as minimised in your task panel? Discord has gone down each time that plasmashell crashed. Also, while both konsole windows were present, the tabs had been collapsed to one. > Do you have a multimonitor system? Not at the time of this crash, I had 2 for the first occurrence. The other monitor was very old and died recently.
Well plasmashell crashed again overnight, but discord did not go down, and the konsoles have their tabs, so I may have been wrong about that.
It took longer to crash this time, 3 days approximately. I don't use my system much, mostly watching YouTube & updating google docs & sheets.
This sounds just like the regular "plasmashell is sometimes vanished after screen standby" bug I've been having since Plasma 5 times already, with upstream having been through various workarounds against Qt crashing simply because DisplayPort standby e.g. leaves no screens enabled.
My monitor is connected by a Display Port cable. I'm going to switch it to HDMI.
Since switching to the HDMI cable, there have been no plasmashell crashes. So, the issue does seem to be related to using a Display Port cable.
Thanks for going through all these tests. This is finally established as a genuine (long-standing) UPSTREAM bug.
