Bug 709773 - [abrt] telepathy-haze-0.4.0-2.fc14: peer_connection_find_by_type: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
Summary: [abrt] telepathy-haze-0.4.0-2.fc14: peer_connection_find_by_type: Process /us...
Keywords:
Status: CLOSED DUPLICATE of bug 575462
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-haze
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6896e9212bd38c9a5530016d20c...
: 655466 657696 666482 668787 671103 767029 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-01 15:28 UTC by Danny Michel
Modified: 2012-03-30 13:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 13:01:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (15.43 KB, text/plain)
2011-06-01 15:28 UTC, Danny Michel
no flags Details

Description Danny Michel 2011-06-01 15:28:47 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 15802 bytes
cmdline: /usr/libexec/telepathy-haze
comment: Just turned my computer on. Happened out of nowhere
component: telepathy-haze
Attached file: coredump, 9973760 bytes
crash_function: peer_connection_find_by_type
executable: /usr/libexec/telepathy-haze
kernel: 2.6.35.13-91.fc14.x86_64
package: telepathy-haze-0.4.0-2.fc14
rating: 4
reason: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Turned my computer on
time: 1306935768
uid: 500

Comment 1 Danny Michel 2011-06-01 15:28:49 UTC
Created attachment 502304 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2011-07-12 20:06:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 abrt-bot 2012-03-20 15:27:12 UTC
*** Bug 668787 has been marked as a duplicate of this bug. ***

Comment 4 abrt-bot 2012-03-20 15:27:29 UTC
*** Bug 666482 has been marked as a duplicate of this bug. ***

Comment 5 abrt-bot 2012-03-20 15:27:48 UTC
*** Bug 657696 has been marked as a duplicate of this bug. ***

Comment 6 abrt-bot 2012-03-20 15:27:59 UTC
*** Bug 767029 has been marked as a duplicate of this bug. ***

Comment 7 abrt-bot 2012-03-20 15:28:10 UTC
*** Bug 655466 has been marked as a duplicate of this bug. ***

Comment 8 abrt-bot 2012-03-20 15:28:22 UTC
*** Bug 671103 has been marked as a duplicate of this bug. ***

Comment 9 abrt-bot 2012-03-30 13:01:44 UTC
Backtrace analysis found this bug to be similar to bug #575462, closing as duplicate.

Bugs which were found to be similar to this bug: bug #575462, bug #592731, bug #602041, bug #613384, bug #613818, bug #613820, bug #620611, bug #627546, bug #630582, bug #636807, bug #636811, bug #644314, bug #657093, bug #666482, bug #666710, bug #668787, bug #683338, bug #711208, bug #723457, bug #767029, bug #786707

This comment is automatically generated.

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


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