[Bug 955176] Re: Brightness hotkeys misdetected on Eee Pc

[Steve Langasek]

> ACPI events, bare for a few exceptions, are now handled either
> directly by the kernel input layer, or other subsystems, like UPower.

But there *are* exceptions, which is why the package is still around.

Could you tell us which ACPI events are the ones getting duplicate
handling on your system, so we can remove the handlers from the package?

** Changed in: acpi-support (Ubuntu)
       Status: New => Incomplete

** Changed in: acpi-support (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to acpi-support in Ubuntu.
https://bugs.launchpad.net/bugs/955176

Title:
  Brightness hotkeys misdetected on Eee Pc

Status in “acpi-support” package in Ubuntu:
  Incomplete

Bug description:
  The acpid scripts that ship with acpi-support misdetect the brightness
  keys on the Eee PC 901 (and probably most other models, as the ACPI
  events are very similar). Both keys, brightness up and down, are
  detected as brightness down. On the other hand, brightness events are
  already handled by eeepc_laptop, so any additional handling by acpi-
  support is harmful and results in crazy behaviour if one presses the
  keys. Removing the acpi-support package solves the issue.

  But, the real WTF is, why does Ubuntu *still* ship acpi-support, and
  acpid? The hacky scripts it uses are largely outdated and cause more
  issues than they solve. ACPI events, bare for a few exceptions, are
  now handled either directly by the kernel input layer, or other
  subsystems, like UPower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/955176/+subscriptions