** Description changed:
- After upgrading from resolute to stonking on 10/10, gdm3 will not allow
- me to enter a password after clicking my user.
+ [ Impact ]
+
+ gdm3 will not allow me to enter a password after clicking my user.
Password field will either be greyed out or there is no field.
Mouse cursor either stops shortly after or immediately, respectively.
gdm3 crashes and relaunches, but issue persists.
- --new info--
- per gdm3 debug mode, ubuntu session files cannot be found.
+ [ Test Plan ]
- gdm3 has hardcoded ubuntu as the fallback session in
- /usr/share/gdm/gdm.schemas. When this is not found, i.e. ubuntu-session
- not installed, gdm3 crashes as below.
+ 1. Set up a vanilla GNOME desktop by installing gnome-session and removing
ubuntu-session
+ 2. Reboot to the login screen
+ 3. Select your user
+ 4. Verify that you are able to log-in
- Adding FallbackSession=gnome to custom.conf fixes this.
+ [ Where problems could occur ]
- ACTION: gdm3 should not crash when an ubuntu session is not found. A
- fix should not assume any specific session is installed in order to
- avoid crashes.
+ The patch solves a double-free error.
+ If this is incorrect, problems would manifest as a new memory leak
- --old--
+ [ Other Info ]
- Workaround: use lightdm as DM for gnome.
-
- Things I've tried:
-
- Turning automatic login on - hangs after Plymouth - gdm3 started
-
- Purging gdm3 and installing gdm3
-
- Using gdm-config to disable smartcard / fingerprint
-
- Updating smartcard alternatives to use a password-inclusive variant
-
- Masking xdg-desktop-portal, xdg-desktop-portal-gnome, pcscd.socket
- pcscd.service, fprintd
-
- Creating a new user and attempting to log in using GDM
-
- Followed older resolute bugs (https://github.com/ublue-
- os/bluefin/issues/4618, https://github.com/JuhLabs/juhradial-
- mx/issues/67):
-
- Looked for system and user units with Wants=graphical-session.target,
- none found
-
- Disabled all my custom units
-
- Journals show:
-
- Started org.freedesktop.IBus.session.GNOME.service - IBus Daemon for GNOME.
- Created slice app-dbus\x2d:1.1\x2dorg.freedesktop.portal.IBus.slice - Slice
/app/dbus-:1.1-org.freedesktop.portal.IBus.
- Reached target gnome-session.target - GNOME Session.
- Reached target graphical-session.target - Current graphical user session.
- A graphical session is already running!
- Gdm: GdmDisplay: Session never registered, failing
- free(): double free detected in tcache 2
- GdmUserVerifierProxy: connection is closed
- gdm.service: Main process exited, code=dumped, status=6/ABRT
- gdm.service: Killing process 5447 (gdm-session-wor) with signal SIGKILL.
- Failed to start gdm-authd verification for user: The connection is closed
+ Adding FallbackSession=gnome to /etc/gdm3/custom.conf is a known
+ workaround
** Changed in: gdm3 (Ubuntu Stonking)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gdm3 (Ubuntu Stonking)
Status: Triaged => In Progress
** Tags removed: desktop-needs-sru
** Tags added: udeng-12017
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170614
Title:
gdm3 crash on password field, missing ubuntu-session file on vanilla
GNOME system: stonking after upgrade from resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2170614/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
