Bug 677863

Summary: [abrt] audacious-2.4.3-4.fc14: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: audaciousAssignee: Michael Schwendt <bugs.michael>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: atkac, bugs.michael
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:59efc4ec5ca4ad4f87db3676b17854397338d35f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-24 23:11:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description piio 2011-02-16 06:15:48 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: audacious2
component: audacious
executable: /usr/bin/audacious2
kernel: 2.6.35.11-83.fc14.i686.PAE
package: audacious-2.4.3-4.fc14
reason: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1.Don't remember
time: 1297808743
uid: 500
Comment 1 piio 2011-02-16 06:15:51 UTC 
Created attachment 479025 [details]
File: backtrace
Comment 2 Michael Schwendt 2011-02-16 11:16:53 UTC 
> #0  0x0511618e in ?? ()
> No symbol table info available.

> How to reproduce: 1.Don't remember

Unfortunately, the backtrace you've sent is not detailed enough either. Please try to refresh it in ABRT, and if that doesn't lead to anything, there's nothing that can be done about this.

Perhaps you've updated software while Audacious was running?