audacious does not restore volume level

Bug #390632 reported by Martin Emrich
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: audacious

After starting audacious and playing music, the volume control button is at the same position as it was when I exited audacious, but the volume itself is is almost completely down. When I then move the volume slider just a little bit, the volume is set to the "right" level corresponding to the slider position.

Revision history for this message
Martin Emrich (emme) wrote :

Update: The volume does not only reset when audacious is started, but also when I skip manually to the next song. Then I have to move the volume control a little bit back and forth to restore my desired volume setting.

Revision history for this message
enb (elitenoobboy) wrote :

I encountered the volume level changing bug only in pulseaudio 1.15, however, in 1.14, audacious' volume level only changes when it is started, not when changing songs.

Revision history for this message
schlehmil (mail-schlehmil) wrote :

I have the same issue with audacious 2.1-1ubuntu1 and pulseaudio 1:0.9.19-0ubuntu4. The only thing that is restored when audacious is restarted is the mute state (previously set in gnome volume control for audacious) but not the volume level.

Revision history for this message
enb (elitenoobboy) wrote :

The latest release (from here: http://hg.atheme.org/) fixes the volume changing bugs when using the pulseaudio output plugin in ubuntu.

Revision history for this message
Benjamin Drung (bdrung) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test Audacious 2.3 from the latest stable Ubuntu version (10.04) or the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect #390632, and any other logs that are relevant for this particular issue.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in audacious (Ubuntu):
status: New → Incomplete
Revision history for this message
Benjamin Drung (bdrung) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Benjamin Drung (bdrung) wrote :

According to enb in comment #4 was this bug fixed upstream and should be fixed in Ubuntu 10.04.

Changed in audacious (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.