Bug 646089 - TightVNC input unusable with non-US keyboard layout on the client
Summary: TightVNC input unusable with non-US keyboard layout on the client
Status: RESOLVED DUPLICATE of bug 400520
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Forgotten User Wum0mkMcd8
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-13 11:57 UTC by Thomas Bächler
Modified: 2010-10-13 21:50 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Bächler 2010-10-13 11:57:33 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100928 Firefox/3.6

Running a TightVNC server on openSuSE 11.3 and connecting with a client that has a non-US keyboard, typing certain necessary characters becomes impossible:

- Typing Shift+'7' on a German layout should produce '/', but yields '&' instead.
- Typing Shift+',' should produce ';', but instead yields ':'

When typing another shift key combination directly before that (let's say Shift+'8' for '(') and then typing the desired combination without releasing the shift key, the correct character is printed.

This is a regression from openSuSE 11.2, where VNC worked as expected.

Reproducible: Always
Comment 1 Stefan Dirsch 2010-10-13 14:12:41 UTC 
dup

*** This bug has been marked as a duplicate of bug 400520 ***
Comment 2 Thomas Bächler 2010-10-13 14:35:46 UTC 
While most of the symptoms are similar, this is not a duplicate of 400520.

The options posted as possible workarounds (-kb/+kb) do not exist for tightvnc's Xvnc program. In fact, none of the solution or workaround information in 400520 is applicable to tightvnc as far as I can see.
Comment 3 Stefan Dirsch 2010-10-13 21:32:49 UTC 
(In reply to comment #2)
> While most of the symptoms are similar, this is not a duplicate of 400520.
> 
> The options posted as possible workarounds (-kb/+kb) do not exist for
> tightvnc's Xvnc program. In fact, none of the solution or workaround
> information in 400520 is applicable to tightvnc as far as I can see.

openSUSE 11.3 does not ship tightvnc's Xvnc, so I could also close this bug as INVALID. Does this sound any better? BTW, Bug #400520 fixes the issue in xf4vnc's Xvnc patched into xorg-server sources.
Comment 4 Thomas Bächler 2010-10-13 21:50:15 UTC 
Okay, I seem to have overlooked that, thanks for clarifying.