Bug 458649 - Plasmashell fails to load because kactivitymanagerd failed to load
Summary: Plasmashell fails to load because kactivitymanagerd failed to load
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.24.6
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-02 21:06 UTC by cantfind
Modified: 2022-09-08 23:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
output of journalctl (136.69 KB, text/plain)
2022-09-02 21:06 UTC, cantfind
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cantfind 2022-09-02 21:06:46 UTC
Created attachment 151791 [details]
output of journalctl

SUMMARY
***
Started the computer, typed password in SDDM and logged in, KDE splash loading animation took a bit longer than usual.
After the splash disapeared, no desktop appeared, only mouse cursor showed. There was an animation for hot corner (but since there were no windows, I don't know if it was functioning). 
No launcher menu (and the bar with quick launch and task bar), the win-key did nothing. 
alt-space, which usually brings up the search widget did nothing. 
win+l did return me to the lockscreen, re-opening did nothing. 
ctrl+alt+del and request to logout did log me out, logging in again brought me to the same state.
After restart KDE loaded as usual. 
I was not able to reproduce this after restart.
***


STEPS TO REPRODUCE
1. Unable to reproduce

OBSERVED RESULT
No desktop

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  5.15.60-1-MANJARO 
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Attached journal during that time (up to restart, after which KDE loaded fine)
Comment 1 Nate Graham 2022-09-08 23:26:31 UTC
Thanks for the log it's very helpful. With it, we can see what happened:


Sep 02 23:01:11 master-desktop dbus-daemon[663]: [session uid=1000 pid=663] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.19' (uid=1000 pid=774 comm="/usr/lib/org_kde_powerdevil")
Sep 02 23:01:11 master-desktop systemd[641]: Starting KActivityManager Activity manager Service...

[...]


Sep 02 23:03:09 master-desktop kactivitymanagerd[835]: The X11 connection broke (error 1). Did the X11 server die?

[...]

Sep 02 23:03:09 master-desktop systemd[641]: plasma-kactivitymanagerd.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 23:03:09 master-desktop systemd[641]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.

[...]

Sep 02 23:01:12 master-desktop plasmashell[768]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.



So this paints a picture of the X server dying and taking everything down with it during startup. Unfortunately there's no way for Plasma and its daemons to survive this.

You'll want to gather X11-related logs and backtraces and submit them in a bug report at https://gitlab.freedesktop.org/xorg/xserver/-/issues/