You are not logged in.

#1 2016-12-11 12:54:20

Davs
Member
Registered: 2011-11-18
Posts: 8

ThinkPad T430 ThinkVantage button

Hi!
I'm using Arch with lts kernel (4.4.37 atm) and since some update, the thinkvantage button stopped working.

Showkey detects it fine

root# showkey
keycode 148 press
keycode 148 release

root# showkey --scancodes
0xe0 0x1f 0xe0 0x9f

However xev does not detect the key:
KeymapNotify event, serial 34, synthetic NO, window 0x0,
    keys:  2   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

Is there a way to fix this? Thanks.

Offline

#2 2016-12-11 12:56:31

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: ThinkPad T430 ThinkVantage button

It works on my ThinkPads - it gives the symbol XF86Launch1.

Your xev output does not suggest that it is not detected, but rather that the keysym is already grabbed/handled by another process.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2016-12-11 12:59:30

Davs
Member
Registered: 2011-11-18
Posts: 8

Re: ThinkPad T430 ThinkVantage button

Thanks for the reply. Is there a way to possible detect what is grabbing that keyevent?

Offline

#4 2016-12-11 13:13:07

Davs
Member
Registered: 2011-11-18
Posts: 8

Re: ThinkPad T430 ThinkVantage button

I've found it! It was my i3wm config; I created a binding with 'bindcode 148' and now I changed that to 'bindsym XF86Launch1', which actually works.

Offline

#5 2016-12-11 13:24:12

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: ThinkPad T430 ThinkVantage button

Not directly, but it is a running process connected to the Xserver.  You could check lsof output, maybe something like

lsof | awk '/libX11/ { print $1; }' | sort -u

to get a list of possible suspects.

But this would most likely be a window manager, DE, or some sort of laptop utility package.

More on point though, why does it matter?  Surely the end goal is not to get the key to show up in xev output.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#6 2016-12-11 13:32:08

Davs
Member
Registered: 2011-11-18
Posts: 8

Re: ThinkPad T430 ThinkVantage button

Trilby wrote:

Not directly, but it is a running process connected to the Xserver.  You could check lsof output, maybe something like

lsof | awk '/libX11/ { print $1; }' | sort -u

to get a list of possible suspects.

But this would most likely be a window manager, DE, or some sort of laptop utility package.

More on point though, why does it matter?  Surely the end goal is not to get the key to show up in xev output.

I wanted to map it to a custom action. In my window managers config I mapped the key's code (148), which caused the problem. After changing that to XF86Launch1 everywthing works smile

Offline

Board footer

Powered by FluxBB