Bug 460324 - no desktop, launcher and krunner after login following an upgrade to plasma 5.26
Summary: no desktop, launcher and krunner after login following an upgrade to plasma 5.26
Status: RESOLVED DUPLICATE of bug 450068
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.26.0
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
Depends on:
Reported: 2022-10-12 22:02 UTC by sp
Modified: 2022-10-17 18:53 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description sp 2022-10-12 22:02:43 UTC

After the upgrade to plasma 5.26 on a up-to-date kde neon, the desktop and krunner and launcher are missing after login. None of them are displayed.

If I wait for 10 minutes after login, which is coincidentally the same amount of time that the wallpaper changer of plasma is set to change (slideshow), they all come back; desktop has new wallpaper, krunner works and the launcher appears when pressing super-key.

I've already changed video driver from nvidia to nouveau. Problem still there. So I went back to nvidia driver.

If I try to change the wallpaper changer of plasma, when clicking on "OK", I loose again the desktop, krunner and launcher and the option window stays there  greyed out.

In that attempt I specified a slideshow delay from 10 minutes to  5.

Regardless of that option window now greyed out and no desktop, laucher and krunner, I rebooted.

I logged back in. Same problem but this time before they all came back in only took 5 minutes. So apparently even if option window froze and lost everyting the setting was accepted.

On a maybe related effect, when powersave of the screen comes in, the screen turns off but no key pressing or movement of the mouse brings the screen back on. I have to manually switch the screen off an on.

Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-3930K CPU @ 3.20GHz
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2
Comment 1 Nate Graham 2022-10-14 20:06:28 UTC
It would appear that Plasma is crashing and failing to automatically restart itself. Can you look for plasma crashes in the "crashed processes viewer" app?
Comment 2 sp 2022-10-14 23:41:25 UTC
I don't know where is the "crashed processes viewer"  app.  Where is it? how can I start it? ...
Comment 3 Nate Graham 2022-10-15 14:02:09 UTC
You can search for it in Kickoff or KRunner, or find it in the "System" category in Kickoff.
Comment 4 sp 2022-10-15 17:46:03 UTC
There's no/nothing resembling a "crashed processes viewer" either in system settings or krunner.
Is there a terminal/konsole command that can be used?
Don't know if its the right one but in konsole I've tried "drkonqi-coredump-gui" and it says no crash logs.
Comment 5 Nate Graham 2022-10-15 18:04:35 UTC
`coredumpctl` will do it too.
Comment 6 sp 2022-10-15 19:19:36 UTC
coredumpctl returns:  No coredumps found.
Comment 7 Nate Graham 2022-10-17 18:53:19 UTC
Ok, in that case nothing is crashing, and what's happening is that Plasma has lost the containment for this screen for unknown and very worrying issues.

This will be fixed automatically once Bug 450068 is fixed, and unfortunately cannot be reliably fixed without it; the current system is just too fragile and it needs to be replaced with a new one, which is what Bug 450068 is all about. I'm marking this as a duplicate of it. Thanks!

*** This bug has been marked as a duplicate of bug 450068 ***