Bug 586043 - [abrt] crash in pidgin-2.6.6-2.fc12: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in pidgin-2.6.6-2.fc12: Process /usr/bin/pidgin was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 573286
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2a60741fb0591937a88054dbb22...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 17:11 UTC by Sara L. Uckelman
Modified: 2010-05-25 09:59 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (18.93 KB, text/plain)
2010-04-26 17:11 UTC, Sara L. Uckelman 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Sara L. Uckelman 2010-04-26 17:11:35 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pidgin ^
component: pidgin
executable: /usr/bin/pidgin
global_uuid: 2a60741fb0591937a88054dbb22e3d165f2235b3
kernel: 2.6.32.11-99.fc12.x86_64
package: pidgin-2.6.6-2.fc12
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

comment
-----
type "pidgin ^" into command line (typo for "pidgin &"); recognize that you've made a typo, and hit "ctrl + C".  Watch a segfault appear.

This happens pretty often, but it doesn't happen every time.
Comment 1 Sara L. Uckelman 2010-04-26 17:11:38 UTC 
Created attachment 409236 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:59:47 UTC 

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

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