[SRU] New upstream release 3.36.3

Bug #1894874 reported by Iain Lane
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Iain Lane

Bug Description

[ Description ]

We should ship the stable update for gdm3

    - Always use separate session bus for greeter sessions
    - Chrome remote desktop fix
    - Don't hardcode path to plymouth
    - Fixes for when GDM isn't started on its configured initial VT (bug 1845801)
    - keyutils has a .pc file so use it
      This runs dbus-run-session, so the binary needs to be available
    - User switching fix

We have a GNOME MRE so upstream's fixes don't need to be explicitly verified.

[ QA ]

Test:

1. Regular login
2. Auto-login
3. Fast user switching
4. X and Wayland
5. Launching different sessions

[ Regression potential ]

It's the program which logs you in to your session - the consequences could be severe up to and including nobody being able to log in using gdm.

Iain Lane (laney)
Changed in gdm3 (Ubuntu):
status: New → Fix Released
Changed in gdm3 (Ubuntu Focal):
status: New → In Progress
assignee: nobody → Iain Lane (laney)
description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Iain, or anyone else affected,

Accepted gdm3 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.36.3-0ubuntu0.20.04.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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in gdm3 (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-focal
description: updated
description: updated
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (gdm3/3.36.3-0ubuntu0.20.04.1)

All autopkgtests for the newly accepted gdm3 (3.36.3-0ubuntu0.20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.2 (amd64, s390x, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#gdm3

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Iain Lane (laney) wrote :

Looks to me like the systemd-fsckd test is just busted on focal since 2020-08-13 :(

Revision history for this message
jeremyszu (os369510) wrote :

I'd some verification on this ticket.

[Steps]

1. Install an Ubuntu image (5.6.0-1027 kernel)
2. sudo apt upgrade
3. enable focal-proposed
4. sudo apt install gdm3
5. reboot

[Test scenarios]

* With attaching nVidia graphic P2000:
(NVIDIA Corporation GP106GL [Quadro P2000] [10de:1c30])

** using nouveau as graphic driver:

1. Regular login
 - Login as "u" through X: PASS
 - Login as "u" through Wayland: PASS

2. Auto-login
 - Auto-login as "u" through X: PASS
 - Auto-login as "u" through Wayland: PASS

3. Fast user switching
 - Login as "u" throuh X: PASS
 - Switch from "u" to "uu" through X: PASS
 - Switch from "uu" to "uuu" through Wayland: PASS
 - Switch from "uuu" to "uuuu" through Wayland: PASS
 - Switch from "uuuu" to "u": PASS
 - Switch from "u" to "uu": PASS
 - Switch from "uu" to "uuuu": PASS
 - Switch from "uuuu" to "uuu": PASS

4. X and Wayland
 - Not sure the test cases, please review the above test cases whether covering this case.

5. Launching different sessions
```
$ loginctl
SESSION UID USER SEAT TTY
      1 1001 u seat0 tty2
     15 1000 uu seat0 tty3
     17 1002 uuu seat0 tty4
     19 1003 uuuu seat0 tty5
     39 1005 uuuuuu seat0 tty7
     44 1004 uuuuu seat0 tty6
     49 1001 u pts/5
```

** using nvidia (from nvidia-driver-440) as graphic driver:

1. Regular login
 - Login as "u" through X: PASS

2. Auto-login
 - Auto-login as "u" through X: PASS

3. Fast user switching
 - Login as "u" throuh X: PASS
 - Switch from "u" to "uu" through X: PASS
 - Switch from "uu" to "uuu" through X: PASS
 - Switch from "uuu" to "uuuu" through X: PASS
 - Switch from "uuuu" to "u": PASS
 - Switch from "u" to "uu": PASS
 - Switch from "uu" to "uuuu": PASS
 - Switch from "uuuu" to "uuu": PASS

4. X and Wayland
 - nvidia is blocking Wayland.

5. Launching different sessions
```
$ loginctl
SESSION UID USER SEAT TTY
      1 1001 u seat0 tty2
     10 1001 u pts/1
      4 1000 uu seat0 tty3
      6 1002 uuu seat0 tty4
      8 1003 uuuu seat0 tty5
     c1 125 gdm seat0 tty1
```

* Without attaching graphic card:
(Intel Corporation Device [8086:9bc5] using i915)

1. Regular login
 - Login as "u" through X: PASS
 - Login as "u" through Wayland: PASS

2. Auto-login
 - Auto-login as "u" through X: PASS
 - Auto-login as "u" through Wayland: PASS

3. Fast user switching
 - Login as "u" throuh X: PASS
 - Switch from "u" to "uu" through X: PASS
 - Switch from "uu" to "uuu" through Wayland: PASS
 - Switch from "uuu" to "uuuu" through Wayland: PASS
 - Switch from "uuuu" to "u": PASS
 - Switch from "u" to "uu": PASS
 - Switch from "uu" to "uuuu": PASS
 - Switch from "uuuu" to "uuu": PASS
 - Switch from "uuu" to "uuuuuu" (X): PASS
 - Switch from "uuuuuu" to "uuuuu" (Wayland): PASS

4. X and Wayland
 - Not sure the test cases, please review the above test cases whether covering this case.

5. Launching different sessions
```
$ loginctl
SESSION UID USER SEAT TTY
     12 1005 uuuuuu seat0 tty7
     15 1004 uuuuu seat0 tty8
     17 1001 u pts/3
      4 1001 u seat0 tty2
      5 1000 uu seat0 tty3
      7 1002 uuu seat0 tty4
      9 1003 uuuu seat0 tty5
```

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdm3 - 3.36.3-0ubuntu0.20.04.1

---------------
gdm3 (3.36.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ Iain Lane ]
  * New upstream release (LP: #1894874).
    - Always use separate session bus for greeter sessions
      This runs dbus-run-session, so the binary needs to be available
    - Chrome remote desktop fix
    - Don't hardcode path to plymouth
    - Fixes for when GDM isn't started on its configured initial VT (LP:
      #1845801)
    - keyutils has a .pc file so use it
    - User switching fix
  * debian/{control,gbp.conf}: Update for ubuntu/focal & upstream/3.36.x

  [ Simon McVittie ]
  * Add Depends on dbus, for dbus-run-session
  * Update symbols file.
    This ignores a change to private symbols: gdm_find_display_session_for_uid
    isn't declared in a public header, and nothing in Debian/Ubuntu seems to
    call it.

 -- Iain Lane <email address hidden> Tue, 08 Sep 2020 18:01:39 +0100

Changed in gdm3 (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for gdm3 has completed successfully and the package is now being 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.