I've revised this further in Intrepid. There were some problems with
the original fix, and it turns out that the driver defaults are actually
not good enough for us.
We now take a more conservative approach, and use the driver defaults
except for enabling the few things we seem to need.
This bug was fixed in the package hotkey-setup - 0.1-23ubuntu4
---
hotkey-setup (0.1-23ubuntu4) intrepid; urgency=low
* init.d: No need to mess with the Thinkpad hotkey mask anymore.
Current version of thinkpad_acpi suggests using the default.
(LP: #256887)
-- Timo
15:44:48 shenki mjg59: do you know what this message is about:
15:44:52 shenki thinkpad_acpi: setting the hotkey mask to 0x00ff is
likely not the best way to go about it
15:45:17 mjg59 Yes, with recent thinkpad_acpis userspace shouldn't be
setting hotkey_mask
15:48:38 shenki mjg59: where
23:14 shenki mjg59: do you know what this message is about:
23:14 shenki thinkpad_acpi: setting the hotkey mask to 0x00ff is likely
not the best way to go about it
23:15 mjg59 Yes, with recent thinkpad_acpis userspace shouldn't be setting
hotkey_mask
Seeing
On Thu, Aug 28, 2008 at 02:01:10PM -, Reinhard Tartler wrote:
15:44:48 shenki mjg59: do you know what this message is about:
15:44:52 shenki thinkpad_acpi: setting the hotkey mask to 0x00ff is
likely not the best way to go about it
15:45:17 mjg59 Yes, with recent thinkpad_acpis
I can confirm this issue on an Thinkpad X60s
** Changed in: hotkey-setup (Ubuntu)
Status: New = Confirmed
--
thinkpad_acpi complains that hotkey-setup is doing the wrong thing
https://bugs.launchpad.net/bugs/256887
You received this bug notification because you are a member of Ubuntu
