up (arrow) key does not work in gnome-terminal after upgrade to 3.34

odror · 2019-09-20 05:36:15

After upgrading to gnome 3.34 the up arrow key stopped working in gnome-teminal. Instead I get s screen flush.

For example if I want to use the prior command. Normally I press the up key and fetch the prior bash or fish command. Now after the upgrade nothing happen except for
screen flush.

Any help in debugging will be appreciated.

jasonwryan · 2019-09-20 05:54:31

Is it just in gnome-terminal, or in all/other terms?

odror · 2019-09-20 06:23:13

Also in xterm, mate-terminal and Knosole (running in gnome)

Last edited by odror (2019-09-20 06:23:55)

seth · 2019-09-20 07:21:09

"screen flush" like a visual bell?
What about other keys, notably left, right, home and end?
Is this gome on wayland or gnome on X11?
Did you update other packages as well?
Does it happen for a fresh account (or if you move away *all* your personal shell configs)?

odror · 2019-09-20 13:55:56

I had a full update. Yes the other arrow keys are a problem. I am using X11. I do not use the Home and End keys.

I also noticed that the default function of the super was changed. The super key does not bring the Preview I need to press Super+S for the preview.

I think gnome does not pass the Arrow keys to the terminals. I do not know how to fix that.

Screen flush ? like bell or warning. I have not see, it before.

Last edited by odror (2019-09-20 13:56:57)

seth · 2019-09-20 14:05:08

I do not use the Home and End keys.

You're not supposed to /use/ but /try/ their behavior.
Gnome doesn't pass anything on X11 and if the input was grabbed, you'd get no response from the terminal at all.

Please run "xev -event keyboard" and press the up arrow key. Post the output.

Edit: and also your Xorg log, https://wiki.archlinux.org/index.php/Xorg#General

Last edited by seth (2019-09-20 14:06:27)

odror · 2019-09-20 15:38:28

xev -event keyboard (up arrow)

KeymapNotify event, serial 26, synthetic NO, window 0x0,
keys: 4294967294 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
(for down arrow)

KeyRelease event, serial 28, synthetic NO, window 0x4600001,
root 0x1fe, subw 0x0, time 943989690, (103,62), root:(3943,138),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

It is strange after resetting gnome Alt-f2 (Then r). The issue resolved.

I guess I have to reset gnome after each startup.

seth · 2019-09-20 15:41:33

There's only a release event for the down key, what would suggest xev didn't have the input focus when you started the test?

odror · 2019-09-20 15:44:22

There were 2 events. I did not copy properly.

KeyPress event, serial 28, synthetic NO, window 0x4600001,
root 0x1fe, subw 0x0, time 944675424, (143,137), root:(3983,213),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x4600001,
root 0x1fe, subw 0x0, time 944675584, (143,137), root:(3983,213),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

seth · 2019-09-20 15:54:29

That's still only the Down arrow and no repsonse for the up arrow at all.
Can you please post the complete xev output? (Even if the up arrow key was grabbed, there'd be 2 keymap events.

Is alt+f2 the shortcut for some runner?

odror · 2019-09-20 16:06:47

I had to restart my desktop. (the issue was resolved after gnome reset)

The up arrow has only on event.

up arrow followed by down arrow:

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

KeyPress event, serial 28, synthetic NO, window 0x4200001,
root 0x1fe, subw 0x0, time 945950534, (158,145), root:(3998,221),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x4200001,
root 0x1fe, subw 0x0, time 945950702, (158,145), root:(3998,221),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

seth · 2019-09-20 16:09:15

Smells still like a grab then.

xdotool key "XF86LogGrabInfo"

will dump all active and passive grabs (and the grabbing client) into the xorg log.
You're looking for "keycode 111 (keysym 0xff52, Up)"

odror · 2019-09-20 16:24:30

this is strange:

As soon as I typed the xdotool command the problem is resolved.

xorg.log is:
946864.735] xi2 event mask 0xc 0 0 0
[946864.735] owner-events false, kb 0 ptr 1, confine 0x0, cursor 0x0
[946864.735] grab 0x40600824 (xi2), type 'KeyPress' on window 0x1fe
[946864.735] detail 111 (mask 0), modifiersDetail 6 (mask 0)
[946864.735] device 'Virtual core keyboard' (3), modifierDevice 'Virtual core keyboard' (3)

odror · 2019-09-20 16:34:29

Do you know how to disable the info grabbing by xdotool. I wan to see if the issue comes back.

seth · 2019-09-20 16:38:14

Somewhere above the posted output it'll say sth. like

Printing all registered grabs of client pid 1234 /usr/bin/foobar

(make sure it's the closest instance)

I'm not sure what post #14 is supposed to mean.
xdotool sends a key event to the X11 server (and this key triggers a server shortcut to print the grabbing clients)
You could try to send any other key instead.

odror · 2019-09-20 16:46:40

First instance:
[946864.735] xi2 event mask 0xc 0 0 0
[946864.735] owner-events false, kb 0 ptr 1, confine 0x0, cursor 0x0
[946864.735] grab 0x40600824 (xi2), type 'KeyPress' on window 0x1fe
[946864.735] detail 111 (mask 0), modifiersDetail 6 (mask 0)
[946864.735] device 'Virtual core keyboard' (3), modifierDevice 'Virtual core keyboard' (3)

#14 means how do disable logging the keys in the org file.

seth · 2019-09-20 20:07:15

Again: the interesting line will be the one that reveals *what* grabs that key.
And I still don't really understand what you mean by #14 - the grabs are only logged once as direct response to the xdotool call - it has no static impact on the server, let alone the configuration.

odror · 2019-09-21 00:39:23

How can I do that. As soon as I type the xdotool command the issue is resolved.

seth · 2019-09-21 07:15:16

Do *what*?
The resolution is just a random side-effect, but eg. "xdotool key ctrl" will virtually press and release the ctrl-key.

Arch Linux

#1 2019-09-20 05:36:15

up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#2 2019-09-20 05:54:31

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#3 2019-09-20 06:23:13

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#4 2019-09-20 07:21:09

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#5 2019-09-20 13:55:56

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#6 2019-09-20 14:05:08

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#7 2019-09-20 15:38:28

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#8 2019-09-20 15:41:33

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#9 2019-09-20 15:44:22

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#10 2019-09-20 15:54:29

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#11 2019-09-20 16:06:47

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#12 2019-09-20 16:09:15

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#13 2019-09-20 16:24:30

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#14 2019-09-20 16:34:29

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#15 2019-09-20 16:38:14

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#16 2019-09-20 16:46:40

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#17 2019-09-20 20:07:15

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#18 2019-09-21 00:39:23

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

#19 2019-09-21 07:15:16

Re: up (arrow) key does not work in gnome-terminal after upgrade to 3.34

Board footer