Paul, can you elaborate on this?
The thinkpad-brightness-{down,up}.sh scripts appeared in version 0.101 of
acpi-support, which has the following changelog:
acpi-support (0.101) gutsy; urgency=low
* Switch Thinkpad to using ACPI events for magic keys so that
'thinkpad-keys' can go away and save us all from the new Lenovopad
slow NVRAM.
- See 'hotkey-setup' for remapping and initial module loading + setup.
* Extend mask used in 'thinkpad_acpi.modprobe'.
* Replace 'bin/bash' with 'bin/sh' in a couple of files.
/etc/acpi/video_brightnessup.sh in Hardy now is:
#!/bin/bash
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_BRIGHTNESSUP
$ cat /etc/acpi/thinkpad-brightness-up.sh
#!/bin/bash
manufacturer=`dmidecode --string system-manufacturer`
case "$manufacturer" in
LENOVO*)
exit
;;
*)
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_BRIGHTNESSUP
;;
esac
I suspect that the fix is to not handle LENOVO special in
/etc/acpi/thinkpad-brightness-{up,down}.sh.
Would this lead to increasing/decreasing the brightness in two steps per
action, if the video module is loaded (and therefore
/etc/acpi/video_brightnessup.sh gets called, too)?
** Changed in: acpi-support (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
Why isn't thinkpad-brightness-down.sh used for Lenovo thinkpads?
https://bugs.launchpad.net/bugs/161745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
