On Sat, Nov 10, 2012 at 12:35 PM, Ben Armstrong <[email protected]> wrote: > On 10/11/12 07:33 AM, Hans-J. Ullrich wrote: >> This behaviour appears with or without "acpi_osi=Linux". In my case I have to >> use "acpi_osi=Linux", as my EEEPC 1005 HGO needs this (eeepc-wmi is not >> supported by my hardware, because the vendors kept the specs secret). > > Even using the kernel in Wheezy? That's what we're talking about here. I > was under the impression that no hardware supporting eeepc-wmi should > use eeepc-laptop, and therefore in wheezy, acpi_osi="Linux" should never > be used. > >> If you wonder, why I filed no bugreport: This is easy to explain. As I seemed >> to be the only user in the world with this problem, I did not want to waste >> your ressources in this work for a single person. :) >> >> As it looks now, other people have too, maybe a bug might be opened? > > Possibly, but in that case, I'm not sure it would ever be fixed in > eeepc-acpi-scripts, which should do less and less until it is finally > eliminated. > > One possibility that I have not investigated recently is that certain > hotkeys are not handled by ACPI at all anymore and should be caught by > the window manager itself and handled there. If that's the case here, it > is a small matter of configuring your key bindings (in LXDE's case, the > openbox key bindings) to issue the appropriate command and send a > message to the notification daemon. > > Ben
Actually I have just realised Fn spacebar for me actually doesnt do anything. Thats using eeepc_wmi _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-eeepc-devel
