> Date: Sun, 23 Mar 2014 10:50:21 +0100 > From: Remi Locherer <[email protected]> > > On Sat, Mar 22, 2014 at 04:31:22PM -0600, Theo de Raadt wrote: > > > > Date: Sat, 22 Mar 2014 21:49:19 +0100 (CET) > > > > From: [email protected] > > > > > > > > With the snapshot from March 22 the volume keys on my ThinkPad > > > > x201 do not work anymore. mixerctl still works. Before I was > > > > running the snapshot from Feb 3 with which the volume keys > > > > worked. > > > > > > The volume keys still work. What changed is that the volume keys no > > > longer control the hardware mixer directly anymore when you're running > > > X. Instead the volume key events are passed to whatever X application > > > is running. If you're running mplayer, you'll see that the volume > > > keys still control the volume and give you feedback on the screen. If > > > you run gnome, you'll see something similar. > > > > > > The problem you might experience is that the x201 boots up with the > > > hardware mixer set to a fairly low level. And the software volume > > > control in most X applications won't change it so you won't be able to > > > go any higher by just pressing the volume keys. > > When several X applications are running which one should get the event?
Good question. Typically the application that has focus gets the events, but other applications (window manager?) can steal them. > I cranked outputs.master to 200 and tested with smplayer and aqualung > both playing something. The volume keys had no audible nor visual effect. Try xev(1). The audio keys should show up as XF86AudioMute, XF86AudioLowerVolume and XF86AudioRaiseVolume. > I'm using cwm. Does this make a difference? Possibly. > The mute key works as expected tough mixerctl said outputs.master.mute=off > while the speaker was muted. The mute key on the Thinkpads seems to be special in that it mutes in hardware behind the back of the OS. Possibly acpithinkpad(4) is responsible for this. > > So we should take all our hardware mixers, and crank them to full > > volume right at boot time. > > > > Except that would be bad. So this indicates that the new mixer layer > > has a problem. > > The old behaviour where the volume keys manipulated outputs.master was > more intuitive to me. Except that in the old model X would also see the events and also muck around with the volume settings.
