abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/libexec/fprintd component: fprintd executable: /usr/libexec/fprintd kernel: 2.6.31.5-127.fc12.i686 package: fprintd-0.1-15.git04fd09cfa.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 379695 [details] File: backtrace
Could you please install the missing debuginfo packages and regenerate the backtrace of the crash?
which packages are needed?
The packages are listed in the backtrace you posted above, such as: Debuginfo absent: 0c29704d80ea28bc608223ffb415753f8902a636 So this command should do the trick: debuginfo-install 0c29704d80ea28bc608223ffb415753f8902a636 The abrt UI should also tell you what you need to type.
nope, abrt does not suggest installing any new packages (i usually do, when it lists smth like 'debuginfo-install firefox', etc) and running 'debuginfo-install 0c29704d80ea28bc608223ffb415753f8902a636' yields: > No debuginfo packages available to install any thoughts?
fprintd and glib2's debuginfo packages are missing to start with.
it said that glib2 debuginfo had already been installed. fprintd debuginfo and a couple of other packages were installed, then i refreshed the abrt report, but i don't think it did any good :) https://bugzilla.redhat.com/show_bug.cgi?id=550142
*** Bug 550142 has been marked as a duplicate of this bug. ***
The duplicate patch actually worked fine, and the error is because fprintd cannot get on the D-Bus. Try running fprintd as root on your system, it will give you a better error.
actually, error for fprintd is not shown in abrt, unless abrt-gui is run as root. so, i suspect that the error was produced by a root as well running 'fprintd' from command line does not work: "Command not found."...
(In reply to comment #10) > actually, error for fprintd is not shown in abrt, unless abrt-gui is run as > root. so, i suspect that the error was produced by a root as well > running 'fprintd' from command line does not work: "Command not found."... As root, run /usr/libexec/fprintd This should tell you why it cannot connect to D-Bus. I've also committed this upstream, so that it won't abort() on errors: commit 7872479415c6b83c6dd1328f306c6a63a90a17da Author: Bastien Nocera <hadess> Date: Tue Aug 17 15:34:20 2010 +0100 Change g_errors to g_warnings So as to avoid aborts when D-Bus isn't available. https://bugzilla.redhat.com/show_bug.cgi?id=549484
Version 0.2.0 of libfprint and fprintd is now in F12 updates.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.