As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of gnome-shell from artful-
proposed was performed and bug 1726821 was found.  Please investigate
this bug report to ensure that a regression will not be created by this
SRU. In the event that this is not a regression remove the
"verification-failed" tag from this bug report and add the tag "bot-
stop-nagging" to bug 1726821 (not this bug). Thanks!

** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725153

Title:
  Reintroduce headless mode in GNOME Shell

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  Fix Committed
Status in mutter source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * I day before the 17.10 release, we had to revert some commits in
  GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577
  which was a release blocker (GNOME Shell not displaying anything on
  multiple config).

   * Pinging upstream, they debugged it and found the real issue in
  mutter, and so fixed it, which will enable us to align again with
  upstream's repo.

   * This should mostly be a no visible-effect for previously impacted
  users, but GNOME Shell shouldn't crash anymore in GDM (reverting then
  to Xorg), triggering apport on logging, and the users can then use
  Wayland instead of Xorg.

  [Test Case]

   * Install both mutter and gnome-shell to their latest version in -proposed
   * Reboot
   * Ensure you have an UI in GDM
   * Log in into your session, check that you have an UI and everything is 
showing up as expected

  [Regression Potential]

   * Impact is a regression in GNOME Shell (showing up your entire UI)
  and not being able to log in. However, some of us (not impated by the
  bug) are already running latest version and don't see any issue. I
  have also asked 3 people being impacted by the bug and fixed by the
  revert to test upstream commits (prepared a package for them in a
  PPA), and they are running on it since yesterday, confirming Wayland
  is available.

   * The regressions are quite straightfoward to see: either you have an
  UI in GDM or none.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1725153/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to