Red Hat Bugzilla – Bug 537108
[abrt] crash detected in empathy-220.127.116.11-3.fc12
Last modified: 2010-12-04 10:48:51 EST
abrt detected a crash.
Comment: Running Empathy and crashed
Attached file: backtrace
reason: Process was terminated by signal 11
Created attachment 369227 [details]
Thank you for the bug report.
Fedora Bugzappers volunteer triage team
*** Bug 539795 has been marked as a duplicate of this bug. ***
*** Bug 541204 has been marked as a duplicate of this bug. ***
*** Bug 548411 has been marked as a duplicate of this bug. ***
*** Bug 549003 has been marked as a duplicate of this bug. ***
*** Bug 556927 has been marked as a duplicate of this bug. ***
How to reproduce
1.Open Empathy and connect.
2.Minimize it to the system tray (mantaining the online status)
3.Double clock on the system tray icon (crash)
First, I minimized Empathy in the system tray (I'm using it both with Jabber and MSN). When I tried to bring up the program, the crash occurred but I noticed that the program is still running in the background (if i click on the Empathy icon, the system tray icon appears again and the connection is still on).
How to reproduce
1.Click on the tray icon right after start
I started empathy, clicked on the tray icon right after start.
Empathy was minimized for a while. I gave it the focus. It restored to normal size, then crashed.
How to reproduce
1.Start som programs on a fresh started system
2.Clicked on empathy tray icon to close empathy contact list, after contact list appear
I started liferea, firefox, thunderbird, skype and empathy. When empathy contact list appears, i chceck it, and click on the tray icon, to close the contact list. After the click, it starts to be unresponsive, and after some seconds it crashes
*** Bug 586801 has been marked as a duplicate of this bug. ***
*** Bug 587061 has been marked as a duplicate of this bug. ***
*** Bug 589800 has been marked as a duplicate of this bug. ***
*** Bug 592593 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:
*** Bug 609163 has been marked as a duplicate of this bug. ***
*** Bug 623873 has been marked as a duplicate of this bug. ***
*** Bug 625684 has been marked as a duplicate of this bug. ***
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.
I am pretty sure all of the bugs I've reported on Fedora were closed by EOLing... I wonder if there is any point to it.