Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 594518 - [abrt] crash in pidgin-2.6.6-2.fc12: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
[abrt] crash in pidgin-2.6.6-2.fc12: raise: Process /usr/bin/pidgin was kille...
Status: CLOSED DUPLICATE of bug 593351
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
abrt_hash:4950550aae6b5504efc41a00be2...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-20 17:56 EDT by John Knight
Modified: 2010-05-23 11:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-23 11:57:40 EDT
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 (33.29 KB, text/plain)
2010-05-20 17:56 EDT, John Knight
no flags Details

  None (edit)
Description John Knight 2010-05-20 17:56:26 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pidgin
comment: Received a gtalk message (person was on android g1 gtalk client at the same time abrt caught the error if that helps at all .
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: 4950550aae6b5504efc41a00be26a779dbddfa3a
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)

How to reproduce
-----
1. happened rather randomly
2.
3.
Comment 1 John Knight 2010-05-20 17:56:27 EDT
Created attachment 415532 [details]
File: backtrace
Comment 2 Stu Tomlinson 2010-05-23 11:57:40 EDT

*** 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.