dx-packages team mailing list archive

[Iain Lane <iain@xxxxxxxxxxxxxxxxxxx>]

unity-gtk-module needs to update the systemd environment now too

** Description changed:

+ [ Description ]
+ 
+ In Xenial, when dbus-user-session is installed, dbus' upstart job still
+ starts a new bus. Things get confused about which bus to talk to.
+ 
+ [ Fix ]
+ 
+ Already fixed in Yakkety. Cherry-pick the upstart job. On top of
+ Yakkety's version, call `dbus-update-activation-environment --verbose
+ --systemd GTK_MODULES', because Xenial does not have the change in
+ upstart to automatically publish to the systemd activation environment.
+ 
+ [ QA ]
+ 
+ Install dbus-user-session, press print screen. It should be delayed if
+ you are experiencing this bug, and not delayed otherwise.
+ 
+ Remove dbus-user-session, make sure the session still works properly -
+ the global menu works, everything launches properly, etc.
+ 
+ [ Regression potential ]
+ 
+ This change alters the way that the session bus is launched, even if you
+ aren't using dbus-user-session. Even though this same change is deployed
+ in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-
+ session by default, so the case where you don't have it isn't as well
+ tested. I would suggest focusing some testing on the non dbus-user-
+ session case.
+ 
+ [ Original report ]
+ 
  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as launching
  chromium and ctrl-alt-t for a new terminal session.
  
  Removing both the deb and the snap followed by a reboot does not fix the
  symptoms.
  
  Xenial amd64 laptop

** Also affects: unity-gtk-module (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: unity-gtk-module (Ubuntu)
       Status: New => Fix Released

** Changed in: unity-gtk-module (Ubuntu Xenial)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1644323

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions