Comment 3 for bug 1966795

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")