Red Hat Bugzilla – Bug 606094
[abrt] crash in empathy-18.104.22.168: tp_proxy_get_object_path: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Last modified: 2012-08-16 17:46:12 EDT
abrt 1.1.1 detected a crash.
Attached file: backtrace
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created attachment 425446 [details]
*** Bug 609950 has been marked as a duplicate of this bug. ***
*** Bug 631886 has been marked as a duplicate of this bug. ***
OS Release: Fedora release 13 (Goddard)
suspended/resumed my laptop
*** Bug 653096 has been marked as a duplicate of this bug. ***
*** Bug 637734 has been marked as a duplicate of this bug. ***
*** Bug 652057 has been marked as a duplicate of this bug. ***
*** Bug 652990 has been marked as a duplicate of this bug. ***
Upstream would like some additional information:
'Thanks for the bug. I looked at the code and didn't see any obvious reason why
account would be NULL. Can you reproduce this crash? Any chance to get empathy
logs before the crash?'
*** Bug 661392 has been marked as a duplicate of this bug. ***
hmmm, it seems, that the actions, that I described in #661392 don't lead to crash. don't know what was the actual reason. sry.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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: