*** This bug is a duplicate of bug 39098 ***
How exactly did you make the volume-up button trigger both thinkpad-
mixer-up and soundcard-mixer-up ?
I think for edgy what I'll do is have a daemon that listens for changes
to the ALSA state and syncs these back to the hardware.
So the hardware
*** This bug is a duplicate of bug 39098 ***
I did not do anything to trigger this behaviour. Out-of-the box (more-
or-less, as my notebook was installed with the dapper development branch
a long time ago, and is constantly updated), I already had the weird
behaviour, that the Thinkpad buttons
*** This bug is a duplicate of bug 39098 ***
Martin: Okay, I think what you're highlighting is this:
Mute = hardware mute-set regardless
VolumeDown/VolumeUp = Unmute
and this is [almost] the same as 'gnome-settings-daemon', which takes
the first movement (Up or Down) after a mute as also
*** This bug is a duplicate of bug 39098 ***
It was not my intention to highlight this, but now as you explain it,
the behaviour makes sense.
As I see it: lshal -m does not dump events generated by buttons, but
rather what some layer in between makes of the button presses.
My opinion is that
*** This bug is a duplicate of bug 39098 ***
Oops, I forgot: I use both Kubuntu and Ubuntu, Dapper Drake
development branch (my Desktop environment is GNOME, but I installed
KDE, too, and use kontact as my pim...)
Ciao
Martin
--
ibm-acpi volume control unpredictable
*** This bug is a duplicate of bug 39098 ***
Martin: you have a different issue; which is that your keys aren't
doing what you expect them? Can you post the output from running:
lshal -m
when pressing the Up, Down and Mute volume keys and stick that in a new
bug report along with
*** This bug is a duplicate of bug 39098 ***
Hi!
output of lshal -m
:
[EMAIL PROTECTED]:~$ lshal -m
Start monitoring devicelist:
-
pressing down
computer_logicaldev_input condition ButtonPressed = volumedown
computer_logicaldev_input condition
