Bug 596366 – [abrt] crash in pidgin-2.6.6-2.fc12: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)

Bug 596366 - [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 575322

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pidgin (Show other bugs)
Sub Component:
Version:	12
Hardware:	i686 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Warren Togami
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:a2363e6ef38b2bf2e7cae4ccd9f...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-26 12:48 EDT by Amram
Modified:	2010-05-26 14:21 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-05-26 14:21:14 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 (32.32 KB, text/plain) 2010-05-26 12:48 EDT, Amram	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Amram 2010-05-26 12:48:53 EDT

abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pidgin
comment: open with msn messenger
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: a2363e6ef38b2bf2e7cae4ccd9f3064152e79f5c
kernel: 2.6.32.12-115.fc12.i686.PAE
package: pidgin-2.6.6-2.fc12
rating: 3
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. open with msn messenger
2.
3.

Comment 1 Amram 2010-05-26 12:48:56 EDT

Created attachment 416931 [details]
File: backtrace

Comment 2 Stu Tomlinson 2010-05-26 14:21:14 EDT


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

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