This isn't quite enough in this situation.
- Log in over SSH or in a vt (so there is a logind session alive for your user)
- Log into the same user in Unity
- Simulate an Xorg crash (pkill -f -SEGV Xorg)
- Log back in
You don't have GTK_MODULES set properly. The previous gnome-session is
lingering.
To fix that, something like comment #3 is needed. Such as looping over
all 'active' units that are PartOf graphical-session.target and stopping
them all.
gnome-session needs a fix to its ExecStopPost to not kill the one we
just started.
I'll upload this and it can be reviewed in the queue.
** Changed in: gnome-session (Ubuntu)
Status: Fix Released => Triaged
** Changed in: gnome-session (Ubuntu)
Importance: Undecided => High
** Changed in: upstart (Ubuntu)
Status: Fix Released => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-session (Ubuntu)
Importance: High => Medium
** Changed in: gnome-session (Ubuntu)
Assignee: Martin Pitt (pitti) => Iain Lane (laney)
** Changed in: upstart (Ubuntu)
Assignee: Martin Pitt (pitti) => Iain Lane (laney)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
