After the upgrade from audacious 2.0.1 to 2.1, I started seeing this. This did not happen at the same time as a kernel upgrade, so I feel fairly justified in seeing this bug filed against audacious.
-- John -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
