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 <iain.l...@canonical.com> Tue, 08 Sep 2020 18:01:39 +0100
** Changed in: gdm3 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gnome-session-binary fixes it, or just not using automatic
login.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
