Description of problem:
audacious in F18 crash when AOSD plugin is loaded.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start audacious
2. enable AOSD plugin
AOSD plugin should be loaded or at least an error message that AOSD plugin cannot be loaded.
Attach the full output of "audacious -V" when starting it within a terminal. Also attach the backtrace, which ABRT (abrt-gui) should have caught automatically, btw.
The problem seem to be in the config file in [aosd] section.
Up to F17 I had:
Now there are only 4 triggers so the line should be
I'm not sure, but it seems like somewhere in the source files, one does not check the number of triggers.
This is the whole section:
Obviously. Thanks for the detective work!
The trigger config constants have changed between Audacious 3.2.4 and 3.3. One trigger constant has been removed, the other ones have been lowered by one. That causes several parts of the AOSD plug-in crash during array out-of-bounds access.
I've forwarded the bug report upstream: http://redmine.audacious-media-player.org/issues/243
Since there is a work-around (editing the config file) and Audacious 3.3.x at Fedora has passed the development and testing period without anyone reporting this problem before, I'll wait for a response from upstream before releasing an update. There are several ways how to fix this.
Sounds fine. Thank you.
audacious-plugins-3.3.3-4.fc18 has been submitted as an update for Fedora 18.
Thank you. Works fine.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing audacious-plugins-3.3.3-4.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
audacious-plugins-3.3.3-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.