Bug 631886 - [abrt] empathy-2.30.3-1.fc13: tp_proxy_get_object_path: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] empathy-2.30.3-1.fc13: tp_proxy_get_object_path: Process /usr/bin/empa...
Keywords:
Status: CLOSED DUPLICATE of bug 606094
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1f998e0c8694a62fb4d7beab65b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-08 15:18 UTC by Mark A. Baldridge
Modified: 2010-11-09 16:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:46:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.17 KB, text/plain)
2010-09-08 15:18 UTC, Mark A. Baldridge
no flags Details

Description Mark A. Baldridge 2010-09-08 15:18:37 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: empathy
component: empathy
crash_function: tp_proxy_get_object_path
executable: /usr/bin/empathy
kernel: 2.6.34.6-47.fc13.i686.PAE
package: empathy-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1283956710
uid: 1000

comment
-----
My user ID is reiki33, yet in one of the paths it looks like it might be reiki330, with an extra 0 at the end.  This might be normal, though
Wireless is present, I do not think it was the active link, as I was wired to eth0.

How to reproduce
-----
1. Had an idle chat session open
2. Did the network manager update (which requires a postponed reboot).
3. Crashed on its own without my watching.  Perhaps a new message had appeared.  I did not see one before the message window vanished.

Comment 1 Mark A. Baldridge 2010-09-08 15:18:39 UTC
Created an attachment (id=446010)
File: backtrace

Comment 2 Karel Klíč 2010-11-09 16:46:02 UTC

*** This bug has been marked as a duplicate of bug 606094 ***

Comment 3 Karel Klíč 2010-11-09 16:46:02 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #606094.

Sorry for the inconvenience.


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