You are not logged in.
Can anyone else running kernel 3.17.1.1-ARCH on a Lenovo Thinkpad T440S (or similar hardware) confirrm that their F11/F12 Hotkeys are no longer working?
On kernel 3.16.2, these keys mapped to (as provided by xbindkeys):
F11 (image of windows in rectangle) = XF86LaunchA
F12 (image of windows in 3X2 layout) = XF86MyComputer
On 3.17.1.1, the mappings now are (again from xbindkeys):
F11 = nothing
F12 = XF86Explorer
The current mappings appear to have regressed to what they were on kernels < 3.15 (if I remember right).
Noticed this after trying to move an i3 window to scratchpad (which I remapped the keys to do).
Thanks in advance for any input.
Last edited by halocaridina (2014-10-24 19:41:25)
4X Intel(R) Xeon(R) CPU E7-8870 @ 2.40GHz; 256GiB; 11TB EXT4; SL6.8
2X Intel(R) Xeon(R) CPU E5-2680 @ 2.70GHz; 256GiB; 3.4TB EXT4; SL6.8
Thinkpad X250; Broadwell-ULT Core i5; 8GiB, 525GB Crucial_CT525MX3; Arch
Thinkpad T440S; Haswell-ULT Core i7; 12GiB, 512GB SanDisk X210; Arch
Offline
i get
[lambda] /home/pi > xbindkeys -k
Press combination of keys or/and click under the window.
You can use one of the two lines after "NoCommand"
in $HOME/.xbindkeysrc to bind a key.
"(Scheme function)"
m:0x0 + c:152
XF86Explorer
[lambda] /home/pi > xbindkeys -k
Press combination of keys or/and click under the window.
You can use one of the two lines after "NoCommand"
in $HOME/.xbindkeysrc to bind a key.
"(Scheme function)"
m:0x0 + c:128
XF86LaunchA
[lambda] /home/pi > uname -a
Linux lambda 3.17.1-1-ARCH #1 SMP PREEMPT Wed Oct 15 15:04:35 CEST 2014 x86_64 GNU/Linux
so F12 changed, but F11 still works.
Offline
Dispanser,
Thank you for checking and confirming that the behavior is differnet for those hotkeys between kernels 3.17 and 3.16 (and even different machines running the same kernel version).
Interesting difference for F11. My guesses for it are difference in regards to specific hardware and/or firmware (the latter was something I also updated last night).
Guess I'll remap the scratchpad keys in the meantime. I'll mark this as "solved" in the near future (i.e., after testing the next point release for 3.17).
Halocaridina
4X Intel(R) Xeon(R) CPU E7-8870 @ 2.40GHz; 256GiB; 11TB EXT4; SL6.8
2X Intel(R) Xeon(R) CPU E5-2680 @ 2.70GHz; 256GiB; 3.4TB EXT4; SL6.8
Thinkpad X250; Broadwell-ULT Core i5; 8GiB, 525GB Crucial_CT525MX3; Arch
Thinkpad T440S; Haswell-ULT Core i7; 12GiB, 512GB SanDisk X210; Arch
Offline
A reboot resulted in both F11 and F12 hotkeys being fully functional under kernel 3.17.1.1. Not sure what the problem was earlier (but will keep an eye on it).
Note that the keymapping still has changed between kernels 3.16 and 3.17 for F12 on this make and model of Lenovo:
3.16: F12 = XF86MyComputer
3.17: F12 = XF86Explorer
while F11 remains XF86LaunchA
Hope this helps someone else.
4X Intel(R) Xeon(R) CPU E7-8870 @ 2.40GHz; 256GiB; 11TB EXT4; SL6.8
2X Intel(R) Xeon(R) CPU E5-2680 @ 2.70GHz; 256GiB; 3.4TB EXT4; SL6.8
Thinkpad X250; Broadwell-ULT Core i5; 8GiB, 525GB Crucial_CT525MX3; Arch
Thinkpad T440S; Haswell-ULT Core i7; 12GiB, 512GB SanDisk X210; Arch
Offline