Fingerprint Reader not working after reboot / resume (tried the fix #3 - different issue) #128

Activity

1. uunicorn commented on Jun 8, 2022

   

   uunicorn

   on Jun 8, 2022

   Owner

   More actions

   Hi, can you share the systemctl status for open-fprintd-suspend.service and open-fprintd-resume.service services?
2. tenjinsoftware commented on Jun 8, 2022

   

   tenjinsoftware

   on Jun 8, 2022

   Last edited by tenjinsoftware

   Author

   More actions

   Hi,

   Thanks for the reply. Here is the additional information:

   [darren@tenjin-fedora ~]$ sudo systemctl status open-fprintd-suspend.service
   [sudo] password for darren:
   ○ open-fprintd-suspend.service - Restart devices after resume
   Loaded: loaded (/usr/lib/systemd/system/open-fprintd-suspend.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
   [darren@tenjin-fedora ~]$

   [darren@tenjin-fedora ~]$ sudo systemctl status open-fprintd-resume.service
   ○ open-fprintd-resume.service - Restart devices after resume
   Loaded: loaded (/usr/lib/systemd/system/open-fprintd-resume.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
   [darren@tenjin-fedora ~]$

   When I reboot or resume, manually restarting either open-fprintd-resume.service or python3-validity.service restores the fingerprint reader to working.

   I'm quite new to this stuff, so might be a silly question, but there are two additional services that seem to do the same thing: open-fprintd-restart-after-resume.service and python3-validity-restart-after-resume.service, is it possible there is a clash as it looks like the services are being restarted twice?

   D.
3. uunicorn commented on Jun 8, 2022

   

   uunicorn

   on Jun 8, 2022

   Owner

   More actions

   I don't know where open-fprintd-restart-after-resume.service and python3-validity-restart-after-resume.service came from. open-fprintd-suspend.service and open-fprintd-resume.service on the other hand are supposed to be a part of open-fprintd package. They are not designed to restart anything, rather they are there to notify the driver service (python3-validity) that computer went to sleep and the device needs to be re-initialized when it comes back.

   From what I can see, both open-fprintd-suspend.service and open-fprintd-resume.service are disabled on your computer for some reason. Can you try to enable them and remove all these "restart-after-resume" services? Make sure you are using the latest python-validity version, as there was a fix related to suspend/resume recently. I'm not sure who's maintaining Fedora packaging for this project, but it would be nice to incorporate this fix. Also, find out why open-fprintd-{suspend,resume}.service are disabled on Fedora by default.

   I'm not very familiar with the Fedora packaging system and I don't have anywhere to test, so I'm hoping someone with more experience can pick this up.
4. tenjinsoftware commented on Jun 9, 2022

   

   tenjinsoftware

   on Jun 9, 2022

   Last edited by tenjinsoftware

   Author

   More actions

   Thanks again for your help.

   It's all working now. In case anyone finds this thread I thought I'd add some info.

   Bit of context: I'm just getting back into Linux after many years (I first played with Linux in the Red Hat days c. 2000...). I'm pretty rusty. I'm running a Fedora 36 installation on a Lenovo Thinkpad T470s now.

   For "ease" I tried to install the libprintf code (https://github.com/3v1n0/libfprint/) via Snap as the README said it was "for any distro". That failed at one of the steps.

   I then installed this code as per the Fedora instructions and enrolled my fingerprint, and that initially seemed to work fine.

   However, as soon as I went into suspend or rebooted everything stopped working.

   How it was fixed:

   1. i think the Snap install left a couple of dodgy services running, so as per uunicorn's suggestion above I disabled them both and removed the service files:

   i. sudo systemctl disable open-fprintd-restart-after-resume.service
   ii. sudo systemctl disable python3-validity-restart-after-resume.service

   2. I applied the workaround "# 3" from the other thread on this forum (Fix for "Fingerprint not working after waking up from suspend" doesn't work on Fedora 36 #127):

   Change "/usr/lib/systemd/system/open-fprintd-resume.service" to this:
   
   [Unit]
   Description=Restart devices after resume
   After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target
   
   [Service]
   Type=oneshot
   #ExecStart=/usr/lib/open-fprintd/resume.py
   ExecStart=systemctl restart open-fprintd.service python3-validity.service
   
   [Install]
   WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target
   
   

   3. The open-fprintd-suspend.service, open-fprintd-resume.service, and python3-validity.service services were not enabled properly for some reason. I did this:

   i. sudo systemctl daemon-reload
   ii. sudo systemctl enable open-fprintd-suspend.service
   iii. sudo systemctl enable open-fprintd-resume.service
   iv. sudo systemctl enable python3-validity.service
   v. sudo systemctl restart open-fprintd-suspend.service
   vi. sudo systemctl restart open-fprintd-resume.service
   vii. sudo systemctl restart python3-validity.service
   viii. I then ran "sudo systemctl status " on all the services above to check they are running.

   4. Rebooted and suspended, and all working.

   I'm still learning, so there might be quicker ways to do some of this, but all I can say is that this worked for me.

   Darren.
5. uunicorn commented on Jun 9, 2022

   

   uunicorn

   on Jun 9, 2022

   Owner

   More actions

   Hi Darren,

   I applied "fix 3" from the other thread on this forum

   This is not a fix, it's a workaround. As someone mentioned, it is not how things supposed to work and should no longer be required with the latest version of python-validity.
6. tenjinsoftware commented on Jun 9, 2022

   

   tenjinsoftware

   on Jun 9, 2022

   Author

   More actions

   Hi,

   Thanks for the catch, you are right, I have updated my comments to reflect the correction.

   D.
7. maru-sama commented on Nov 16, 2022

   

   maru-sama

   on Nov 16, 2022

   Last edited by maru-sama

   More actions

   Hello,
   I just updated from Ubuntu 22.04 to 22.10 and I a facing the same issues with my Lenovo t470s. After a suspend/resume cycle the reader is no longer available.
   I tried to figure out the differences between the two running the same kernel and found out the following.

   When you suspend under 22.04 and then resume the USB connected fingerprint reader gets "RESET".
   If you do the same with 22.10 then the reader is not "RESET" but it gets removed and then added again as a new device. As a result it is no longer available under the old location since it is per definition a new device.
   Since this is happening with the same kernel it has be the a change in the runtime services but with 1500 updates this is difficult to pinpoint.

   The workaround with restarting the service of course works in this case, but I wonder if a reconnect of the sensor can be handled as well without the need to restart everything.
8. maru-sama commented on Nov 16, 2022

   

   maru-sama

   on Nov 16, 2022

   More actions

   Hi,

   A small update on this while looking at differences, between the two versions I saw that the "power/persist" flag is set to "0" for the newer distribution. As a result the device gets reconnected on resume. I changed the config to always set persist to 1 and now it behaves correctly and works without any workarounds.
9. maru-sama commented on Nov 17, 2022

   

   maru-sama

   on Nov 17, 2022

   More actions

   I found out why the persist is set to 0 in the first place. Recent udev releases have an updated hwdb which lists (at least) my fingerprint sensor as unsupported and sets the flag to 0. I manually put in an exception for my sensor and set this to 0. So now the sensor works as before. To check if this is happening for your sensor as well take a look at /lib/udev/hwdb.d/60-autosuspend-fingerprint-reader.hwdb and check if our sensor is listed there.
10. 4rc0s commented on Feb 20, 2023

    

    4rc0s

    on Feb 20, 2023

    More actions

    I found out why the persist is set to 0 in the first place. Recent udev releases have an updated hwdb which lists (at least) my fingerprint sensor as unsupported and sets the flag to 0. I manually put in an exception for my sensor and set this to 0. So now the sensor works as before. To check if this is happening for your sensor as well take a look at /lib/udev/hwdb.d/60-autosuspend-fingerprint-reader.hwdb and check if our sensor is listed there.

    In that file on my system (Mint 21.1) everything is set to ID_AUTOSUSPEND=1. You said, " I manually put in an exception for my sensor and set this to 0."

    lsusb lists my sensor as 06cb:009a which is apparently included in the "known unsupported devices" as usb:v06CBp009A*

    Do I comment out it's listing in the unsupported section and add a new entry with ID_AUTOSUSPEND=0?
11. maru-sama commented on Feb 23, 2023

    

    maru-sama

    on Feb 23, 2023

    More actions

    I found out why the persist is set to 0 in the first place. Recent udev releases have an updated hwdb which lists (at least) my fingerprint sensor as unsupported and sets the flag to 0. I manually put in an exception for my sensor and set this to 0. So now the sensor works as before. To check if this is happening for your sensor as well take a look at /lib/udev/hwdb.d/60-autosuspend-fingerprint-reader.hwdb and check if our sensor is listed there.

    In that file on my system (Mint 21.1) everything is set to ID_AUTOSUSPEND=1. You said, " I manually put in an exception for my sensor and set this to 0."

    lsusb lists my sensor as 06cb:009a which is apparently included in the "known unsupported devices" as usb:v06CBp009A*

    Do I comment out it's listing in the unsupported section and add a new entry with ID_AUTOSUSPEND=0?

    Hello I wrote a small howto some time ago of how to fix the issue https://mike.it-loops.com/item/32 This was more for myself so I do not forget how I fixed it.
12. ChonkaLoo commented on Nov 11, 2023

    

    ChonkaLoo

    on Nov 11, 2023

    More actions

    Worked for me as well on a X270, had the same fingerprint reader as you @maru-sama but on Debian 12. The override file and update to systemd-hwdb worked like a charm. Thank you for nice tutorial on your site! God I love the open-source community🥰
13. YovanggaAnandhika commented on Oct 25, 2024

    

    YovanggaAnandhika

    on Oct 25, 2024

    Last edited by YovanggaAnandhika

    More actions

    @tenjinsoftware .i have recomendation for if finger not working after resume/suspend/reboot

    I looked at the resume and suspend scripts crashing. because the open-fprintd and python3 validity services are not running perfectly. so when I Tried With Sequence

    1. restart open-fprintd service
    2. restart pyhton3-validity service.

    they must be running so that libusb does not error

    Create Costum Script Bash

    create a file /usr/local/bin/open-fprintd-resume.sh

    allow execution +x /usr/local/bin/open-fprintd-resume.sh

    #!/bin/sh
    
    set -e  # Exit immediately if a command exits with a non-zero status.
    
    # Restart the open-fprintd service and wait for it to complete.
    if /bin/systemctl restart open-fprintd; then
        echo "open-fprintd restarted successfully."
    else
        echo "Failed to restart open-fprintd."
        exit 1  # Exit if the restart fails.
    fi
    
    # Restart the python3-validity service and wait for it to complete.
    if /bin/systemctl restart python3-validity; then
        echo "python3-validity restarted successfully."
    else
        echo "Failed to restart python3-validity."
        exit 1  # Exit if the restart fails.
    fi
    
    # Run the Python script and wait for it to complete.
    if /usr/lib/open-fprintd/resume.py; then
        echo "resume.py executed successfully."
    else
        echo "Failed to execute resume.py."
        exit 1  # Exit if the script fails.
    fi
    

    create a file /usr/local/bin/open-fprintd-suspend.sh

    allow execution +x /usr/local/bin/open-fprintd-suspend.sh

    #!/bin/sh
    
    set -e  # Exit immediately if a command exits with a non-zero status.
    
    # Restart the open-fprintd service and wait for it to complete.
    if /bin/systemctl restart open-fprintd; then
        echo "open-fprintd restarted successfully."
    else
        echo "Failed to restart open-fprintd."
        exit 1  # Exit if the restart fails.
    fi
    
    # Restart the python3-validity service and wait for it to complete.
    if /bin/systemctl restart python3-validity; then
        echo "python3-validity restarted successfully."
    else
        echo "Failed to restart python3-validity."
        exit 1  # Exit if the restart fails.
    fi
    
    # Run the Python script and wait for it to complete.
    if /usr/lib/open-fprintd/suspend.py; then
        echo "resume.py executed successfully."
    else
        echo "Failed to execute resume.py."
        exit 1  # Exit if the script fails.
    fi
    

    Modify Systemd Suspend / Resume

    open and modify suspend
    in file /usr/lib/systemd/system/open-fprintd-suspend.service

    [Unit]
    Description=Restart devices after resume
    After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/local/bin/open-fprintd-suspend.sh
    
    [Install]
    WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

    open and modify resume
    in file /usr/lib/systemd/system/open-fprintd-resume.service

    [Unit]
    Description=Restart devices after resume
    After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/local/bin/open-fprintd-resume.sh
    
    [Install]
    WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

    Run Refresh Service

    Refresh Daemon sudo systemctl daemon-reload

    Enable All Service :

    sudo systemctl enabled open-fprintd-suspend
    sudo systemctl enabled open-fprintd-resume
    

    and try reboot.

    🎉React with 🎉4Reacted by Moh Anif Yuliansyah, Yovangga Anandhika, Lukas Probsthain and Attila Ujvarosy