dsd / fprintd

http://reactivated.net/fprint/wiki/Fprintd
GNU General Public License v2.0
20 stars 3 forks source link

Fedora hanging after login - suspect fprintd may be to blame #7

Open KingsdownKid opened 2 weeks ago

KingsdownKid commented 2 weeks ago

Sorry for such a vague message, but I'm getting desperate.

A few days ago (maybe a week?) I discpvered that fprintd now supported my fingerprint reader:

Bus 003 Device 005: ID 1c7a:0587 LighTuning Technology Inc. ETU905A88-E

So, I duly enabled it - oh joy! ;-)

Today I applied an update to my system, as suggested by Software. Usually, this is trouble-free. However, today, following the reboot, I found that the system hung, immediately after login, leaving a blank screen and an non-moving cursor.

I tried various options, including booting into previous versions (from the list presented on the initial boot screen). All to no avail.

Now, the fingerprint reader is built in to my laptop's power switch (it's an ASUS Vivobook. More details available if required.

As part of this, I naturally had to keep pressing the power switch. During one such occasion, I left my finger on the power switch (purely by chance, being lazy(). After a few seconds, the login succeeded (oh joy!). I got a message about the keychain not being unlocked, which I have seen before, but the login then worked just fine.

So, is it possible that the latest fprintd is hanging, and not letting the login proceed? If so, can I get a fix asap (joke). Also, how can I temporarily disable fprintd, to prevent this from happening?

KingsdownKid commented 2 weeks ago

Following advice found on Reddit, I have tried to disable fprintd using:

sudo systemctl disable --now fprintd
sudo systemctl mask fprintd

Hoping this will persist following logout/reboot. Don't want to risk it just yet, since I have work I want to do ;-)

KingsdownKid commented 2 weeks ago

Ho hum, latest news - after following the above steps, I logged out and the problem still occurred, so likely fprintd is not the issue. However, I finally managed to overcome the issue by hitting ctrl-c immediately after entering my password. It's a really scary situation :-(