Bug 902909 - [abrt] fprintd-0.4.1-4.fc18: fpi_imgdev_report_finger_status: Process /usr/libexec/fprintd was killed by signal 11 (SIGSEGV)
Summary: [abrt] fprintd-0.4.1-4.fc18: fpi_imgdev_report_finger_status: Process /usr/li...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: fprintd
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f1c9fda588ca9c9b7f683ac8411...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-22 17:30 UTC by John Sauter
Modified: 2014-02-05 15:37 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:37:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.06 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: cgroup (154 bytes, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: core_backtrace (1.53 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: dso_list (3.00 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: environ (92 bytes, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: maps (15.39 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: open_fds (474 bytes, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: proc_pid_status (884 bytes, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: smolt_data (3.54 KB, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details
File: var_log_messages (328 bytes, text/plain)
2013-01-22 17:30 UTC, John Sauter
no flags Details

Description John Sauter 2013-01-22 17:30:27 UTC
Version-Release number of selected component:
fprintd-0.4.1-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/fprintd
crash_function: fpi_imgdev_report_finger_status
executable:     /usr/libexec/fprintd
kernel:         3.7.2-204.fc18.x86_64
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 fpi_imgdev_report_finger_status at imgdev.c:122
 #1 sm_await_intr_cb at drivers/upeksonly.c:633
 #2 usbi_handle_transfer_completion at io.c:1483
 #3 handle_bulk_completion at os/linux_usbfs.c:2250
 #4 reap_for_handle at os/linux_usbfs.c:2468
 #5 op_handle_events at os/linux_usbfs.c:2506
 #6 handle_events at io.c:1940
 #7 libusb_handle_events_timeout_completed at io.c:2020
 #8 libusb_handle_events_timeout at io.c:2074
 #9 fp_handle_events_timeout at poll.c:231

Comment 1 John Sauter 2013-01-22 17:30:38 UTC
Created attachment 685337 [details]
File: backtrace

Comment 2 John Sauter 2013-01-22 17:30:41 UTC
Created attachment 685338 [details]
File: cgroup

Comment 3 John Sauter 2013-01-22 17:30:43 UTC
Created attachment 685339 [details]
File: core_backtrace

Comment 4 John Sauter 2013-01-22 17:30:45 UTC
Created attachment 685340 [details]
File: dso_list

Comment 5 John Sauter 2013-01-22 17:30:47 UTC
Created attachment 685341 [details]
File: environ

Comment 6 John Sauter 2013-01-22 17:30:49 UTC
Created attachment 685342 [details]
File: limits

Comment 7 John Sauter 2013-01-22 17:30:51 UTC
Created attachment 685343 [details]
File: maps

Comment 8 John Sauter 2013-01-22 17:30:52 UTC
Created attachment 685344 [details]
File: open_fds

Comment 9 John Sauter 2013-01-22 17:30:54 UTC
Created attachment 685345 [details]
File: proc_pid_status

Comment 10 John Sauter 2013-01-22 17:30:56 UTC
Created attachment 685346 [details]
File: smolt_data

Comment 11 John Sauter 2013-01-22 17:30:57 UTC
Created attachment 685347 [details]
File: var_log_messages

Comment 12 Dario Castellarin 2013-05-21 18:50:02 UTC
It happened when gnome asked me for root privileges to perform an install.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/fprintd
crash_function: fpi_imgdev_report_finger_status
executable:     /usr/libexec/fprintd
kernel:         3.9.3-200.fc18.x86_64
package:        fprintd-0.4.1-4.fc18
reason:         Process /usr/libexec/fprintd was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            0

Comment 13 Fedora End Of Life 2013-12-21 10:42:14 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 14 Fedora End Of Life 2014-02-05 15:37:48 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.