You are not logged in.

#1 2016-05-28 11:47:07

VCoolio
Member
From: Netherlands
Registered: 2010-01-05
Posts: 120

[not really SOLVED] Button 'up' doesn't work, not even when simulated

I can't find a way to go 'up':
- pressing key 'up' on my default bluetooth logitech k810 doesn't work (where all others do)
- pressing key 'up' on a normal usb keyboard doesn't work (where all others do)
- command xte 'key up' doesn't work (while e.g. xte 'key down' does)
- command xvkbd -text "\[Up]" doesn't work (while e.g. xvkbd -text "[\Down]" does)

When I use xev, I get this when down arrow key is pressed (this seems normal):

KeyPress event, serial 39, synthetic NO, window 0x2000001,
    root 0x299, subw 0x0, time 84493056, (-158,-594), root:(1584,303),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x2000001,
    root 0x299, subw 0x0, time 84493168, (-158,-594), root:(1584,303),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

If I use the up key however, I get this:

FocusOut event, serial 39, synthetic NO, window 0x2000001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x2000001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 39, synthetic NO, window 0x0,
    keys:  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   0   

Any hints on what might be wrong are very much appreciated. It looks like 'up' is already claimed/grabbed by some program/daemon, but how to figure out what it is?

Edit: I was trying to exclude all possibilities while editing this post. Now I tried to add a keybinding for 'up' in my window manager config (enlightenment). It didn't exist yet, I added a binding for 'up', it didn't work (as expected) and then I deleted the binding for 'up'. Now it works. Don't have a clue why. Maybe it's temporary. Then I'll reopen this issue. Sorry for the noise.

Edit 2: the problem does not lie in Enlightenment. Assigning and removing an keybinding to 'up' is just a way of 'getting the key back'. I suspect flashplayer to be the problem, but don't know how to debug or pinpoint, so I'll leave it at this. I know now how to easily work around.

Last edited by VCoolio (2016-06-06 20:51:52)

Offline

#2 2016-05-28 11:55:10

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

Re: [not really SOLVED] Button 'up' doesn't work, not even when simulated

VCoolio wrote:

It looks like 'up' is already claimed/grabbed by some program/daemon, but how to figure out what it is?

Yup.

So start narrowing it down.  Does it work in a tty? (I suspect it will).  Does it work in another WM?  What WM/DE is this in?


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

Offline

#3 2016-05-28 11:57:50

VCoolio
Member
From: Netherlands
Registered: 2010-01-05
Posts: 120

Re: [not really SOLVED] Button 'up' doesn't work, not even when simulated

Thanks Trilby, quick response much appreciated. Looks like something was wrong in the keybinding config for enlightenment (see last lines in OP) without showing in the settings. Edit: see OP.

Last edited by VCoolio (2016-06-06 20:53:32)

Offline

Board footer

Powered by FluxBB