First boot with fingerprint auth enabled, gdm doesn't prompt to enter password

[Luke Freeman]

Steps:

- Enroll fingerprints
- Run `pam-auth-update`
- Enable "Fingerprint authentication"
- Restart

Outcome:

Fingerprint authentication will work correctly but the textbox to enter a password manually will be disabled. If fingerprint verification fails, then you can type into it.

Expected:

Should be able to enter your password manually OR use the fingerprint.

Ideal scenario:

Some things require that you enter your password at least once on startup (e.g.: unlocking the keyring).

The best UX (in my opinion) would be to disallow the fingerprint option and require a password on first login. Each subsequent login should then default to fingerprint (or other option as configured), hide the password entry and then only show the password entry if verification fails.

System info:

Ubuntu Jammy Jellyfish (development branch)
Gnome 42
Wayland
5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1966795/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

In case this is due to fprintd crashing, see also bug 1960336.

[Francois Thirioux (fthx)]

Hi all,

I run into the same issue (Jammy, GDM).
Sometimes I get pwd and fp auth, sometimes fp *then* pwd. Very random.

Very annoying since a fp gdm auth causes GS to ask for pwd to open seahorse keys wallet pwd after session startup.

Logs:

07:48:17 gdm3: Gdm: Child process -1900 was already dead.
07:48:17 gsd-color: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Chimei_Innolux_Corporation_gdm_126
07:48:17 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
07:48:17 gnome-shell: Registering session with GDM
07:48:14 gdm-session-wor: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
07:48:14 gdm-session-wor: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
07:48:14 gdm-session-wor: pam_unix(gdm-password:session): session opened for user fthx(uid=1000) by (uid=0)
07:48:14 gdm-session-wor: gkr-pam: stashed password to try later in open session
07:48:14 gdm-session-wor: gkr-pam: unable to locate daemon control file
07:48:10 gdm-session-wor: gkr-pam: no password is available for user
07:48:06 gnome-shell: Registering session with GDM
07:48:04 systemd: Started Session c1 of User gdm.
07:48:04 (systemd): pam_unix(systemd-user:session): session opened for user gdm(uid=126) by (uid=0)
07:48:04 systemd-logind: New session c1 of user gdm.
07:48:04 gdm-session-wor: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=126) by (uid=0)

07:48:41 systemd: fprintd.service: Deactivated successfully.
07:48:08 fprintd: libusb: error [udev_hotplug_event] ignoring udev action change
07:48:06 dbus-daemon: [system] Successfully activated service 'net.reactivated.Fprint'
07:48:06 fprintd: Device responded with error: 789 retry: 1
07:48:06 dbus-daemon: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.34' (uid=126 pid=1938 comm="/usr/bin/gnome-shell " label="unconfined")

[Francois Thirioux (fthx)]

my laptop: ThinkPad P14s
Bus 005 Device 002: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.