FP identify is failed when Suspend is invoked after doing WIN+L operation

Bug #1994962 reported by prafulla chandra kota
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fprintd
New
Critical
Unassigned

Bug Description

FP identify is failed when Suspend is invoked after doing WIN+L operation

[steps]
1) user is logged in
2) execute lock option from top right corner of screen (or) use WIN+L button to lock it.
3) Execute Suspend option from top right corner of screen
4) Wait for 2 minutes
5) Observed that FP identify is failed, as host didn’t request device for FP identify call.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.2-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-9005.5+exp.12-oem 6.0.0
Uname: Linux 6.0.0-9005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 16:07:38 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
InstallationDate: Installed on 2022-10-27 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
prafulla chandra kota (prafullakota) wrote :
Revision history for this message
prafulla chandra kota (prafullakota) wrote :

Suspend -1)
    Steps:
1) user is logged in
2) execute suspend function from top right corner via power option.
  Observed FP identity is working fine.

Suspend -2)
   Steps:
1) user is logged in
2) execute lock option from top right corner of screen (or) use WIN+L button to lock it.
3) Execute Suspend option from top right corner of screen
4) Observed that FP identify is failed, as host didn’t request device for FP identify call.

Below is the log from fprintd & libfprintd modules:

(fprintd:15501): fprintd-DEBUG: 15:25:57.487: Released delay inhibitor for sleep.
(fprintd:15501): fprintd-CRITICAL **: 15:25:57.487: Error closing device after disconnect: The device is still busy with another operation, please try again later.
(fprintd:15501): fprintd-DEBUG: 15:26:10.634: Preparing devices for resume
(fprintd:15501): fprintd-DEBUG: 15:26:10.635: Got delay inhibitor for sleep.

Note: This operation works fine on 20.04 OS version

affects: fprintd (Ubuntu) → libfprint-2-tod1-broadcom
Andy Chi (andch)
Changed in libfprint-2-tod1-broadcom:
importance: Undecided → Critical
assignee: nobody → Andy Chi (andch)
Revision history for this message
Andy Chi (andch) wrote :

Verify on other fp device and same issue present.

Oct 28 17:56:20 ubuntu fprintd[6091]: Device reported an error during verify: Cannot run while suspended.
Oct 28 17:56:20 ubuntu dbus-daemon[975]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=977 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 28 17:56:20 ubuntu gdm-fingerprint][6166]: pam_fprintd(gdm-fingerprint:auth): ReleaseDevice failed: Release failed with error: The device is still busy with another operation, please try again later.
Oct 28 17:56:20 ubuntu gdm-fingerprint][6166]: gkr-pam: no password is available for user

affects: libfprint-2-tod1-broadcom → fprintd
Changed in fprintd:
assignee: Andy Chi (andch) → nobody
Revision history for this message
Andy Chi (andch) wrote :

Seems like the usb device is in suspend state, so fprintd will report error.

description: updated
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.