Description of problem: I happens when I try to enroll a fingerprint on IBM T61 ID 0483:2016 STMicroelectronics Fingerprint Reader Version-Release number of selected component: mate-control-center-1.24.0-3.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: mate-about-me crash_function: set_current_page executable: /usr/bin/mate-about-me journald_cursor: s=6ce089b17a39412aaa797b9a06426b1b;i=2a35f3;b=f5f55da574d6456ba7b87cbd09fb8a88;m=625774aa;t=5a4d458830c63;x=df6e0961c2cba661 kernel: 5.6.8-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 set_current_page at gtkassistant.c:992 #1 compute_next_step at gtkassistant.c:1041 #2 gtk_assistant_next_page at gtkassistant.c:1610 #3 _g_closure_invoke_va at ../gobject/gclosure.c:873 #6 gtk_button_clicked at gtkbutton.c:1541 #7 gtk_button_do_release at gtkbutton.c:1845 #9 gtk_real_button_released at gtkbutton.c:1963 #10 _g_closure_invoke_va at ../gobject/gclosure.c:873 #13 multipress_released_cb at gtkbutton.c:666 #14 _gtk_marshal_VOID__INT_DOUBLE_DOUBLEv at gtkmarshalers.c:4803
Created attachment 1684900 [details] File: backtrace
Created attachment 1684901 [details] File: core_backtrace
Created attachment 1684902 [details] File: cpuinfo
Created attachment 1684903 [details] File: dso_list
Created attachment 1684904 [details] File: environ
Created attachment 1684905 [details] File: exploitable
Created attachment 1684906 [details] File: limits
Created attachment 1684907 [details] File: maps
Created attachment 1684908 [details] File: mountinfo
Created attachment 1684909 [details] File: open_fds
Created attachment 1684910 [details] File: proc_pid_status
Created attachment 1684911 [details] File: var_log_messages
Can you please file out an upstream report? https://github.com/mate-desktop/mate-control-center/issues I don't have a hardware with a fingerprint reader for myself. So, i can't reproduce the issue or help you, sorry.
Also, here is the root cause: ▲ ~ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out ▲ ~ sudo /usr/libexec/fprintd -t (fprintd:343450): libfprint-upekts-CRITICAL **: 22:15:48.449: async msg read failed: transfer timed out
Should I also fill a separate bug for fprintd?
https://bugzilla.redhat.com/show_bug.cgi?id=1832229 fprintd bug filled as well.
https://github.com/mate-desktop/mate-control-center/issues/563 filled an upstream bug
Loosing the enrolled prints is unfortunate but expected.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.