Comment # 4 on bug 1207788 from
Created attachment 864640 [details]
journal

Relevant pieces in the log:

> Jan 29 21:48:14 ares.mittagstun.de dbus-daemon[1734]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.25' (uid=460 pid=2752 comm="/usr/bin/gnome-shell ")
> Jan 29 21:48:14 ares.mittagstun.de fprintd[3222]: Device responded with error: 789 retry: 1
> Jan 29 21:48:17 ares.mittagstun.de gdm-fingerprint][3354]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[martin] ruser=[<unknown>] rhost=[<unknown>]
> ...

fprintd is started, lots of pam_sm_authenticate messages. I *think* this
corresponds to the issue occuring after boot (it's not the scene I recorded in
the video).

> Jan 29 21:49:06 ares.mittagstun.de systemd[1]: fprintd.service: Deactivated successfully.
> Jan 29 21:49:17 ares.mittagstun.de dbus-daemon[1734]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.82' (uid=0 pid=3456 comm="/bin/login -p --        ")
> Jan 29 21:49:19 ares.mittagstun.de systemd-logind[2596]: New session 2 of user martin.

I switched to console 2 and logged in succesfully. Tried some commands on the
console. I don't think they made a difference.

> Jan 29 21:49:55 ares.mittagstun.de systemd[1]: fprintd.service: Deactivated successfully.
> Jan 29 21:50:34 ares.mittagstun.de dbus-daemon[1734]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.25' (uid=460 pid=2752 comm="/usr/bin/gnome-shell ")
> Jan 29 21:50:40 ares.mittagstun.de systemd-logind[2596]: New session 4 of user martin.
> Jan 29 21:50:40 ares.mittagstun.de systemd[1]: Started Session 4 of User martin.
> Jan 29 21:50:40 ares.mittagstun.de gdm-password][3896]: pam_unix(gdm-password:session): session opened for user martin by (uid=0)

Now the graphical login worked. Fingerprint authentication did not (it's
usually about 50:50 on this system), but I was able to log in using my
password.


You are receiving this mail because: