History

David Edmundson 39ecc45e5b [systemd] Fix logout issues It is important that we end plasma-core.target plasma-workspace.target and graphical-session.target when we log out. graphical-session in turn closes all other apps and daemons and prevents restarts. Handling it in systemd gives the least racey option. graphical-session used to be hanlded in the plasma-ksmserver service file, but this was removed in 5.24 in a refactor where it caused issues for Xwayland restarting. This patch reintroduces the sentinel programs to close down our target, which in turn take down the other targets. It also removes a complicated use of templates that in hindsight didn't really solve anything. BUG: 448492 Testing done: - logout of wayland shows all targets as inactive, logging in repeatedly works smoothly - logout of X11 behaves the same. - calling systemctl --user stop plasma-kwin_wayland.service closes the session - killing ksmserver on wayland does not close the session - killing ksmserver on X does		4 years ago
..
CMakeLists.txt	[systemd] Fix logout issues	4 years ago
README.md	…
kde-systemd-start-condition.cpp	[kde-systemd-start-condition] Always return success on non Plasma	4 years ago
plasma-core.target	[systemd] Fix logout issues	4 years ago
plasma-ksplash-ready.service.in	…
plasma-workspace-wayland.target	[systemd] Fix logout issues	4 years ago
plasma-workspace-x11.target	[systemd] Fix logout issues	4 years ago
plasma-workspace.target	[systemd] Fix logout issues	4 years ago

README.md

Startup

Startup can be summarised as being:

plasma-core.target plasma-workspace@.target graphical-session.target

plasma-workspace@ is the target explicitly activated.

X11 and wayland

plasma-workspace@ is a template file that ends with x11 or wayland. That will then require the correct kwin_ startup order can be different between the two.

Wants & Order

Note that in systemd dependencies (wants/wantedby) counter-intuitively do not determine order.

plasma-workspace wants graphical-session, meaning it will make it something started by it, but it also explicitly comes before graphical-session.

The order of events is: plasma-core does anything that adjusts environment variables plasma-workspace@ starts all runtime services graphical-session is at a point where everything including runtime services are up

Adding a new service

If it should only be used on plasma it should be wanted by plasma-core or plasma-workspace@.

That service is responsible for setting "After=plasma-core.target" if we need envs set up.