Since this bug was filed, Audacious 2.1 is now Audacious 2.4 in Maverick and this bug does not occur, so I suspect it's been fixed elsewhere along the line.
Since this bug was filed, Audacious 2.1 is now Audacious 2.4 in Maverick and this bug does not occur, so I suspect it's been fixed elsewhere along the line.