Re: [Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
On Sun, Oct 02, 2016 at 10:27:43AM -, Martin Pitt wrote: > Iain Lane [2016-10-01 19:26 -]: > > Hmm. Maybe this is saying that we should bind ubuntu-session.target to > > something else - like unity7? You can't log in again with an active > > unity7, so in theory (if stop is propagated down to graphical-session > > and graphical-session-pre) there wouldn't be a need to stop/restart in > > the script since everything would be stopped by definition if you're > > trying to start unity7 again. > > I like that idea in principle -- picking a session leader which > automatically dies when X goes away would be a lot simpler indeed (and > gnome-session does not do that). I picked gnome-session as the session > leader because it traditionally has had that role, and it still has > the API for logging out. > > Another point is that we want to make unity/compiz robust against > crashes and provide auto-restart -- if it becomes the session leader, > then the whole session will go down on any crash. So picking > unity7.service in particular is a bad choice. It would be good if it were possible to say that the BindsTo shouldn't trigger the target to stop until after systemd gives up restarting the unit. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
On Sun, Oct 02, 2016 at 08:39:01AM -, Martin Pitt wrote: > > If you ever end up stopping gnome-keyring from within a new session > then its ExecStopPost kills the upstart session of this new one that we > are starting up, *not* the previous one that it was started up under. > > I assume you meant to say "gnome-session.service" here, not keyring (as > its ExecStopPost is harmless). gnome-session is the session leader, so > stopping it by definition means to end the current session. Yes I did. But the problem is that it is *not* always stopped when the session dies, so it is a bad choice of leader while that is true. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
Iain Lane [2016-10-01 19:26 -]: > Hmm. Maybe this is saying that we should bind ubuntu-session.target to > something else - like unity7? You can't log in again with an active > unity7, so in theory (if stop is propagated down to graphical-session > and graphical-session-pre) there wouldn't be a need to stop/restart in > the script since everything would be stopped by definition if you're > trying to start unity7 again. I like that idea in principle -- picking a session leader which automatically dies when X goes away would be a lot simpler indeed (and gnome-session does not do that). I picked gnome-session as the session leader because it traditionally has had that role, and it still has the API for logging out. Another point is that we want to make unity/compiz robust against crashes and provide auto-restart -- if it becomes the session leader, then the whole session will go down on any crash. So picking unity7.service in particular is a bad choice. Of course over time we want to get rid of gnome-session -- we don't need its service management any more, thus the only thing it provides is that D-Bus API for logout/user switching etc. This can/should be replaced with calls to stop units or calls to the DM, and then we should actually be able to completely drop that concept of a "session leader" (or rather, foo-session.target then *is* the leader, as we really intend). But we aren't there yet, so until then I think BindsTo=gnome-session.service is still conceptually correct IMHO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
> If you ever end up stopping gnome-keyring from within a new session then its ExecStopPost kills the upstart session of this new one that we are starting up, *not* the previous one that it was started up under. I assume you meant to say "gnome-session.service" here, not keyring (as its ExecStopPost is harmless). gnome-session is the session leader, so stopping it by definition means to end the current session. I now cleaned up the transaction handling to avoid having to wait for "deactivating" units after *-session.target ends (both at the top of the script to clean up lingering sessions and the end to cleanly exit without prematurely stopping X). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This bug was fixed in the package upstart - 1.13.2-0ubuntu32 --- upstart (1.13.2-0ubuntu32) yakkety; urgency=medium * debian/systemd-graphical-session.conf: Stop any lingering active units when logging in. (LP: #1618886) * debian/control: Break old versions of gnome-session, which take the session down when stopped in the above way. -- Iain Lane Tue, 27 Sep 2016 17:47:27 +0100 ** Changed in: upstart (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
On Sat, Oct 01, 2016 at 01:53:56PM -, Martin Pitt wrote: > > 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. > > I think we would only need to "systemctl stop graphical-session.target" > for this, otherwise a unit forgets the PartOf= and that loop would not > work anyway. I tried this, but I think that it might have only been before I worked out the below ExecStopPost issue - so it's worth testing again. > > > gnome-session needs a fix to its ExecStopPost to not kill the one we > just started. > > This is similar to waiting for "deactivating" units after > *-session.target goes down. On the systemd sprint we just figured out a > better scheme for this which solves that waiting, does not require this > session ID tracking, and also gets rid of the manual starting of > graphical-session-pre.target: Eventually we just want to declare in > *-session.target that it comes After=graphical-session-pre.target and > have this propagate to the dependencies > (https://github.com/systemd/systemd/issues/3750). Until then we can just > have a mini-generator do this for us. After we have the Requires/After > =graphical-session-pre.target, then "systemctl stop graphical-session- > pre.target" properly blocks until all "later" units are completely > stopped. I remember this problem. It would only solve this specific issue if it lets us get rid of the stop or restart in the session-runner script. If you ever end up stopping gnome-keyring from within a new session then its ExecStopPost kills the upstart session of this new one that we are starting up, *not* the previous one that it was started up under. That's a mismatch vs. session and user specific semantics of upstart and systemd --user. Hmm. Maybe this is saying that we should bind ubuntu-session.target to something else - like unity7? You can't log in again with an active unity7, so in theory (if stop is propagated down to graphical-session and graphical-session-pre) there wouldn't be a need to stop/restart in the script since everything would be stopped by definition if you're trying to start unity7 again. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
> 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. I think we would only need to "systemctl stop graphical-session.target" for this, otherwise a unit forgets the PartOf= and that loop would not work anyway. > gnome-session needs a fix to its ExecStopPost to not kill the one we just started. This is similar to waiting for "deactivating" units after *-session.target goes down. On the systemd sprint we just figured out a better scheme for this which solves that waiting, does not require this session ID tracking, and also gets rid of the manual starting of graphical-session-pre.target: Eventually we just want to declare in *-session.target that it comes After=graphical-session-pre.target and have this propagate to the dependencies (https://github.com/systemd/systemd/issues/3750). Until then we can just have a mini-generator do this for us. After we have the Requires/After =graphical-session-pre.target, then "systemctl stop graphical-session- pre.target" properly blocks until all "later" units are completely stopped. ** Bug watch added: github.com/systemd/systemd/issues #3750 https://github.com/systemd/systemd/issues/3750 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This bug was fixed in the package gnome-session - 3.20.2-1ubuntu4 --- gnome-session (3.20.2-1ubuntu4) yakkety; urgency=medium * debian/data/run-systemd-session: Stop any lingering active units when logging in. (LP: #1618886) * debian/data/gnome-session.service: Save the XDG SESSION we were started with, and only use that one to end the session. Otherwise, if we are stopped by the above codepath, we risk stopping the session that we are logging into and not the previous (crashed) one. * debian/patches/50_ubuntu_sessions.patch: Set the desktop names to Unity:Unity7. "Unity" is shared between Unity 7 and Unity 8, but applications should be able to Only/NotShowIn either one of these if they want. -- Iain Lane Wed, 28 Sep 2016 12:09:16 +0100 ** Changed in: gnome-session (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
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 Touch seeded packages, which is subscribed to upstart 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: Triaged Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This bug was fixed in the package upstart - 1.13.2-0ubuntu31 --- upstart (1.13.2-0ubuntu31) yakkety; urgency=medium * init/tests/test_conf.c: Disable previous check harder (on powerpc). upstart (1.13.2-0ubuntu30) yakkety; urgency=medium * init/tests/test_conf.c: Disable check in "Invalid .conf file does not stop ConfFile being serialised" test on powerpc, there is just no pleasing it and the numerous build retries are unnerving. upstart (1.13.2-0ubuntu29) yakkety; urgency=medium * debian/systemd-graphical-session.conf: Drop workaround for killing gnome-keyring, this was fixed properly now. * debian/systemd-graphical-session.conf: Add missing $unit to systemctl show call, so that the cleanup of failed units actually works. (LP: #1618886) -- Martin Pitt Mon, 19 Sep 2016 12:26:08 +0200 ** Changed in: upstart (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This bug was fixed in the package gnome-session - 3.20.2-1ubuntu3 --- gnome-session (3.20.2-1ubuntu3) yakkety; urgency=medium [ Dmitry Shachnev ] * Backport upstream patch to allow users to override $QT_QPA_PLATFORMTHEME (allow_overriding_qt_platformtheme.patch). [ Martin Pitt ] * debian/data/run-systemd-session: Add missing $unit to systemctl show call, so that the cleanup of failed units actually works. (LP: #1618886) -- Martin Pitt Fri, 16 Sep 2016 15:27:56 +0200 ** Changed in: gnome-session (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Changed in: gnome-session (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gnome-session (Ubuntu) Status: Won't Fix => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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: Fix Committed Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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 Status in upstart package in Ubuntu: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Changed in: upstart (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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 Status in upstart package in Ubuntu: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
The same "missing $unit" is in /usr/share/upstart/systemd- session/upstart/systemd-graphical-session.conf. ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu) Status: New => In Progress ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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 Status in upstart package in Ubuntu: In Progress 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp