This bug was fixed in the package acpi-support - 0.126

---------------
acpi-support (0.126) karmic; urgency=low

  * Drop /etc/acpi/start.d/10-save-dmidecode.sh, which is irrelevant given
    the existence of /sys/class/dmi/id/.
  * Drop events/panasonic-brightness-{down,up}, events/panasonic-mute,
    events/panasonic-volume-{down,up}, and panabright.sh, confirmed to be
    implemented now by the panasonic-laptop kernel driver.
  * Drop events/asus-{a6u-touchpad,internet,lock,wireless} and
    events/asus-media-{next,play-pause,prev,stop}, confirmed to be
    implemented by the asus-laptop kernel driver.
  * Drop events/thinkpad-thinkpad and thinkpad-thinkpad.sh, which is also
    implemented in the thinkpad_acpi driver and should have been dropped a
    while ago.
  * Drop /etc/acpi/{ac,battery}.d, which were still being installed.
  * Drop panapower.sh, which seems to have never been used.
  * Clean up /etc/acpi/toshbright.sh, which was meant to be removed back in
    jaunty
  * Clean up /etc/acpi/hibernatebtn.sh, no longer used.
  * Clean up /etc/acpi/wireless.sh, unused since before hardy.
  * debian/preinst: fix the rm_conffile script to correctly handle conffiles
    whose filename is a substring of another conffile in the same package
  * Drop events/video_brightness{down,up}, video_brightness{up,down}.sh: at
    least some platforms that use these ACPI sequences are seeing them
    correctly translated to input events, so those users will see duplicate
    events unless we drop them.  LP: #178860.
  * Add missing dh_shlibdeps call to debian/rules.

 -- Steve Langasek <steve.langa...@ubuntu.com>   Wed, 26 Aug 2009
08:59:55 -0700

** Changed in: acpi-support (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to