| Summary: | Login immediately after Logout may fail if systemd service stops too slowly | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Jolene K <jolene> |
| Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | agurenko, bugseforuns, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
possibly duplicate of bug 450320 A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2318 Ah, this was fixed a year or so ago. |
SUMMARY If using the systemd startup and a user service takes too long to shut down, a future login may fail. STEPS TO REPRODUCE 1. Ensure Plasma uses the systemd startup 2. Have a systemd user service which is very slow to shutdown (like /bin/bash -c 'trap -- "" SIGINT SIGTERM; while true; do sleep 1000; done' in autostart, but the virtualbox guest additions work too) 3. Logoff and then login again very quickly (can use SDDM autologin for this) OBSERVED RESULT Login fails with mouse cursor on black background. session log says org.kde.startup: Could not start systemd managed Plasma session: "org.freedesktop.systemd1.TransactionIsDestructive" "Transaction for plasma-workspace-x11.target/start is destructive (graphical-session.target has 'stop' job queued, but 'start' is included in transaction)." EXPECTED RESULT Login works normally ADDITIONAL INFORMATION I believe that on logout, startplasma-{wayland,x11} should wait for graphical-session.target to stop instead of waiting for a DBUS name to disappear. I'll try to create a patch in the next few days.