kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

dl.zerocool, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/218598

Title:
  ASUS F8SV: touchpad hotkey not handled

Status in “acpi-support” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: acpi

  Hello,
  Actually there is only one way to turn off the touchpad is by manualy turn it off in Bios.

  Here is details:
  ASUSTeK Computer Inc.
  F8SV
  1.0

  Here is the result of  tail -f /var/log/acpid
  [Thu Apr 17 12:32:39 2008] received event "hotkey ATKD 0000008a 00000001"
  [Thu Apr 17 12:32:39 2008] notifying client 5408[107:116]
  [Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
  [Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
  [Thu Apr 17 12:32:39 2008] completed event "hotkey ATKD 0000008a 00000001"

  
  The hotkey is actually supposed to turn off/on the touchpad.

  
  The other hotkey  (a little man running, sorry I didn't find any description for what is it...)
  Here is the result of  tail -f /var/log/acpid
  [Thu Apr 17 12:46:56 2008] received event "hotkey ATKD 0000005c 00000001"
  [Thu Apr 17 12:46:56 2008] notifying client 5408[107:116]
  [Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
  [Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
  [Thu Apr 17 12:46:56 2008] executing action "/etc/acpi/lockbtn.sh"
  [Thu Apr 17 12:46:56 2008] BEGIN HANDLER MESSAGES
  [Thu Apr 17 12:46:56 2008] END HANDLER MESSAGES
  [Thu Apr 17 12:46:56 2008] action exited with status 0
  [Thu Apr 17 12:46:56 2008] completed event "hotkey ATKD 0000005c 00000001"

  I didn't really know what the lockbtn.sh does
  It apparently just do nothing " Fake Key".

  Well I really hope someone can help me to add the hotkey for to turn on/off touchpad
  Because it's a really anoying thing.

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