https://bugs.kde.org/show_bug.cgi?id=523155
Bug ID: 523155
Summary: plasmashell double-launches on cold boot, fails to
register DBus name, taskbar missing until manual
restart
Classification: Plasma
Product: plasmashell
Version First 6.7.3
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Startup process
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: 1.0
Plasma 6.7.3-1
KDE Frameworks 6.28
plasma-login (not SDDM)
Arch Linux, Wayland
Steps to reproduce:
1. Cold boot Arch Linux, Wayland session, plasma-login as display manager
2. Log in normally
3. Observe: plasmashell starts and registers DBus name successfully
4. ~8s later, a second plasmashell instance launches and fails to register the
same DBus name, exiting with an error
Observed:
Panel/taskbar missing or non functional until plasmashell is manually restarted
Expected:
Only one plasmashell instance launches at login no DBus registration conflict
Add info:
Full boot log: https://invent.kde.org/-/snippets/3844
Relevant window: 17:37:02–17:37:10 in the log. Ignore everything after 17:37:17
thats just me manually recovering with a keybound restart script
The second plasmashell instance is launched (app-plasmashell@<hash>.service)
with an empty SourcePath, indicating not via a .desktop autostart entry. I was
unable to identify what triggers this second launch.
Two other machines on the same network, running Plasma 6.7.2-1 with SDDM
(instead of plasma-login), do not reproduce this. Not yet confirmed whether the
point release or the login manager is the relevant factor.
Ruled out: KDE session restore (ksmserverrc showed count=0 at last logout),
both plasmashell-related .desktop autostart entries
(org.kde.plasmashell.desktop and
org.kde.plasma-fallback-session-restore.desktop- disabling either had no
effect), and stale ~/.config/session files (unrelated to plasmashell).
--
You are receiving this mail because:
You are watching all bug changes.
