Bug 594449 - [abrt] crash in empathy-2.28.2-2.fc12: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
[abrt] crash in empathy-2.28.2-2.fc12: Process /usr/bin/empathy was killed by...
Status: CLOSED DUPLICATE of bug 547865
Product: Fedora
Classification: Fedora
Component: empathy (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-20 13:31 EDT by Jeff Frontz
Modified: 2010-05-25 05:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 05:13:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (18.20 KB, text/plain)
2010-05-20 13:31 EDT, Jeff Frontz
no flags Details

  None (edit)
Description Jeff Frontz 2010-05-20 13:31:13 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: empathy
component: empathy
executable: /usr/bin/empathy
global_uuid: a499e3def2e1dd0f0447682ac4f6551f03dce028
package: empathy-2.28.2-2.fc12
rating: 3
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1.first-ever use
2.open app from applications->internet menu
3.cancel setup
4.close window (causing icon to appear at top menu bar)
5. select "quit" from right-clicking on application's menu bar icon
6. fall down, go boom.
Comment 1 Jeff Frontz 2010-05-20 13:31:15 EDT
Created attachment 415478 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:13:21 EDT

*** This bug has been marked as a duplicate of bug 547865 ***
Comment 3 Karel Klíč 2010-05-25 05:13:21 EDT
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 #547865.

Sorry for the inconvenience.

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