Bug 631886

Summary: [abrt] empathy-2.30.3-1.fc13: tp_proxy_get_object_path: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mark A. Baldridge <reiki33>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:1f998e0c8694a62fb4d7beab65ba140e31483547
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 16:46:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

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.