The unity-gtk-module problem is simple enough to fix (bring back the
upstart job, and restrict the systemd unit to dbus+systemd to avoid
calling initctl set-env twice). Opening a second gnome-session task to
investigate the more general "services don't go down when the session
stops" issue.
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Status: New => Triaged
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- unity-gtk-module.service is racy
+ unity-gtk-module.service is racy; session services don't stop if session
terminates
--
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:
Triaged
Status in unity-gtk-module 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
