Bug 594990 - [abrt] crash in pidgin-2.6.6-2.fc12: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in pidgin-2.6.6-2.fc12: raise: Process /usr/bin/pidgin was kille...
Status: CLOSED DUPLICATE of bug 593351
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d70ac3d54e3de40a6163bded66...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-22 15:22 UTC by Benjamin Bellec
Modified: 2010-05-23 15:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-23 15:58:47 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 (34.04 KB, text/plain)
2010-05-22 15:22 UTC, Benjamin Bellec 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Benjamin Bellec 2010-05-22 15:22:24 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/pidgin --session 10d4c5c6d7000127082872700000017960018 --display :0.0
comment: Pidgin crash when I was AFK so I can't explain the condition of the crash. I was connected on my accounts Gmail Talk and Facebook.
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: 8d70ac3d54e3de40a6163bded669b5b413a4be8e
kernel: 2.6.32.12-115.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 1 Benjamin Bellec 2010-05-22 15:22:27 UTC 
Created attachment 415871 [details]
File: backtrace
Comment 2 Stu Tomlinson 2010-05-23 15:58:47 UTC 

*** This bug has been marked as a duplicate of bug 593351 ***
Note You need to log in before you can comment on or make changes to this bug.