Login with fingerprint not working after reboot

Bug #1675856 reported by Robert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I boot my laptop or reboot it and want to log into the gnome-shell with my fingerprint it only loads and then it will load the login screen again.

It recognizes wrong fingers ("please try again") and if I use the correct one I will get the behaviour described above.

After locking the laptop or going to suspend I can unlock it with my fingerprint without any problems.

Requirements:

1) & 2) Further Information:
 - Ubuntu Gnome 16.10
 - Gnome-Shell 3.20.4-0ubuntu2
 - Thinkpad T460 with Fingerprint Scanner
 - Using fprintd (tried Fingerprint-GUI but also didn't work, but I like fprintd more)

3) What you expected to happen

Move finger over fingerprint scanner and log in

4) What happened instead

Moved finger over fingerprint scanner, grey screen and then the login window again.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-shell 3.20.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 24 17:47:27 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-03-24 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Robert (rehni) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and help make Ubuntu better.

Unfortunately, I don't have a fingerprint reader so I'm not sure how to figure out what's not working here.

I'm having trouble understanding your first sentence. Could you try rephrasing? What does "it only loads" mean?

When you say this works after suspend, do you have to be logged in for it to work then?

After logging in, can you then log out and log in with your fingerprint?

Can you find any logs or journal entries about this?

Is the fprintd systemd service running?

Revision history for this message
Robert (rehni) wrote :

Okay I will describe the process after reboot to explain "it only loads":

I select my user and get to the password field. Under the field it says "(or swipe finger)". When I swipe with my finger now all the screen buttons and fields go away (like when I normally login) but instead of showing my desktop I get back to the login window where I can select my user again.

Logging out and back into the session with fingerprint works.

Rebooted now and tried it three times and checked the logs. It seems that this is the error message (appeared three times at login time, I used the logs application and this was in the important section):

gdm-session-wor
Message: pam_ecryptfs: NULL passphrase; aborting
Priority: 3

How can I check if the fprintd systemd service is running at boot time without being logged in?

Revision history for this message
Robert (rehni) wrote :

After each of this log there was another log:

(sd-pam)
Message: pam_unix(systemd-user:session): session closed for user robert
Audit Session: 5
Priority: 6

And the next log entry is this:

gdm-session-wor
Message: pam_ecryptfs: Passphrase file wrapped
Priority: 7

It seems that the passphrase is not set correct after swiping with my finger after boot.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Oh, it looks like you clicked the box during install to encrypt your home directory (it uses ecryptfs). I wonder if that is the problem.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Yes, it looks like that this is the problem. Therefore, I am marking this a duplicate of bug 998367.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.