http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c2 --- Comment #2 from Carlos Robinson --- The laptop is a Compaq presario CQ61-330SS You have the hwinfo in Bug 694943 https://bugzilla.novell.com/attachment.cgi?id=485953 I was running 11.4 at the time, but I suppose it does not affect. Later I'll boot to 42.2 and try the kernel you suggest. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c4 --- Comment #4 from Carlos Robinson --- Some produce an action, some only produce some output on xev, some do nothing. 2,3,4,5,6, 9 10, 11 and 12 seen in xev 1, 7, 8 do nothing. Working: 2 print? 3 www - makes firefox display home page on current tab. Erased what I had wrote on this bugzilla, too. 4 display setup 5 sleep machine 6 lock display 9 play/pause (untested with multimedia app) 10 stop 11 rewind 12 fast forward Do nothing: 1 ? help key? 8 brightens up the display - works on 13.1, not 42.2 7 darkens the display - works on 13.1, not 42.2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c6 --- Comment #6 from Carlos Robinson --- (In reply to Max Staudt from comment #1)

Please also try a 42.2 and a TW KOTD:

http://kernel.opensuse.org/branches/stable

Trying 4.9.0-1.g8c92422-default. Same thing, no output in xev. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c8 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carlos.e.r@opensu | |se.org) | --- Comment #8 from Carlos Robinson --- --- Comment #7 from Max Staudt <> ---

Ewww, so the keys don't even make it through to X11.

I'm not sure about the help key. What was supposed to happen?

I don't know. Nothing starts. Xev on 13.1 says: KeyPress event, serial 37, synthetic NO, window 0x3200001, root 0x80, subw 0x3200002, time 110322919, (64,25), root:(658,331), state 0x10, keycode 146 (keysym 0xff6a, Help), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x3200001, root 0x80, subw 0x3200002, time 110323094, (64,25), root:(658,331), state 0x10, keycode 146 (keysym 0xff6a, Help), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False See that the "Help" name is recognized. But I don't care about that one. What I need are the brightness keys .-) On 42.2 the '?' key produces nothing in xev.

As for the brightness keys, their handling has changed. They tend to be handled either by systemd's ACPI handler, or by the desktop environment now. However, since they never make it through to X11, something is blocking them further down the stack.

1. Could you please post a dump of 'xinput' on both 13.1 and 42.2?

This should give us an idea of the input hardware in your machine.

13.1 cer@minas-tirith:~> xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ HP Webcam-101 id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ HP WMI hotkeys id=13 [slave keyboard (3)] cer@minas-tirith:~> 42.2 cer@Minas-Anor:~> xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ HP Webcam-101 id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ HP WMI hotkeys id=13 [slave keyboard (3)] cer@Minas-Anor:~> (there is no sleep button that I know off in this machine. There is a lid close detector, but not visible, must be internal)

2. On 13.1, do these keys generate events in xev? Do they show any name (a keysym)? For example, the play/pause key may be named XF86AudioPlay, and the brightness keys should have similar names. They will not show any name though if they're grabbed by a program, such as your desktop environment's power manager.

On 13.1, xev says about those two keys: KeyRelease event, serial 34, synthetic NO, window 0x3200001, root 0x80, subw 0x0, time 110594157, (-478,151), root:(116,457), state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES, XLookupString gives 1 bytes: (0d) "^M" XFilterEvent returns: False MappingNotify event, serial 37, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 FocusOut event, serial 37, synthetic NO, window 0x3200001, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 37, synthetic NO, window 0x3200001, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 4294967227 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RRNotify event, serial 38, synthetic NO, window 0x3200001, subtype XRROutputPropertyChangeNotifyEvent output LVDS1, property Backlight, timestamp 110598545, state NewValue FocusOut event, serial 41, synthetic NO, window 0x3200001, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 41, synthetic NO, window 0x3200001, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 41, synthetic NO, window 0x0, keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RRNotify event, serial 41, synthetic NO, window 0x3200001, subtype XRROutputPropertyChangeNotifyEvent output LVDS1, property Backlight, timestamp 110599840, state NewValue ClientMessage event, serial 43, synthetic YES, window 0x3200001, message_type 0x130 (WM_PROTOCOLS), format 32, message 0x12e (WM_DELETE_WINDOW) And they do produce effect in brightness, and a a popup with a slider shows. Notice the word "Backlight" On 42.2 neither the brightness keys or the help key produces anything in xev.

3. Run 'sudo evtest' on any event devices that seem to fit (keyboard, ACPI buttons, whatever isn't a mouse really) and see whether the keys generate any events. Please stop X completely before running this: switch to a text console and run 'rcxdm stop'. Compare the output on 13.1 and 42.2.

This will show whether the kernel relays the events at all.

13.1 minas-tirith:~ # evtest Usage: evtest /dev/input/eventX Where X = input device number minas-tirith:~ # with event0, those two keys write an @ to the screen, no data Event: time 1482200711.621233, type 4 (Misc), code 4 (ScanCode), value 8a ^@Event: time 1482200711.621233, type 1 (Key), code 152 (Coffee), value 1 Event: time 1482200711.621233, -------------- Report Sync ------------ Event: time 1482200711.797281, type 4 (Misc), code 4 (ScanCode), value 8a Event: time 1482200711.797281, type 1 (Key), code 152 (Coffee), value 0 Event: time 1482200711.797281, -------------- Report Sync ------------ ^@^@Event: time 1482200721.712123, type 4 (Misc), code 4 (ScanCode), value a2 Event: time 1482200721.712123, type 1 (Key), code 164 (PlayPause), value 1 Event: time 1482200721.712123, -------------- Report Sync ------------ ^@Event: time 1482200721.854956, type 4 (Misc), code 4 (ScanCode), value a2 Event: time 1482200721.854956, type 1 (Key), code 164 (PlayPause), value 0 Event: time 1482200721.854956, -------------- Report Sync ------------ The help key is here: Testing ... (interrupt to exit) Event: time 1482201067.294028, type 4 (Misc), code 4 (ScanCode), value 1c Event: time 1482201067.294028, type 1 (Key), code 28 (Enter), value 0 Event: time 1482201067.294028, -------------- Report Sync ------------ Event: time 1482201069.568403, type 4 (Misc), code 4 (ScanCode), value b1 ^@Event: time 1482201069.568403, type 1 (Key), code 138 (Help), value 1 Event: time 1482201069.568403, -------------- Report Sync ------------ Event: time 1482201069.709524, type 4 (Misc), code 4 (ScanCode), value b1 Event: time 1482201069.709524, type 1 (Key), code 138 (Help), value 0 Event: time 1482201069.709524, -------------- Report Sync ------------ Event: time 1482201071.386862, type 4 (Misc), code 4 (ScanCode), value 1d Event: time 1482201071.386862, type 1 (Key), code 29 (LeftControl), value 1 Event: time 1482201071.386862, -------------- Report Sync ------------ Event: time 1482201071.597675, type 4 (Misc), code 4 (ScanCode), value 2e ^C minas-tirith:~ # The brightness keys are on 6: minas-tirith:~ # evtest /dev/input/event6 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0 Input device name: "Video Bus" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 224 (Brightness down) Event code 225 (Brightness up) Event code 227 (?) Event code 241 (?) Event code 242 (?) Event code 243 (?) Event code 244 (?) Event code 245 (?) Testing ... (interrupt to exit) ^@Event: time 1482200874.300429, type 1 (Key), code 224 (Brightness down), value 1 Event: time 1482200874.300429, -------------- Report Sync ------------ Event: time 1482200874.300512, type 1 (Key), code 224 (Brightness down), value 0 Event: time 1482200874.300512, -------------- Report Sync ------------ ^@Event: time 1482200876.025011, type 1 (Key), code 225 (Brightness up), value 1 Event: time 1482200876.025011, -------------- Report Sync ------------ Event: time 1482200876.025170, type 1 (Key), code 225 (Brightness up), value 0 Event: time 1482200876.025170, -------------- Report Sync ------------ 42.2 Minas-Anor:~ # evtest /dev/input/event6 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0 Input device name: "Power Button" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 116 (KEY_POWER) Properties: Testing ... (interrupt to exit) ^P^CMinas-Anor:~ # I don't see the video bus event number. I tried them all. event0 displays them, but as far as I can see both produce the same values: Testing ... (interrupt to exit) Event: time 1482201676.380961, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1c Event: time 1482201676.380961, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0 Event: time 1482201676.380961, -------------- SYN_REPORT ------------ Event: time 1482201681.896395, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1482201681.896395, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1 Event: time 1482201681.896395, -------------- SYN_REPORT ------------ Event: time 1482201681.968316, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1482201681.968316, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0 Event: time 1482201681.968316, -------------- SYN_REPORT ------------ Event: time 1482201682.916661, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1482201682.916661, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1 Event: time 1482201682.916661, -------------- SYN_REPORT ------------ Event: time 1482201682.987614, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1482201682.987614, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0 Event: time 1482201682.987614, -------------- SYN_REPORT ------------ But not event6, so they are on different place. The ? key also appears here. Oh. I had not stopped graphics, try again. [...] No, same result. cer@Minas-Anor:~> uname -a Linux Minas-Anor.Valinor 4.4.36-8-default #1 SMP Fri Dec 9 16:18:38 UTC 2016 (3ec5648) x86_64 x86_64 x86_64 GNU/Linux cer@Minas-Anor:~> Minas-Anor:~ # evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: SynPS/2 Synaptics TouchPad /dev/input/event2: PC Speaker /dev/input/event3: Power Button /dev/input/event4: Lid Switch /dev/input/event5: Sleep Button /dev/input/event6: Power Button /dev/input/event7: HP WMI hotkeys /dev/input/event8: Video Bus /dev/input/event9: HP Webcam-101 /dev/input/event10: HDA Digital PCBeep /dev/input/event11: HDA Intel Mic /dev/input/event12: HDA Intel Headphone /dev/input/event13: HDA Intel HDMI/DP,pcm=3 Select the device event number [0-13]: Oh, it should be the #8. I will send this, then close X to try again. If I see something I'll add. If I say nothing, nothing was produced by the brightness keys. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c10 --- Comment #10 from Max Staudt --- Right. So this is definitely not an X problem. The brightness popup that you saw on 13.1 was the power manager - in XFCE, this is xfce4-power-manager. Things that may grab the brightness keys and change the brightness setting are: - The hardware - Some ACPI daemon (acpid, systemd) - A power manager such as the above Fun times ensue when two of them do this at the same time, but that's another story. Thanks for your helpful testing! For comparison, I tried evtest on the "Video Bus" device on my Intel Broadwell machine, and that did produce the events. It's time for a hardware list. Can you please post "sudo hwinfo"? Also, on both 13.1 and 42.2: "ls /sys/class/backlight/" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c12 --- Comment #12 from Carlos Robinson --- Ok, 42.2. On reboot, graphics mode crashed. On two reboots. Was difficult to get a console to isue init 3; init 5 and get graphics again. And I have not applied any update or change. Go figure. Minas-Anor:~ # ls /sys/class/backlight/ acpi_video0 Minas-Anor:~ # ls /sys/class/backlight/acpi_video0 actual_brightness bl_power brightness device max_brightness power subsystem type uevent Minas-Anor:~ # echo 5 > /sys/class/backlight/acpi_video0/brightness Minas-Anor:~ # echo 10 > /sys/class/backlight/acpi_video0/brightness Minas-Anor:~ # I will now obtain recent hwinfo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c14 --- Comment #14 from Max Staudt --- Thanks, I forgot about that other bug! Alright, it's an Intel GPU... I haven't heard of issues like this with them before. In this case, I guess the only thing left to do is to bisect the kernel. You can either do this yourself, and I may or may not be able to do this in January. As a start, can you please try a 13.1, 13.2, 42.1, and 42.2 kernel, each on 13.1 and 42.2? That is, 8 tests in total, of which 2 are already done :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c16 --- Comment #16 from Max Staudt --- You can grab the KOTDs from http://kernel.opensuse.org/ and the 13.1 packages from OBS. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c18 --- Comment #18 from Max Staudt --- Okay, so that sounds like it's been broken for a long while, and nobody noticed. So it may be unlikely that I can find hardware to reproduce this on, but I'll try. In case you know how to bisect the kernel on your own, feel free to go ahead, and I'll have a look at what you find. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c20 --- Comment #20 from Carlos Robinson --- (In reply to Max Staudt from comment #18)

Okay, so that sounds like it's been broken for a long while, and nobody noticed.

Well, you see, this laptop has stayed on 13.1... I did test 13.2 and 42.1, but briefly. I noticed the problem in 42.2 because when testing for another bug I was asked to try with gnome, and it was too dark, and I could not make it brighter. I'm surprised that the bug only affects me, though,

So it may be unlikely that I can find hardware to reproduce this on, but I'll try.

In case you know how to bisect the kernel on your own, feel free to go ahead, and I'll have a look at what you find.

I know the general idea, but I have never done it. I suspect that I have to try with a kernel just in the middle between 3.11 and 3,16, and depending on the results I go up or down in version another half. But I don't know where susified kernels of all versions are stored. IF they are stored. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1015020 http://bugzilla.suse.com/show_bug.cgi?id=1015020#c22 --- Comment #22 from Max Staudt --- Hmm, I tried to reproduce this on a MacBook with 3rd gen graphics that I currently have access to, but that one sends the backlight key events via the keyboard input device. So I'll have to keep looking for hardware :( -- You are receiving this mail because: You are on the CC list for the bug.