gdm3 fails to start when default session-name=ubuntu

This bug was fixed in the package gdm3 - 3.24.1-0ubuntu2

---------------
gdm3 (3.24.1-0ubuntu2) artful; urgency=medium

  * Add git_restore-session-name-override.patch:
    - Explicitly set gdm's session-name to 'gnome'. This fixes the login
      screen not starting when the default session is set to something else,
      such as when a Ubuntu (Unity) user installs gnome-shell and chooses
      gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha <email address hidden> Wed, 26 Apr 2017 14:52:18 -0400

Hello Jeremy, or anyone else affected,

Accepted gdm3 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.24.1-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Jeremy, or anyone else affected,

Accepted gdm3 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.20.1-1ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Jeremy, or anyone else affected,

Accepted gdm3 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.18.3-0ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Need to have gdm3 depend on:

gnome-session-wayland

Otherwise a manual install of, in my case:

gnome-core

on stock Ubuntu 16.04.2 will not allow gdm3 to complete startup and leave the user at blank screen.

I tested this from both Unity and Ubuntu GNOME.
3.18.3-0ubuntu2.1 on Ubuntu 16.04 LTS
3.20.1-1ubuntu2.1 on Ubuntu 16.10
3.24.1-0ubuntu0.1 on Ubuntu 17.04
I verified that after rebooting into gdm, I could successfully log in to both Unity and GNOME Shell.

Chris, please file a new bug for that issue since it doesn't sound to me like it's directly related to this bug or this bug fix.

@jbicha: yeah ... I just tried to reproduce in a gnome-boxes clean install of ubuntu-16.04.2-x86_64 to no avail. gnome-session-wayland is _not_ required.

Workaround: install ubuntu-gnome-default-settings

was all that was needed to complete a boot cycle.

Sorry for hijacking this bug!

This bug was fixed in the package gdm3 - 3.24.1-0ubuntu0.1

---------------
gdm3 (3.24.1-0ubuntu0.1) zesty; urgency=medium

  * New upstream release (LP: #1685500)
  * Drop git_dont-cache-ignore-wayland.patch:
    - Applied in new release
  * Add git_fix-crash-if-session-does-not-start.patch:
    - Backport 3.24 commit to fix a crash bug
  * Add git_restore-session-name-override.patch:
    - Explicitly set gdm's session-name to 'gnome'. This fixes the login
      screen not starting when the default session is set to something else,
      such as when a Ubuntu (Unity) user installs gnome-shell and chooses
      gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha <email address hidden> Tue, 02 May 2017 09:04:14 -0400

The verification of the Stable Release Update for gdm3 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package gdm3 - 3.20.1-1ubuntu2.1

---------------
gdm3 (3.20.1-1ubuntu2.1) yakkety; urgency=medium

  * Add git_restore-session-name-override.patch:
    - Explicitly set gdm's session-name to 'gnome'. This fixes the login
      screen not starting when the default session is set to something else,
      such as when a Ubuntu (Unity) user installs gnome-shell and chooses
      gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha <email address hidden> Tue, 02 May 2017 09:05:59 -0400

This bug was fixed in the package gdm3 - 3.18.3-0ubuntu2.1

---------------
gdm3 (3.18.3-0ubuntu2.1) xenial; urgency=medium

  * Add git_restore-session-name-override.patch:
    - Explicitly set gdm's session-name to 'gnome'. This fixes the login
      screen not starting when the default session is set to something else,
      such as when a Ubuntu (Unity) user installs gnome-shell and chooses
      gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha <email address hidden> Tue, 02 May 2017 09:11:19 -0400

The update to gdm3 - 3.24.1-0ubuntu0.1 is just crap.

It's not possible anymore to switch users. It just shows a black screen when using the user switch button.
Also logging out to the login screen also shows a black screen.
service gdm3 restart does not bring the login screen back.

Why are updates are not tested before they got uploaded?

Using Ubuntu Gnome, Zesty and Intel Skylake graphics.

Works-for-me after dist-upgrade using Ubuntu Gnome 17.04 64-bit and Intel®
HD Graphics 520 (Skylake GT2).

On Tue, May 16, 2017 at 10:46 AM Johon Doee <email address hidden>
wrote:

> The update to gdm3 - 3.24.1-0ubuntu0.1 is just crap.
>
> It's not possible anymore to switch users. It just shows a black screen
> when using the user switch button.
> Also logging out to the login screen also shows a black screen.
> service gdm3 restart does not bring the login screen back.
>
> Why are updates are not tested before they got uploaded?
>
> Using Ubuntu Gnome, Zesty and Intel Skylake graphics.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686257
>
> Title:
> gdm3 fails to start when default session-name=ubuntu
>
> Status in gdm:
> Fix Released
> Status in Ubuntu GNOME:
> In Progress
> Status in gdm3 package in Ubuntu:
> Fix Released
> Status in gdm3 source package in Xenial:
> Fix Released
> Status in gdm3 source package in Yakkety:
> Fix Released
> Status in gdm3 source package in Zesty:
> Fix Released
>
> Bug description:
> Impact
> ------
> If a person installs gnome-shell (and not ubuntu-gnome-desktop) on
> Ubuntu and choose gdm3, they will be unable to log in.
>
> Workaround: install ubuntu-gnome-default-settings
>
> This reverts a change that was made in gdm 3.16.
>
> Test Case
> ---------
> From Ubuntu (Unity), run
> sudo apt install gdm3
>
> Choose gdm3 when prompted.
> Restart.
> You should get a login screen. Your desktop session (Unity or whatever)
> should still be the same as whatever you last successfully logged in with.
>
> Regression Potential
> --------------------
> This patch was accepted upstream. It only affects the default session
> for the 'gdm' system user.
>
> Other Info
> ----------
> ubuntu-settings contains this in
> /usr/share/glib-2.0/10_ubuntu-settings.gchema.override
>
> [org.gnome.desktop.session]
> session-name="ubuntu"
>
> gdm3 fails to start unless session-name="gnome"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gdm/+bug/1686257/+subscriptions
>

Johon, please open a new bug for your issue by running "ubuntu-bug gdm3" . Your issue is probably with the 3.24.1 upgrade (LP: #1685500) and not with this particular bugfix.