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

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

Summary:	[abrt] crash in pidgin-2.7.0-2.fc12: raise: Process /usr/bin/pidgin was kille...

Status:	CLOSED DUPLICATE of bug 593351

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pidgin (Show other bugs)
Sub Component:
Version:	11
Hardware:	x86_64 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:158d257a77cd4897f79140b078f...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-30 23:10 EDT by Slawek Gawlowski
Modified:	2010-05-31 08:15 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-31 08:15:59 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 (41.20 KB, text/plain) 2010-05-30 23:10 EDT, Slawek Gawlowski	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Slawek Gawlowski 2010-05-30 23:10:51 EDT

abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pidgin
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: 158d257a77cd4897f79140b078f019305a402b9c
kernel: 2.6.32.12-115.fc12.x86_64
package: pidgin-2.7.0-2.fc12
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 11

Comment 1 Slawek Gawlowski 2010-05-30 23:10:56 EDT

Created attachment 418144 [details]
File: backtrace

Comment 2 Stu Tomlinson 2010-05-31 08:15:59 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.