Bug 606553 - [abrt] crash in empathy-2.30.1.1-1.fc13: do_row: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in empathy-2.30.1.1-1.fc13: do_row: Process /usr/bin/empathy was...
Status: CLOSED DUPLICATE of bug 579399
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:289e1511b2f6e83e8398d563044...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-21 23:10 UTC by Matthew P. McCrobie
Modified: 2010-11-09 13:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 13:08:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (106.68 KB, text/plain)
2010-06-21 23:10 UTC, Matthew P. McCrobie
no flags Details

Description Matthew P. McCrobie 2010-06-21 23:10:26 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: empathy
component: empathy
crash_function: do_row
executable: /usr/bin/empathy
global_uuid: 289e1511b2f6e83e8398d563044315c896880afc
kernel: 2.6.33.5-124.fc13.x86_64
package: empathy-2.30.1.1-1.fc13
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Matthew P. McCrobie 2010-06-21 23:10:28 UTC
Created attachment 425771 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:08:23 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:08:23 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 #579399.

Sorry for the inconvenience.


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