Newer Toshiba laptops (like Wez's and mine, the Satellite Pro M30) have hotkeys that are not (yet, anyway) supported by acpid. Attached to this issue report is an updated ebuild for acpid-1.0.3 with Wez's patch. If this gets accepted into portage I will provide an ebuild for his toshkey client utility as well. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 34473 [details] ebuild for acpid 1.0.3 with toshiba-keys-patch
Created attachment 34474 [details] toshiba-keys.patch, used by acpid-1.0.3 ebuild
Created attachment 34475 [details] digest for acpid-1.0.3
*** Bug 45741 has been marked as a duplicate of this bug. ***
I have a working sys-apps/acpid-1.0.3 ebuild here - but I am not sure whether to apply the toshiba-keys.patch since it is not applied upstream and, quite frankly, it's not the right way to do it. Any specialized ACPI kernel module should provide events through /etc/acpi/event - and not some special file.
Bug #33335 contains a request for a package called fnfx (http://fnfx.sourceforge.net) which is a program designed for monitoring the Toshiba specific hotkeys. I suggest we leave sys-apps/acpid unmodified and, if any developers are willing to maintain it, commit fnfx to portage. Comments?
I agree that vanilla acpid should go into the tree and use the FnFX program for toshiba users. The ibm-acpi ebuild does similar things for my thinkpad by creating a kernel module and passing the events to acpid -- it works well without patching up the acpid source. BTW, acpid 1.0.4 is out.
Ah, so it is. Thanks.
Vanilla acpid-1.0.4 is now in portage. Closing as FIXED.
