Talk:HP EliteBook 840 G2

From ArchWiki

What does "Generates ACPI events" mean?

ACPI events and "Visible to xev and similar" should be the same thing, yet in your table they're two separate things that are conflicting with each other.

At the very least shorten the titles down to not create massive columns, thanks. DerpishCat (talk) 19:25, 1 May 2021 (UTC)

The acpi_listen tool reports ACPI events; the xev tool reports the X events. One example of difference between them is a “lid close”, which AFAIK is a ACPI event but is not a X event, and can still be configured in the software. Inversely, the classical a key raises a X event, but no ACPI event.
I'm not an expert about the question. I just notice that most of Fn+F… key on my laptop are not reported by `xev`, so I think they don't fit in the classical “Visible?” column, isn't it? That's why I added a column about ACPI events.
Audeoudh (talk) 08:43, 3 May 2021 (UTC)
The example table on the Laptop page guidelines page already says that systemd-logind listens on some keys. Your desktop environment or window manager may listen on some of them, too so they are not visible to xev. The reason why the table is asking for the function keys and not ACPI events because e.g the lid close event is very different from your "lower the brightness" button.
Luckily lid close is detected properly on most laptops, so it is not necessary to specify it unless it is not working correctly.
-- NetSysFire (talk) 19:16, 3 May 2021 (UTC)
All my tests have been done with the recommended systemd-inhibit --what=handle-suspend-key sleep 1h running. Still most of them are not emitting events as seen by xev. Not sure of my desktop environment (Gnome) and my window manager (Wayland), I do not know how to ask them not to handle these keys for some time.
I make the table compliant with Laptop Page Guidelines. I still don't understand what is the mean of the “Visible?” column if we don't care of ACPI events.
-- Audeoudh (talk) 09:11, 5 May 2021 (UTC)
The systemd-inhibit command is only needed to capture keys which logind is listening on. Your desktop environment is probably swallowing most other keys, which is why they still emit ACPI events. The only way I can think of right now to properly capture all keys is by using some sort of minimal window manager, I recommend Openbox, that does not listen on any of these events by default.
-- NetSysFire (talk) 10:04, 5 May 2021 (UTC)
Well done! Gnome hid most keys. I started Openbox for testing, and xev reports allmost all events. Thank you!
-- Audeoudh (talk) 14:31, 5 May 2021 (UTC)