>Are you sure its 232 and 233? KEY_BRIGHTNESSDOWN should be 224 and
>KEY_BRIGHTNESSUP 225.
I think so.
KeyRelease event, serial 26, synthetic NO, window 0x400001,
root 0x13c, subw 0x400002, time 4287063, (54,65), root:(56,67),
state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown),
same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 26, synthetic NO, window 0x400001,
root 0x13c, subw 0x400002, time 4287334, (54,65), root:(56,67),
state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp),
same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
>Anyway, what happens if you remove
>/etc/acpi/events/asus-brightness-down and /etc/acpi/events/asus-brightness-up
>or alternativly change /etc/acpi/asus-brn-down.sh to just 'exit 0' instead of
>calling acpi_fakekey? This should stop the keypresses, but does your system
>still correct brightness? Well it should if it did before, but let's find out.
"Unfortunately", I cannot reproduce the bug anymore. I tried to delete
video_brightnessdown and video_brightnessup (I have a dell laptop, so I don't
know if asus-* file have effects here), and this
seemed to remove the bug with no other undesired effects. Now, after restoring
these files, the bug didn't come back.
>Does this problem still appear after upgrading acpi-support to 0.130-1?
>Michael
Ok also after upgrading.
Michele
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
