Ubuntu

Master volume control has no effect on headphones

Reported by Tim Hull on 2007-07-08
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

In Gutsy Tribe 2, changing the master volume control - either by the GNOME panel applet, using the keys on my MacBook keyboard, or in the mixer itself - has no effect on headphone volume. The volume controls DO work for the internal speaker, but not for headphones. It seems logical to have this setting control the volume for BOTH headphones and speakers, as this is typically what is expected on other OSes and distributions of Linux.

Stefano Rivera (stefanor) wrote :

According to bug 63544, in general this isn't solevable, and the best you can do is make the volume keys control both Master and Headphones.

Is there any better way to do this?

Aaron Whitehouse (luna-tick) wrote :

Further to the discussion on Ubuntu-Devel-Discuss:
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-August/001517.html

and especially Matthew Garrett's comment:
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-August/001522.html

A method to solve this would be to:
"Alter the kernel so that it binds the headphone and master channel
together. That's how it's handled on various pieces of hardware."

With any luck, mjg will be able to give some advice on this.

Changed in linux-source-2.6.22:
importance: Undecided → Low
status: New → Confirmed
assignee: nobody → ubuntu-kernel-team
Stefano Rivera (stefanor) wrote :

It appears to be more complex than I thought. In Gutsy beta, the Master controls some speakers in the laptop, and Front, others. Front controls headphones.

So the correct thing to do is select Front & Master for both Gnome Sound settings and the Volume control applet preferences.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Stefano Rivera (stefanor) wrote :

Fixed for me in jaunty. I think having pulseaudio as the default "mixer" has fixed this.

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

Other bug subscribers