Shift+insert doesn't work

stee1rat · 2019-04-06 14:09:19

I am not sure if this is Gnome or OS related problem: I hadn't updated my system for a while and decided to finally do pacman -Syu. After the update the key combination SHIFT+INSERT stopped working. CTRL+V, CTRL+C and CTRL+INSERT are all working fine. Can someone, please, help me diagnose the problem?

seth · 2019-04-06 14:17:30

Since this is a local shortcut and the clipboard itself seems ok, it is very relevant in what particular client(s) this fails.
Since it's gnome: X11 or wayland? (And did you try the other display server?)

stee1rat · 2019-04-06 14:24:29

It is Gnome with X11. I have not tried any other display servers. Also I am not sure what that means. Do you mean other DE/WM or like X11/Wayland?

seth · 2019-04-06 15:12:39

X11 and wayland are the display server (protocols), but the crucial question is for the actual clients (libreoffice, gedit, firefox, …) since this shortcut is handled by them, not the display server nor the desktop environment.

Edit:

xdotool key "XF86LogGrabInfo"

will print the grabbed shortcuts into your xorg log - in case the shortcut is globally occupied by something.

Last edited by seth (2019-04-06 15:13:39)

stee1rat · 2019-04-06 15:25:56

I would say it does not work across the system: chromium, firefox, visual studio code. What should I do with the information provided by xdotool?

Last edited by stee1rat (2019-04-06 15:29:13)

seth · 2019-04-06 15:28:08

Read it and see whether the shortcut is among the grabs?
You can also try whether xev reads the combination (and as what)

stee1rat · 2019-04-06 15:29:37

Logged in into i3 and SHIFT+INSERT does work perfectly there. So I guess it is gnome's problem then? I wonder how to fix it.

seth · 2019-04-06 15:31:30

See what grabs the shortcut or whether gnome gets you a different keyboard layout and shift+ins isn't actually shift+ins (though I'm not aware of common layouts where insert isn't insert)

stee1rat · 2019-04-06 16:03:44

The output of xev when I press shift+insert

KeyPress event, serial 37, synthetic NO, window 0x2a00001,
    root 0x29c, subw 0x0, time 1795946, (-764,-36), root:(677,447),
    state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 37, synthetic NO, window 0x2a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 37, synthetic NO, window 0x2a00001,
    mode NotifyUngrab, detail NotifyAncestor

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

KeyRelease event, serial 37, synthetic NO, window 0x2a00001,
    root 0x29c, subw 0x0, time 1798458, (-1132,112), root:(309,595),
    state 0x1, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Not sure what that means.

seth · 2019-04-06 16:05:02

That means the shortcut is globally grabbed. The xorg log (after you issued the xdotool command) will tell you by what client.

stee1rat · 2019-04-06 16:14:09

Could you, please, elaborate a little on how to use xdotool? I issued xdotool key "XF86LogGrabInfo" and got a lot of messages in journalctl and nothing in /var/log/Xorg.0.log.

Last edited by stee1rat (2019-04-06 16:14:27)

seth · 2019-04-06 16:18:57

Because GDM stores the xorg log in the journal, https://wiki.archlinux.org/index.php/Xorg#General

stee1rat · 2019-04-06 16:27:19

So what should I be looking for in the log? The key code for the insert is 161 and I have a bunch of messages like these logged by xdotool:

Apr 06 19:09:46 monster /usr/lib/gdm-x-session[803]:   grab 0x4021e0f8 (xi2), type 'KeyPress' on window 0x29c
Apr 06 19:09:46 monster /usr/lib/gdm-x-session[803]:     detail 161 (mask 0), modifiersDetail 10 (mask 0)
Apr 06 19:09:46 monster /usr/lib/gdm-x-session[803]:     device 'Virtual core keyboard' (3), modifierDevice 'Virtual core keyboard' (3)
Apr 06 19:09:46 monster /usr/lib/gdm-x-session[803]:       xi2 event mask 0xc 0 0 0
Apr 06 19:09:46 monster /usr/lib/gdm-x-session[803]:     owner-events false, kb 0 ptr 1, confine 0x0, cursor 0x0

seth · 2019-04-06 16:36:00

You can isolate the grab by turning it active
Run

sleep 2; xdotool key XF86LogGrabInfo

and press Shift+Ins within 2 seconds, keep it down until some moments after xdotool completed.

stee1rat · 2019-04-06 17:00:30

Is this somehow related?

Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   grab 0x4021cf8c (xi2), type 'KeyPress' on window 0x29c
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:     detail 14 (mask 0), modifiersDetail 67 (mask 0)
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:     device 'Virtual core keyboard' (3), modifierDevice 'Virtual core keyboard' (3)
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       xi2 event mask 0xc 0 0 0
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:     owner-events false, kb 0 ptr 1, confine 0x0, cursor 0x0
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 840 /usr/lib/at-spi2-registryd --use-gnome-session
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 856 /usr/bin/gnome-shell
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 950 /usr/lib/gsd-keyboard
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 953 /usr/lib/gsd-power
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 961 /usr/lib/gsd-media-keys
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 972 /usr/lib/gsd-clipboard
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 973 /usr/lib/gsd-wacom
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 981 /usr/lib/gsd-color
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 987 /usr/lib/gsd-xsettings
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 902 /usr/bin/pulseaudio --daemonize=no
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 1108 /usr/bin/gnome-software --gapplication-service
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 1105 /usr/lib/evolution-data-server/evolution-alarm-notify
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:   Printing all registered grabs of client pid 1226 /usr/lib/chromium/chromium --ppapi-flash-version=32.0.0.156 --ppapi-flash-path=/usr/l>

seth · 2019-04-06 20:00:45

Ther should be something like

[133351.148] (II) Printing all currently active device grabs:
[133351.148] Active grab 0xe00000 (core) on device 'Virtual core keyboard' (3):
[133351.148]       client pid 469 /usr/bin/foobar
[133351.148]       at 133351146 (from active grab) (device thawed, state 1)
[133351.148]         core event mask 0x3
[133351.148]       owner-events false, kb 1 ptr 1, confine 0, cursor 0x0
[133351.148] (II) End list of active device grabs

stee1rat · 2019-04-06 23:27:45

I have this block:

Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]: (II) Printing all currently active device grabs:
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]: Active grab 0x40205169 (xi2) on device 'Virtual core keyboard' (3):
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       client pid 856 /usr/bin/gnome-shell
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       at 1071222 (from passive grab) (device thawed, state 1)
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       xi2 event mask for device 3: 0xc000
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       passive grab type 2, detail 0x76, activating key 118
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]:       owner-events false, kb 0 ptr 1, confine 0, cursor 0x0
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]: (II) End list of active device grabs
Apr 06 19:52:05 monster /usr/lib/gdm-x-session[806]: Printing all currently registered grabs

And indeed, after I killed 856 process shift+insert started working. Now how do I know what causes it?

seth · 2019-04-07 06:10:42

Something inside the gnome-shell process. Could be an extension, could be triggered by some shortcut config of gnome. Entirely opaque to the rest of the system.
That's the beauty if your goal is to cram as much stuff as possible into a single process…

Does the shortcut cause any notable reaction when pressing it?
I'd first check the shortcut settigns on whether it shows up there.
Then try to disable all extension, because it's a stupid idea to grab that combo and it thus seems unvetted.
Next thing would be to try w/ a fresh user account and see whether it occurs there as well (ie. is some sort of default behavior)

Edit: oranges of the investigation…

Last edited by seth (2019-04-07 06:11:26)

stee1rat · 2019-04-07 06:54:14

You know what is the funniest thing? I booted into system today and shift+insert is still working, how is it possible? Before that reboot did not help.

seth · 2019-04-07 07:00:08

Possibly an extension got updated or not (yet) loaded?

Foucault · 2019-04-14 12:08:02

Sorry for replying here, but I'm facing the same problem with Gnome. This happens on a vanilla Gnome X11 installation with two keyboard layouts. Whenever I'm switching from the default layout to a secondary one insert stops working (and by extension shift insert). It doesn't matter if I switch back to the default layout, it won't go away until I logout and login again, or restart gnome-shell. I believe it's gnome specific as this doesn't happen with Cinnamon, for instance. I've been trying to debug the thing a whole day without much success.

You can check if this happens with your installation very simply as such.

1. Install geany; a text editor. You can replicate it anywhere but it's easier with a visual cue.
2. When you hit insert it should change the input mode to replace, so the caret will change from | to _
3. Change keyboard layout either from the shortcut (super+space or whatever combination you've configured) or from the keyboard indicator on the panel
4. With geany focused hit insert; the cursor does not turn back to regular input and the current line flashes instead.

Any ideas? Just fyi my secondary layout is Greek. I've tried reverting gnome-desktop, gnome-shell, gtk3 and libinput (recent-ish updates) without success.

Last edited by Foucault (2019-04-14 12:38:04)

Arch Linux

#1 2019-04-06 14:09:19

Shift+insert doesn't work

#2 2019-04-06 14:17:30

Re: Shift+insert doesn't work

#3 2019-04-06 14:24:29

Re: Shift+insert doesn't work

#4 2019-04-06 15:12:39

Re: Shift+insert doesn't work

#5 2019-04-06 15:25:56

Re: Shift+insert doesn't work

#6 2019-04-06 15:28:08

Re: Shift+insert doesn't work

#7 2019-04-06 15:29:37

Re: Shift+insert doesn't work

#8 2019-04-06 15:31:30

Re: Shift+insert doesn't work

#9 2019-04-06 16:03:44

Re: Shift+insert doesn't work

#10 2019-04-06 16:05:02

Re: Shift+insert doesn't work

#11 2019-04-06 16:14:09

Re: Shift+insert doesn't work

#12 2019-04-06 16:18:57

Re: Shift+insert doesn't work

#13 2019-04-06 16:27:19

Re: Shift+insert doesn't work

#14 2019-04-06 16:36:00

Re: Shift+insert doesn't work

#15 2019-04-06 17:00:30

Re: Shift+insert doesn't work

#16 2019-04-06 20:00:45

Re: Shift+insert doesn't work

#17 2019-04-06 23:27:45

Re: Shift+insert doesn't work

#18 2019-04-07 06:10:42

Re: Shift+insert doesn't work

#19 2019-04-07 06:54:14

Re: Shift+insert doesn't work

#20 2019-04-07 07:00:08

Re: Shift+insert doesn't work

#21 2019-04-14 12:08:02

Re: Shift+insert doesn't work

Board footer