I don't think we're quite ready yet to make detect_x_display go away, so I offer the following as a compromise to partially address #598097. Most of the time our handlers based on detect_x_display seem to work. I'm still unsure of why it isn't working with Paul with gdm3, as it seems to work for me.
Ben On 14/11/10 10:22 AM, Ben Armstrong wrote: > The following commit has been merged in the master branch: > commit e23230db7f3e299d65b3d6259606638c333ac5ff > Author: Ben Armstrong <[email protected]> > Date: Sun Nov 14 10:22:33 2010 -0400 > > Document alternate acpi_fakekey handlers to synthesize missing input > events. > > diff --git a/debian/changelog b/debian/changelog > index 84d06ae..56e0a72 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -3,8 +3,10 @@ eeepc-acpi-scripts (1.1.12) UNRELEASED; urgency=low > * Allow wireless toggle to be configured independently of kernel version, > but with the documented caveat that it is still intended for use with > older kernels without rfkill input. > + * Document acpi_fakekey alternative key handlers to provide input events > + for keys not handled by the current kernel driver. > > - -- Ben Armstrong <[email protected]> Sun, 14 Nov 2010 08:26:20 > -0400 > + -- Ben Armstrong <[email protected]> Sun, 14 Nov 2010 10:15:07 > -0400 > > eeepc-acpi-scripts (1.1.11) unstable; urgency=low > > diff --git a/debian/eeepc-acpi-scripts.default.in > b/debian/eeepc-acpi-scripts.default.in > index 3af852b..f4d6469 100644 > --- a/debian/eeepc-acpi-scripts.default.in > +++ b/debian/eeepc-acpi-scripts.default.in > @@ -85,6 +85,19 @@ BLUETOOTH_FALLBACK_TO_HCITOOL='yes' > # i.e. <=2.6.27). > # - NONE > # Ignore the key. > +# - acpi_fakekey ${KEY_xxx} > +# Instead of having eeepc-acpi-scripts handle the key, pass it on as > +# an ordinary input event, allowing your window manager or desktop > +# environment handle it (either via a default key binding or else > +# a custom binding configured by you). > +# * This is generally only needed in case the kernel driver does not > +# generate any input event (testable with evtest using "EeePC extra > +# buttons" input# reported in dmesg). A couple of keys known to not > +# generate any input events in Debian kernel version 2.6.32-23 are > +# indicated in comments below. > +# * Consult /usr/share/acpi-support/key-constants for allowable > constants, > +# or if no constant is provided, specify the decimal values for KEY_* > +# constants listed in /usr/include/linux/input.h. > # - custom command > # For example you can write a shell function in this file and use its > # name as an action, or call another internal or external command. > @@ -108,10 +121,14 @@ SOFTBTNSHE_ACTION='handle_shengine' > FnF_WIRELESS='NONE' > # --/F3 - touchpad toggle > FnF_TOUCHPAD='handle_touchpad_toggle' > +# Uncomment to synthesize the standard F22 touchpad toggle key: > +#FnF_TOUCHPAD='acpi_fakekey ${KEY_F22}' > # --/F4 - resolution change > FnF_RESCHANGE='NONE' > # --/F7 - backlight off > FnF_BACKLIGHTOFF='handle_blank_screen' > +# Uncomment to synthesize the standard backlight off key: > +#FnF_BACKLIGHTOFF='acpi_fakekey ${KEY_BACKLIGHT_OFF}' > # F5/F8 - VGA toggle > FnF_VGATOGGLE='handle_vga_toggle' > # F6/F9 - 'task manager' key > diff --git a/eeepc-acpi-scripts/hotkey.sh b/eeepc-acpi-scripts/hotkey.sh > index 98e9c80..7bda610 100755 > --- a/eeepc-acpi-scripts/hotkey.sh > +++ b/eeepc-acpi-scripts/hotkey.sh > @@ -22,6 +22,11 @@ if [ -e "$DEFAULT" ]; then . "$DEFAULT"; fi > code=$3 > value=$(test "x$1" = x- && cat "$BACKLIGHT" || echo "0x$3") > > +# FIXME: should be defined in /usr/share/acpi-support/key-constants which > +# should be regenerated from a recent copy of /usr/include/linux/input.h > +# (see: #603471). > +KEY_DISPLAY_OFF=245 > + > handle_mute_toggle() { > $PKG_DIR/volume.sh toggle > } > _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
