abrt 1.1.0 detected a crash. architecture: i686 Attached file: backtrace cmdline: audacious2 component: audacious crash_function: magazine_chain_pop_head executable: /usr/bin/audacious2 global_uuid: 73027cfc436586d56d293a615c3041463b95ffb5 kernel: 2.6.33.4-95.fc13.i686.PAE package: audacious-2.2-14.fc13 rating: 4 reason: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. start audacious from command line 2. watch it fail to load and end in Segmentation fault (core dumped) 3.
Created attachment 416905 [details] File: backtrace
Hmm, the backtrace is truncated. It only shows a short fragment of a crash in libglib-2.0 and nothing about Audacious. Does "rpm -V glib2" complete without errors? Is it reproducible for you in a fresh user account? -- And with $HOME/.config/audacious/config and $HOME/.config/audacious/playlist.xspf backed up and removed? Upstream has removed the "scrobbler" plugin in Audacious 2.3, because it isn't maintained anymore and is suspect to causing problems.
With the mention of scrobbler no longer being supported, I went and deleted /usr/lib/audacious/General/scrobbler.so and tried starting Audacious again, successfully. Something about that plugin file was causing the errors. I will test it out and play around with it, but have no issues anymore.
Might be choking on something in $HOME/.config/audacious/scrobblerqueue.txt - I see it's trying to load entries in that file early when the plugin initializes. A queue of stuff it hasn't managed to submit to last.fm during a previous run.
JFYI, scrobbler is back since 2.4 alpha2 (in Rawhide).