`open-fprintd-resume.service` fails to start after resuming from suspend

[xyzshantaram]

It is fixed upon restarting, but fails upon resuming from suspend again. This is on Arch Linux with the python-validity-git AUR package, and my FPR is 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader.

Output of systemctl status open-fprintd-resume.service:

× open-fprintd-resume.service - Restart devices after resume
     Loaded: loaded (/usr/lib/systemd/system/open-fprintd-resume.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Fri 2022-01-07 13:12:24 IST; 13s ago
    Process: 38590 ExecStart=/usr/lib/open-fprintd/resume.py (code=exited, status=1/FAILURE)
   Main PID: 38590 (code=exited, status=1/FAILURE)
        CPU: 39ms

Jan 07 13:12:24 haruki resume.py[38590]:   File "/usr/lib/python3.10/site-packages/validitysensor/init_flash.py", line 113, in init_flash
Jan 07 13:12:24 haruki resume.py[38590]:     info = get_flash_info()
Jan 07 13:12:24 haruki resume.py[38590]:   File "/usr/lib/python3.10/site-packages/validitysensor/flash.py", line 41, in get_flash_info
Jan 07 13:12:24 haruki resume.py[38590]:     assert_status(rsp)
Jan 07 13:12:24 haruki resume.py[38590]:   File "/usr/lib/python3.10/site-packages/validitysensor/util.py", line 12, in assert_status
Jan 07 13:12:24 haruki resume.py[38590]:     raise Exception('Failed: %04x' % s)
Jan 07 13:12:24 haruki resume.py[38590]: Exception: Failed: 0315
Jan 07 13:12:24 haruki systemd[1]: open-fprintd-resume.service: Main process exited, code=exited, status=1/FAILURE
Jan 07 13:12:24 haruki systemd[1]: open-fprintd-resume.service: Failed with result 'exit-code'.
Jan 07 13:12:24 haruki systemd[1]: Failed to start Restart devices after resume.

Output of sudo systemctl start open-fprintd-resume.service:

Job for open-fprintd-resume.service failed because the control process exited with error code.
See "systemctl status open-fprintd-resume.service" and "journalctl -xeu open-fprintd-resume.service" for details.

Output of journalctl -xeu open-fprintd-resume.service:

Jan 07 13:12:24 haruki systemd[1]: open-fprintd-resume.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit open-fprintd-resume.service has entered the 'failed' state with result 'exit-code'.
Jan 07 13:12:24 haruki systemd[1]: Failed to start Restart devices after resume.
░░ Subject: A start job for unit open-fprintd-resume.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit open-fprintd-resume.service has finished with a failure.
░░ 
░░ The job identifier is 3350 and the job result is failed.
Jan 07 13:14:00 haruki systemd[1]: Starting Restart devices after resume...
░░ Subject: A start job for unit open-fprintd-resume.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit open-fprintd-resume.service has begun execution.
░░ 
░░ The job identifier is 3432.
Jan 07 13:14:00 haruki resume.py[38872]: Traceback (most recent call last):
Jan 07 13:14:00 haruki resume.py[38872]:   File "/usr/lib/open-fprintd/resume.py", line 11, in <module>
Jan 07 13:14:00 haruki resume.py[38872]:     o.Resume()
Jan 07 13:14:00 haruki resume.py[38872]:   File "/usr/lib/python3.10/site-packages/dbus/proxies.py", line 141, in __call__
Jan 07 13:14:00 haruki resume.py[38872]:     return self._connection.call_blocking(self._named_service,
Jan 07 13:14:00 haruki resume.py[38872]:   File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 652, in call_blocking
Jan 07 13:14:00 haruki resume.py[38872]:     reply_message = self.send_message_with_reply_and_block(
Jan 07 13:14:00 haruki resume.py[38872]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.22 was not provided by any .service files
Jan 07 13:14:00 haruki systemd[1]: open-fprintd-resume.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit open-fprintd-resume.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 07 13:14:00 haruki systemd[1]: open-fprintd-resume.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit open-fprintd-resume.service has entered the 'failed' state with result 'exit-code'.
Jan 07 13:14:00 haruki systemd[1]: Failed to start Restart devices after resume.
░░ Subject: A start job for unit open-fprintd-resume.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit open-fprintd-resume.service has finished with a failure.
░░ 
░░ The job identifier is 3432 and the job result is failed.

I also tried it with the regular python-validity AUR package (which doesn't seem to have been updated to 0.13 yet?), but that also caused the service with a different error -- I'll post the details in a follow-up comment.

Edit: I'm unable to reproduce that error anymore, it was a USBError from pyusb stating that the device couldn't be found and that it may have been disconnected. Now, both the -git and normal versions report the same error.

[guemidiborhane]

how did you manage to fix this?

[xyzshantaram]

I didn't, it's still broken.

[guemidiborhane]

Sorry I miss understood

…

On Fri, 7 Jan 2022, 8:20 pm Siddharth Singh, ***@***.***> wrote: I didn't, it's still broken. — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7KVNYGORS4LN2QIQGJVUTUU44IHANCNFSM5LOGVKOA> . You are receiving this because you commented.Message ID: ***@***.***>

[l4pa]

i can confirm the issue on fully upgraded Arch, libusb error, i suppose it has to do with upgraded python. reinstalled libusb, no effect. same model of fingerprint reader.

[l4pa]

it only gets fixed for me if both python3-validity and open-fprintd are restarted.

[l4pa]

my log of open-fprintd-resume failure just in case

× open-fprintd-resume.service - Restart devices after resume
Loaded: loaded (/usr/lib/systemd/system/open-fprintd-resume.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-01-12 22:14:20 EET; 8s ago
Process: 4606 ExecStart=/usr/lib/open-fprintd/resume.py (code=exited, status=1/FAILURE)
Main PID: 4606 (code=exited, status=1/FAILURE)
CPU: 46ms

Jan 12 22:14:20 zzz resume.py[4606]: File "/usr/lib/python3.10/site-packages/usb/backend/libusb1.py", line 837, in bulk_write
Jan 12 22:14:20 zzz resume.py[4606]: return self.__write(self.lib.libusb_bulk_transfer,
Jan 12 22:14:20 zzz resume.py[4606]: File "/usr/lib/python3.10/site-packages/usb/backend/libusb1.py", line 938, in __write
Jan 12 22:14:20 zzz resume.py[4606]: _check(retval)
Jan 12 22:14:20 zzz resume.py[4606]: File "/usr/lib/python3.10/site-packages/usb/backend/libusb1.py", line 604, in _check
Jan 12 22:14:20 zzz resume.py[4606]: raise USBError(_strerror(ret), ret, _libusb_errno[ret])
Jan 12 22:14:20 zzz resume.py[4606]: usb.core.USBError: [Errno 19] No such device (it may have been disconnected)
Jan 12 22:14:20 zzz systemd[1]: open-fprintd-resume.service: Main process exited, code=exited, status=1/FAILURE
Jan 12 22:14:20 zzz systemd[1]: open-fprintd-resume.service: Failed with result 'exit-code'.
Jan 12 22:14:20 zzz systemd[1]: Failed to start Restart devices after resume.

[sarlej]

I have same issue, what helps for me as workaround is restarting open-fprintd and python3-validity as l4pa suggested.
Also this issue dosn't happened every time i wake up computer from suspend. It started cca month ago.
My device ID: 138a:0097 Validity Sensors, Inc.
Im using version 0.12-4 from AUR python-validity package
Output of journalctl -u open-fprintd-resume.service

led 18 08:45:47 jntb systemd[1]: Starting Restart devices after resume...
led 18 08:45:47 jntb resume.py[38662]: Traceback (most recent call last):
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/open-fprintd/resume.py", line 11, in <module>
led 18 08:45:47 jntb resume.py[38662]:     o.Resume()
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/dbus/proxies.py", line 141, in __call__
led 18 08:45:47 jntb resume.py[38662]:     return self._connection.call_blocking(self._named_service,
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 652, in call_blocking
led 18 08:45:47 jntb resume.py[38662]:     reply_message = self.send_message_with_reply_and_block(
led 18 08:45:47 jntb resume.py[38662]: dbus.exceptions.DBusException: org.freedesktop.DBus.Python.Exception: Traceback (most recent call last):
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/dbus/service.py", line 715, in _message_cb
led 18 08:45:47 jntb resume.py[38662]:     retval = candidate_method(self, *args, **keywords)
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python-validity/dbus-service", line 74, in Resume
led 18 08:45:47 jntb resume.py[38662]:     init.open_common()
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/validitysensor/init.py", line 29, in open_common
led 18 08:45:47 jntb resume.py[38662]:     init_flash()
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/validitysensor/init_flash.py", line 113, in init_flash
led 18 08:45:47 jntb resume.py[38662]:     info = get_flash_info()
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/validitysensor/flash.py", line 41, in get_flash_info
led 18 08:45:47 jntb resume.py[38662]:     assert_status(rsp)
led 18 08:45:47 jntb resume.py[38662]:   File "/usr/lib/python3.10/site-packages/validitysensor/util.py", line 12, in assert_status
led 18 08:45:47 jntb resume.py[38662]:     raise Exception('Failed: %04x' % s)
led 18 08:45:47 jntb resume.py[38662]: Exception: Failed: 0315
led 18 08:45:47 jntb systemd[1]: open-fprintd-resume.service: Main process exited, code=exited, status=1/FAILURE
led 18 08:45:47 jntb systemd[1]: open-fprintd-resume.service: Failed with result 'exit-code'.
led 18 08:45:47 jntb systemd[1]: Failed to start Restart devices after resume.

[ioanmoldovan95]

I have the same issue as the one described above.
I have solved it by writing a service that runs after resume and restarts open-fprintd and python3-validity services
It's a quick and easy fix until a permanent fix is found
I'll leave the code for this service below for anyone who might need it.

[Unit]
Description=Restart services to fix fingerprint integration
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=oneshot
ExecStart=systemctl restart open-fprintd.service python3-validity.service

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[xyzshantaram]

@ioanmoldovan95 Thanks! I was considering doing something like that myself, you're a lifesaver! <3

[saunite]

I have the same issue as the one described above. I have solved it by writing a service that runs after resume and restarts open-fprintd and python3-validity services It's a quick and easy fix until a permanent fix is found I'll leave the code for this service below for anyone who might need it.

[Unit]
Description=Restart services to fix fingerprint integration
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=oneshot
ExecStart=systemctl restart open-fprintd.service python3-validity.service

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

This worked perfectly for me on a Lenovo T480s running Fedora 36