After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 529408 - need to special-case Shift+Tab
need to special-case Shift+Tab
Product: vino
Classification: Applications
Component: Server
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
: 565631 (view as bug list)
Depends on:
Reported: 2008-04-22 18:05 UTC by Dan Winship
Modified: 2020-11-12 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Dan Winship 2008-04-22 18:05:52 UTC
After bug 353304 was closed, someone commented that "Shift+Tab" no longer worked as he expected. (Starting at The problem is that clients are inconsistent about whether Shift+Tab is "Shift+Tab" or "ISO_Left_Tab".

I've just discovered that the RFB protocol spec actually discusses this case and recommends that servers *should* have a special case here:

• There is no universal standard for “backward tab” in the X Window System.
  On some systems shift+tab gives the keysym “ISO Left Tab”, on others it gives
  a private “BackTab” keysym and on others it gives “Tab” and applications tell
  from the shift state that it means backward-tab rather than forward-tab. In the
  RFB protocol the latter approach is preferred. Viewers should generate a shifted
  Tab rather than ISO Left Tab. However, to be backwards-compatible with ex-
  isting viewers, servers should also recognise ISO Left Tab as meaning a shifted
Comment 1 Dan Winship 2009-01-08 14:57:07 UTC
*** Bug 565631 has been marked as a duplicate of this bug. ***
Comment 2 Chris Howie 2011-11-18 16:44:57 UTC
There is a Debian bug report regarding this issue:

I attached a (probably wrong) patch to that bug some time back that resolves the issue for me.  I don't know if it's the right way to fix the problem, but this is a really annoying bug for me and if there's any work I can do to speed along its resolution I'd be more than willing to invest the time.
Comment 3 André Klapper 2020-11-12 12:24:13 UTC
Vino is not under active development anymore and unmaintained.

Please use gnome-remote-desktop instead.

Closing this report as WONTFIX to reflect reality.