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 167450 - Cant enter 'pipe' symbol using vino and uk keyboard
Cant enter 'pipe' symbol using vino and uk keyboard
Status: RESOLVED DUPLICATE of bug 155900
Product: vino
Classification: Applications
Component: Server
unspecified
Other All
: Normal blocker
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-02-15 10:17 UTC by Graham Hudspith
Modified: 2005-05-20 16:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Graham Hudspith 2005-02-15 10:17:58 UTC 
Please describe the problem:
Connecting to a vino session using vncviewer and a uk keyboard, cannot enter
either a 'pipe' symbol or a 'pounds-sterling' symbol.

Doing 'shift-\' gets a '\' instead of a 'pipe' symbol.

Doing 'shift-3' gets a '3' instead of a 'pounds-sterling' symbol.

Can live without the 'pounds-sterling' symbol, but no 'pipe' symbol is
incredibly limiting under Linux!


Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Happens on various versions of vncviewer, so suspect problem is at vino end.
Today's version of vncviewer is 4.0b4 from www.realvnc.com.
Comment 1 Graham Hudspith 2005-02-15 10:25:10 UTC 
Forgot to add ...

If I start up a "real" vncserver (instead of connecting to a vino session),
everything works fine. Well, apart from fact that it is a new session instead of
connecting to the existing X server!

Server (either vino or realvnc) is running under Fedora Core 3, currently.
However, can also reproduce problem with Gnome 2.8 under Gentoo.

[gwh@snowball ddt]$ rpm -qa | grep -i vnc
vnc-server-4.0-8
vnc-4.0-8
Comment 2 Mark McLoughlin 2005-05-20 16:18:55 UTC 
Looks like the same bug as bug #155900

(This will be fixed real soon)

*** This bug has been marked as a duplicate of 155900 ***