Bug 589400 - [abrt] crash in telepathy-sofiasip-0.6.2-1.fc13: Process /usr/libexec/telepathy-sofiasip was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in telepathy-sofiasip-0.6.2-1.fc13: Process /usr/libexec/telepat...
Keywords:
Status: CLOSED DUPLICATE of bug 589346
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-sofiasip
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2e1abdb754ce252935fe5f97f0a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-06 04:54 UTC by Marcus Specht
Modified: 2010-05-25 09:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:38:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.08 KB, text/plain)
2010-05-06 04:54 UTC, Marcus Specht
no flags Details

Description Marcus Specht 2010-05-06 04:54:41 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-sofiasip
comment: this happened while empathy was running in the background
component: telepathy-sofiasip
executable: /usr/libexec/telepathy-sofiasip
global_uuid: 2e1abdb754ce252935fe5f97f0a57a89a6de9b62
kernel: 2.6.33.3-73.fc13.i686.PAE
package: telepathy-sofiasip-0.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/telepathy-sofiasip was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. this happened while empathy was running in the background
2.
3.

Comment 1 Marcus Specht 2010-05-06 04:54:43 UTC
Created attachment 411808 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:38:50 UTC

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

Comment 3 Karel Klíč 2010-05-25 09:38:50 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 #589346.

Sorry for the inconvenience.


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