Hide Forgot
abrt 1.0.7 detected a crash. architecture: i686 Attached file: backtrace cmdline: empathy component: empathy executable: /usr/bin/empathy kernel: 2.6.31.12-174.2.22.fc12.i686 package: empathy-2.28.2-2.fc12 rating: 4 reason: Process /usr/bin/empathy was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- I had just restarted after applying updates, did not note what was included in the update but was March 2, 2010 1. Attempted to start Empathy from a panel shortcut. 2. ABRT reported a crash 3.
Created attachment 397358 [details] File: backtrace
How to reproduce ----- Comment ----- I just run Empathy when I logged in. (didn't even see the window, just got the crash)
How to reproduce ----- 1. 2. 3.
How to reproduce ----- 1. I'm really not very certain what happened with this bug 2. Sorry can't be of more help 3. Hopefully a can catch what happened if the bug strikes again
How to reproduce ----- So far happened only once. Comment ----- Just started Empathy.
How to reproduce ----- 1. Log in to Fedora12 2. 3.
Comment ----- Simply log on gdm ...
How to reproduce ----- 1.Start prior to desktop being completely loaded. 2. 3.
How to reproduce ----- 1.crashed when i started the computer 2. 3.
How to reproduce ----- 1. Login to Fedora 2. 3.
How to reproduce ----- 1. just starting empathy (the first time ever) 2. 3.
*** Bug 585551 has been marked as a duplicate of this bug. ***
*** Bug 586245 has been marked as a duplicate of this bug. ***
*** Bug 586587 has been marked as a duplicate of this bug. ***
*** Bug 587013 has been marked as a duplicate of this bug. ***
*** Bug 587014 has been marked as a duplicate of this bug. ***
*** Bug 589021 has been marked as a duplicate of this bug. ***
*** Bug 589365 has been marked as a duplicate of this bug. ***
*** Bug 591033 has been marked as a duplicate of this bug. ***
*** Bug 591256 has been marked as a duplicate of this bug. ***
*** Bug 592067 has been marked as a duplicate of this bug. ***
*** Bug 592393 has been marked as a duplicate of this bug. ***
*** Bug 592618 has been marked as a duplicate of this bug. ***
*** Bug 592774 has been marked as a duplicate of this bug. ***
*** Bug 593315 has been marked as a duplicate of this bug. ***
*** Bug 593457 has been marked as a duplicate of this bug. ***
*** Bug 594576 has been marked as a duplicate of this bug. ***
*** Bug 594934 has been marked as a duplicate of this bug. ***
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.