SUMMARY Crashed when trying to set desktop background (will make ticket when I can reproduce) and on reboot the shell no longer loads in either x11 or Wayland. STEPS TO REPRODUCE (May not be reproducible) 1. Crash plasmashell (in my case, by double clicking already-selected desktop background) 2. reboot 3. log back in OBSERVED RESULT Logs in, but shell doesn't start. Can see my desktop, and can open GUI apps with the command line. EXPECTED RESULT Shell starts as usual SOFTWARE/OS VERSIONS Linux Kernel: 6.5.0-18-generic (64-bit) KDE Neon: 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I scrubbed journalctl and found the error (I think): `plasmashell[1349]: Aborting shell load, the activity manager daemon (kactivitymanagerd) is not running` I also recently added an entry for krunner in /usr/share/dbus-1/services because people recommended it to resolve krunner not launching. However, the file no longer exists. Could be related?
Apologies, it looks like I should've used journalctl -b All I'm getting is "KPackageStructure of KPluginMetaData(PluginId:"org.kde.plasma.betterinlineclock", filename: "..." doers not match request format "Plasma/applet") " and a few other normal-looking events. Nothing I can see that suggests the shell failed to load but I could be wrong. I'll upload any logs you need if you ask! But since I want to... use my system I might opt to re-install later today :'D
Okay so I can manually add the application launcher and task panel but the one present by default is gone. Maybe it just deleted the panel?
Can you paste here the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc ?
*** This bug has been marked as a duplicate of bug 482066 ***
(In reply to Marco Martin from comment #3) > Can you paste here the file > ~/.config/plasma-org.kde.plasma.desktop-appletsrc ? https://pastebin.com/NfWwyBZH Just as a warning that I've basically re-added the default plasma panel by manually adding the panel and widgets. So this may look normal (?) But also as another note that since my device doesnt have Nvidia graphics, I don't think it was the driver update in the other ticket that fixed their particular case.