This bug was fixed in the package gdm3 - 3.28.2-0ubuntu1.2
---------------
gdm3 (3.28.2-0ubuntu1.2) bionic; urgency=medium
* debian/patches/libgdm-drop-support-for-serializing-multiple-opens.patch,
debian/patches/libgdm-fix-pointer-boolean-task-confusion.patch,
debian/patches/libgdm-don-t-keep-manager-proxy-around-longer-than-we-nee.patch,
debian/patches/libgdm-use-g_object_unref-instead-of-g_clear_object-for-w.patch,
debian/patches/libgdm-get-connection-explicitly.patch,
debian/patches/libgdm-Drop-weak-refs-on-the-GDBusConnection.patch,
debian/patches/libgdm-Unref-the-manager-propagated-from-task.patch,
debian/patches/libgdm-Don-t-double-ref-the-connection-got-from-task.patch,
debian/patches/libgdm-Don-t-leak-connection-on-sync-re-authentication.patch,
debian/patches/libgdm-Use-auto-pointers-and-cleanup-code.patch,
debian/patches/libgdb-Try-to-reuse-connections-from-the-available-proxie.patch,
debian/patches/libgdm-Don-t-save-manager-address.patch,
debian/patches/libgdm-Return-NULL-on-invalid-client-instances.patch:
- Cherry picks commits from upstream 3.28 branch to propely fix ref-counting
issues on GdmClient (LP: #1766137)
gdm3 (3.28.2-0ubuntu1.1) bionic; urgency=medium
* debian/gbp.conf: Add with 'bionic' configuration.
* debian/control{,.in}: Update Vcs-* for git.
* New upstream release (LP: #1773968):
- Reference counting fixes for GdmClient (LP: #1766137)
- ensure plymouth is quit properly even when local greeter is disabled
- make sure GDM doesn't hang when called with unknown command line arguments
* debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
Drop, included in this release.
gdm3 (3.28.0-0ubuntu1.1) bionic; urgency=medium
* debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
Cherry-pick two patches from the 3.28 branch. These fix a refcounting bug
in the GDM Client object, which had meant that the DBus connection was
being disposed too early in some cases, particularly when logging in after
a failed attempt. The symptom of that was that the system hung on a
"blank" screen. (LP: #1766137)
* debian/control{,.in}: Update for bionic
-- Marco Trevisan (Treviño) <[email protected]> Tue, 05 Jun 2018
11:58:41 +0100
** Changed in: gdm3 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1773968
Title:
[SRU] 3.28.2
Status in gdm3 package in Ubuntu:
Fix Released
Status in gdm3 source package in Bionic:
Fix Released
Bug description:
[ Description ]
The second stable release in the 3.28 series.
[ QA ]
Log in, log out, log in again. Get your password wrong. Try different
sessions. Lock the screen, try to swtich to a different user.
We have a GNOME SRU exception allowing us to assume that upstream's
fixes are good, and they don't require explicit QA. Please test gdm as
per the above smoke testing.
(https://wiki.ubuntu.com/StableReleaseUpdates/GNOME)
(In this case there's bug #1766137 which will get explicitly tested.)
[ Regression potential ]
A bad GDM update will, at worst, mean that people can't log in
graphically.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773968/+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
