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

[Steve Langasek]

On Thu, Mar 15, 2012 at 12:00:49AM -0000, greg wrote:
> > But there *are* exceptions, which is why the package is still around.

> Right, but we haven't these exceptions been fixed yet?

The exceptions are the events for which neither the kernel nor the
freedesktop framework provides handling.  So there's no way to "fix" these
until the upstream stack provides standard handling for touchpad and
wireless toggling keys.

> And why does acpi-support ship so much stuff that is clearly
deprecated?

The handlers that are probably deprecated are mostly those for ASUS and
Toshiba hardware, which no one who works on this package has direct access
to.  If you can confirm which of the other /etc/acpi/events/asus-* handlers
are already handled through the kernel input layer, I'm happy to remove
those as well.

> The problematic events are "asus-brightness-down" and "asus-brightness-
> up".

Could you please run acpi_listen and show the actual ACPI events generated
for each of these keys?  This may be important later in case a different
ASUS model isn't being handled correctly in the kernel yet.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org

-- 
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