Glam Prestige Journal

Bright entertainment trends with youth appeal.

On a Windows 10 box, I found that I can't send Shift+Tab to (at least some) applications, such as Notepad++.

I am using that machine remotely via a VNC session (Remmina client under Xubuntu, the Windows machine is running TightVNC server) and my original thought was that the shortcut gets processed by the VNC client or the local OS, but testing the same with a remote Xubuntu machine does send Shift+Tab through; e.g. I could unindent a line in Mousepad which is Xubuntu's default text editor.

Is there a Windows 10 setting or shortcut causing Shift+Tab to be directed away from Notepad++?

Any information on how I could debug this issue would also be appreciated.

16

1 Answer

The solution below fixed the problem for the user. The problem is that basically the combination of Shift+Tabis not unique and may be mistaken when transmitted to the server. This problem may occur when using VNC between non-Linux and Linux computers.

This same problem is evoked in the postusing Alt-Gr from a Windows VNC client to vino. Although dating from 2007, theanswer by Dan Winshipstill applies:

the problem is that the server side (the machine running vino) considers the Tab key to have two different keysyms on it (Tab and ISO_Left_Tab respectively), whereas the client side considers it to only have one keysym on it, and so expects Shift+Tab to be treated the same way as Shift+Up Arrow.

(I assume the client is a non-Linux box?)

I don't think there's a "clean" fix for this; the client and server are both behaving reasonably, this is just one of those warts in the protocol. The only way to fix it would be to special-case the Tab key in the code. If you want to suggest doing that, you should probably file a new bug (and refer to the comments in this one).

You can work around the bug by running

xmodmap -e 'keycode 23 = Tab'

(on the vino box). This doesn't seem to interfere with ordinary gtk operation, so it's probably safe to do this all the time. (Eg, putting 'keycode 23 = Tab' into ~/.xmodmap or ~/.Xmodmap or something might cause it to automatically be evaluated, depending on your distro)

In the more recent postShift + special key does not work using real vnc viewer in windows to access ubuntuwhere the same method was used to fix the problem:

Run in Ubuntu terminal: xmodmap -e 'keycode 23 = Tab'

EDIT: to make the fix permanent run sudo vim /usr/share/X11/xkb/symbols/pc and change the line

key <TAB> { [ Tab, ISO_Left_Tab ] };

to

key <TAB> { [ Tab ] };

After that reboot.

2

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy