Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 579194 - [abrt] crash in empathy-2.28.2-2.fc12: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in empathy-2.28.2-2.fc12: Process /usr/bin/empathy was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 541066
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a1a3f38603ce6e2f5b08f99171c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-03 06:28 UTC by Jazbo
Modified: 2010-05-25 09:11 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (deleted)
2010-04-03 06:28 UTC, Jazbo 		no flags Details
View All

Description Jazbo 2010-04-03 06:28:49 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: empathy
component: empathy
executable: /usr/bin/empathy
kernel: 2.6.32.10-90.fc12.i686.PAE
package: empathy-2.28.2-2.fc12
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jazbo 2010-04-03 06:28:50 UTC 
Created attachment 404276 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:11:56 UTC 

*** This bug has been marked as a duplicate of bug 541066 ***
Comment 3 Karel Klíč 2010-05-25 09:11:56 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 #541066.

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