abrt 1.1.1 detected a crash.
Attached file: backtrace
cmdline: audacious --sm-client-id 102861cb2041d6000127599001700000022100040 --display=:0.0
reason: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created attachment 422460 [details]
Could you please say whether this crash is reproducible? And please explain briefly what you did before it crashed.
That may help with understanding the real problem instead of applying some band-aid. With some configurations (choice of plug-ins and usage patterns), Audacious suffers from sporadic crashes, which haven't been tracked down, but may not reoccur with future releases due to bigger reorganisation of the code.
audacious-2.2-16.fc13 has been submitted as an update for Fedora 13.
Playing Monkey's Audio file.
The tracks are described in the Cue sheet
Trying to view information about a file leads to crash (Alt+I)
audacious-2.2-16.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update audacious'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/audacious-2.2-16.fc13
The problem is not reproduced
audacious-2.2-16.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.