Bug 703310 - [abrt] empathy-2.32.2-1.fc14: tp_proxy_get_object_path: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] empathy-2.32.2-1.fc14: tp_proxy_get_object_path: Process /usr/bin/empa...
Keywords:
Status: CLOSED DUPLICATE of bug 668307
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b73a7cf5e03421767b7cde27a00...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-09 23:24 UTC by Danilo Cestari
Modified: 2012-03-20 17:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:26:36 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (33.48 KB, text/plain)
2011-05-09 23:24 UTC, Danilo Cestari 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Danilo Cestari 2011-05-09 23:24:09 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 34286 bytes
cmdline: empathy
component: empathy
Attached file: coredump, 59416576 bytes
crash_function: tp_proxy_get_object_path
executable: /usr/bin/empathy
kernel: 2.6.35.12-90.fc14.i686
package: empathy-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304982279
uid: 500

How to reproduce
-----
1. In Empathy, I was connected to MSN and Facebook
2. Opened my Accounts, and disabled Facebook
3. Crash!
Comment 1 Danilo Cestari 2011-05-09 23:24:12 UTC 
Created attachment 497937 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:26:36 UTC 
Backtrace analysis found this bug to be similar to bug #668307, closing as duplicate.

Bugs which were found to be similar to this bug: bug #652057, bug #653096, bug #668307

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 668307 ***
Note You need to log in before you can comment on or make changes to this bug.