Bug 1831122

Summary: [abrt] mate-control-center: set_current_page(): mate-about-me killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Alex Smirnoff <ark>
Component: mate-control-centerAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: bberg, raveit65.sun, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/623f2dd368d025d4a2d543d132f0631fd5effad6
Whiteboard: abrt_hash:a55f3122406ebaefe5f4a68f0e9342f1c678e193;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:08:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alex Smirnoff 2020-05-04 17:03:19 UTC
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

Comment 1 Alex Smirnoff 2020-05-04 17:03:23 UTC
Created attachment 1684900 [details]
File: backtrace

Comment 2 Alex Smirnoff 2020-05-04 17:03:25 UTC
Created attachment 1684901 [details]
File: core_backtrace

Comment 3 Alex Smirnoff 2020-05-04 17:03:26 UTC
Created attachment 1684902 [details]
File: cpuinfo

Comment 4 Alex Smirnoff 2020-05-04 17:03:28 UTC
Created attachment 1684903 [details]
File: dso_list

Comment 5 Alex Smirnoff 2020-05-04 17:03:30 UTC
Created attachment 1684904 [details]
File: environ

Comment 6 Alex Smirnoff 2020-05-04 17:03:34 UTC
Created attachment 1684905 [details]
File: exploitable

Comment 7 Alex Smirnoff 2020-05-04 17:03:35 UTC
Created attachment 1684906 [details]
File: limits

Comment 8 Alex Smirnoff 2020-05-04 17:03:38 UTC
Created attachment 1684907 [details]
File: maps

Comment 9 Alex Smirnoff 2020-05-04 17:03:39 UTC
Created attachment 1684908 [details]
File: mountinfo

Comment 10 Alex Smirnoff 2020-05-04 17:03:41 UTC
Created attachment 1684909 [details]
File: open_fds

Comment 11 Alex Smirnoff 2020-05-04 17:03:42 UTC
Created attachment 1684910 [details]
File: proc_pid_status

Comment 12 Alex Smirnoff 2020-05-04 17:03:43 UTC
Created attachment 1684911 [details]
File: var_log_messages

Comment 13 Wolfgang Ulbrich 2020-05-04 17:34:50 UTC
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.

Comment 14 Alex Smirnoff 2020-05-04 19:19:44 UTC
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

Comment 15 Alex Smirnoff 2020-05-06 06:02:57 UTC
Should I also fill a separate bug for fprintd?

Comment 16 Alex Smirnoff 2020-05-06 11:13:42 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1832229 fprintd bug filled as well.

Comment 17 Alex Smirnoff 2020-05-06 11:14:22 UTC
https://github.com/mate-desktop/mate-control-center/issues/563 filled an upstream bug

Comment 18 Benjamin Berg 2020-05-06 11:25:25 UTC
Loosing the enrolled prints is unfortunate but expected.

Comment 19 Fedora Program Management 2021-04-29 16:23:35 UTC
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.

Comment 20 Ben Cotton 2021-05-25 16:08:16 UTC
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.