Description of problem: After configuring the system volume using the gnome volume control and its speaker test, I installed rhythmbox and started a radio station playing. I was wearing headphones and deafened. Rhythmbox had the volume at 100% by default. Version-Release number of selected component (if applicable): rhythmbox-0:0.13.1-1.fc14.i686 How reproducible: Did this once. Steps to Reproduce: 1. Clean F14 net install of gnome desktop excluding sound-and-video group. 2. Configure volume using gnome volume control and its speaker test. 3. sudo yum groupinstall sound-and-video 4. Start rhythmbox and play a radio station. Actual results: Volume is 100%. Expected results: Volume matches that of the gnome volume control. IIRC, the default rhythmbox volume used to be 50%. Additional info:
This can be reproduced by adding a new user, logging in as that user, configuring gnome volume control, starting rhythmbox, and playing a radio station. The rhythmbox volume is at 100%. It appears that rhythmbox sets the gnome volume to 100% on it first run. On subsequent runs, rhythmbox does not appear to alter the gnome volume.
(In reply to comment #1) > This can be reproduced by adding a new user, logging in as that user, > configuring gnome volume control, starting rhythmbox, and playing a radio > station. > > The rhythmbox volume is at 100%. > > It appears that rhythmbox sets the gnome volume to 100% on it first run. On > subsequent runs, rhythmbox does not appear to alter the gnome volume. It's even worse than I thought ... Remove headphones. Set the gnome volume and the rhythmbox volume as low as possible, but not muted. Start playing a radio station. Increase the rhythmbox volume slightly. The gnome volume increases. Repeat. Now decrease the rhythmbox volume slightly. The gnome volume does not change. Test notes: I use the mouse scroll wheel to vary the volume and hover the cursor over the volume control icons to see the volume in a tooltip.
Reproduced on a second F14 system: $ rpm -qa 'rhythmbox*' 'gst*' | sort gstreamer-0.10.30-1.fc14.x86_64 gstreamer-debuginfo-0.10.30-1.fc14.x86_64 gstreamer-plugins-bad-free-0.10.20-3.fc14.x86_64 gstreamer-plugins-base-0.10.30-2.fc14.x86_64 gstreamer-plugins-good-0.10.25-1.fc14.x86_64 gstreamer-python-0.10.16-2.fc14.x86_64 gstreamer-rtsp-0.10.5-2.fc14.x86_64 gstreamer-tools-0.10.30-1.fc14.x86_64 rhythmbox-0.13.1-1.fc14.x86_64
I'm guessing that this is related to bug 593039.
Bumping to F15. Reproduced on F15-Alpha after a clean install. $ rpm -qa rhythmbox 'pulse*' 'gst*' | sort gstreamer-0.10.32-4.fc15.x86_64 gstreamer-plugins-bad-free-0.10.21-3.fc15.x86_64 gstreamer-plugins-base-0.10.32-1.fc15.x86_64 gstreamer-plugins-good-0.10.27-3.fc15.x86_64 gstreamer-python-0.10.19-2.fc15.x86_64 gstreamer-rtsp-0.10.7-3.fc15.x86_64 gstreamer-tools-0.10.32-4.fc15.x86_64 pulseaudio-0.9.22-3.fc15.x86_64 pulseaudio-gdm-hooks-0.9.22-3.fc15.x86_64 pulseaudio-libs-0.9.22-3.fc15.x86_64 pulseaudio-libs-glib2-0.9.22-3.fc15.x86_64 pulseaudio-module-bluetooth-0.9.22-3.fc15.x86_64 pulseaudio-module-gconf-0.9.22-3.fc15.x86_64 pulseaudio-module-x11-0.9.22-3.fc15.x86_64 pulseaudio-utils-0.9.22-3.fc15.x86_64 rhythmbox-2.90.1-6.git20110328.fc15.x86_64
(In reply to comment #4) > I'm guessing that this is related to bug 593039. Thanks, Joe. Reassigning to pulseaudio for comment.
Really an awful bug, since this is one of the few ways in which a computer can actually be plain harmful for the user :/ Just ran into the same issue on Arch Linux which recently switched to PulseAudio, and found a workaround in the Arch Linux wiki: https://wiki.archlinux.org/index.php/PulseAudio#Volume_gets_louder_every_time_a_new_application_is_started Insertig/uncommenting the line flat-volumes = no in /etc/pulse/daemon.conf and then running pulseaudio -k seems to disable the "one volume for all" feature, and volume control works for me exactly as expected again (only tried it in Ryhthmbox): There is a system volume and each application has its own separate volume level. Setting the volume in Rhythmbox therefore does not affect the global volume anymore. I wonder why "flat volume=yes" is set to be the default behaviour, especially due to the health risk it poses on the user.
(In reply to comment #7) > Really an awful bug, since this is one of the few ways in which a computer can > actually be plain harmful for the user :/ ... Thanks for your comment and configuration tip. I completely agree. Without changing /etc/pulse/daemon.conf, I tried reproducing this bug in F15 by creating a new user and starting rhythmbox without changing any volumes. The default volume was still loud, but it was not deafening and it seemed consistent with the "Test Speakers" volumes in the Sound Settings dialog. $ rpm -qa rhythmbox 'pulse*' | sort pulseaudio-0.9.22-5.fc15.x86_64 pulseaudio-gdm-hooks-0.9.22-5.fc15.x86_64 pulseaudio-libs-0.9.22-5.fc15.x86_64 pulseaudio-libs-glib2-0.9.22-5.fc15.x86_64 pulseaudio-module-bluetooth-0.9.22-5.fc15.x86_64 pulseaudio-module-gconf-0.9.22-5.fc15.x86_64 pulseaudio-module-x11-0.9.22-5.fc15.x86_64 pulseaudio-utils-0.9.22-5.fc15.x86_64 rhythmbox-2.90.1-10.git20110502.fc15.x86_64
It's still broken: 1. Set the rhythmbox volume to maximum. 2. Observe that the gnome volume is at 100%. 3. Set the rhythmbox volume to a low value like 12%. 4. Observe that the gnome volume is at 100%. 5. Quit rhythmbox. The gnome volume is *still* at 100%.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping