> sudo killall -9 Xorg This causes some havoc -- as this does not actually stop anything in the session, random services just start failing the next time they try to talk to X. Due to our Restart=on-failure, these units then try to restart a few times until they hit the restart limit and go to "failed".
So this is rather rude -- just log out instead, or do "kill -9 -1" to kill your user processes. That said, I think it's ok that services go to "failed" as long as the next login properly restarts them, which brings us to.. > In general any script which is on graphical-session doesn't get stopped. Indeed this does kill ubuntu-session.target and its associated services like unity7.service. But we don't configure a requirement in the other direction, i. e. graphical-session.target does not stop when ubuntu- session.target stops. /usr/lib/gnome-session/run-systemd-session has a loop to clean up failed units, but appparently that's not wide enough yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: In Progress Status in unity-gtk-module package in Ubuntu: Fix Released Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp