Bug 615748 – [abrt] crash in audacious-2.2-14.fc12: raise: Process /usr/bin/audacious2 was killed by signal 6 (SIGABRT)

Bug 615748 - [abrt] crash in audacious-2.2-14.fc12: raise: Process /usr/bin/audacious2 was killed by signal 6 (SIGABRT)

Summary:	[abrt] crash in audacious-2.2-14.fc12: raise: Process /usr/bin/audacious2 was...

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

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

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

URL:
Whiteboard:	abrt_hash:ebc895cda93d777b8c4bce61354...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-07-18 08:27 EDT by luke_l
Modified:	2010-08-12 15:53 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-08-12 15:53:51 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 (21.30 KB, text/plain) 2010-07-18 08:27 EDT, luke_l	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description luke_l 2010-07-18 08:27:07 EDT

abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: audacious2 -i gtkui
component: audacious
crash_function: raise
executable: /usr/bin/audacious2
global_uuid: ebc895cda93d777b8c4bce613549ffbf3807ab50
kernel: 2.6.32.16-141.fc12.i686.PAE
package: audacious-2.2-14.fc12
rating: 4
reason: Process /usr/bin/audacious2 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 luke_l 2010-07-18 08:27:22 EDT

Created attachment 432695 [details]
File: backtrace

Comment 2 Michael Schwendt 2010-07-18 09:32:19 EDT

Please don't dump backtraces into bugzilla without adding some comments on how to reproduce a problem and on what you did prior to the crash.

You somehow managed to crash Pulse Audio, but I cannot guess what you did to make that happen.

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