https://bugzilla.redhat.com/show_bug.cgi?id=1186030
--- Comment #19 from Benjamin Tissoires <btissoir(a)redhat.com> ---
(In reply to Kent W. Nixon from comment #18)
Ben, your posted keymaps for the 2013 Pixel to not line up with what
I have
over here. My keyboard scancodes line up with the ones you posted from the
2015 Pixel (shown below [no idea how to attach things]). I don't know where
or how you got your scan codes, but please be aware that I nuked Chrome OS
off of my Pixel thing pretty much as soon as I got it from Google I/O 2013.
I am also running a custom version of coreboot courtesy of johnlewis.ie. A
later hardware revision or a firmware update through Chrome OS may have
changed it to match what you posted for others.
OK. thanks for the notice, but hopefully we will not have to tune any custom
scancodes. As mentioned in comment #14, the idea is to use xkb, and not a
custom keymap config.
I have opened fdo bug #90684 for this and we are still waiting on upstream.
If you want to give a try, you can:
- revert the hwdb changes (and reboot)
- add the "inet" section from the patch in the fdo bug in
/usr/share/X11/xkb/symbols/inet (without the leading '+')
- run "setxkbmap -layout us -model chromebook"
This should make the right Alt key as a modifier and the function keys working
like they should.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=FCZlIR24VQ&a=cc_unsubscribe