Bug 1005055 - vnc server does not accept national characters from client
Summary: vnc server does not accept national characters from client
Keywords:
Status: CLOSED DUPLICATE of bug 989502
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 07:05 UTC by Marian Ganisin
Modified: 2013-09-10 10:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-10 07:36:47 UTC
Type: Bug


Attachments (Terms of Use)

Description Marian Ganisin 2013-09-06 07:05:30 UTC
Description of problem:

I use national cz xkb layout on my computer. Since Fedora 19 remote tigervnc server accepts neither  keypress of national characters nor the shift variant of these keys (numbers).

This wasn't issue with Fedora 18 so this is a regression in behavior.

I changed nothing on client, just server side was updated to Fedora 19 and recent tigervnc version.

Version-Release number of selected component (if applicable):
tigervnc-server-1.3.0-3.fc19.x86_64

How reproducible:


Steps to Reproduce:
1. start tigervnc server on Fedora 19
2. on Fedora 18 setup keyboard layout: setxkbmap cz
3. use (tiger) vnc viewer from F18 to connect to server
4. try to put some national text into vnc client.

Run tigervnc server on Fedora 18 and check correct behavior

Actual results:
keypress with national charater including shift variant is not accepted by server

Expected results:
all keys are propagated to vnc server session

Comment 1 Tim Waugh 2013-09-09 16:03:30 UTC
I think this might be a duplicate of bug #989502?

Comment 2 Marian Ganisin 2013-09-10 07:36:47 UTC
(In reply to Tim Waugh from comment #1)
> I think this might be a duplicate of bug #989502?
Didn't I close it? damn. :( (Now I hope that I didn't close another bug by accident, because I swear that I closed this) Well I have found that my issue is caused by incorrect locales, target machine with vnc server had configured LANG=en_US instead of LANG=en_US.UTF-8, with utf-8 suffix I was able to put my characters. It still seems to be regression as the Fedora-18 running vnc server had same LANG=en_US without UTF-8, however I am fine with that.

Nevertheless utf-8 suffix didn't solve all my issues. I still have many problems, however you're right, it really seems to be exactly same class as the issue described in Bug 989502. I will close this one and will monitor/contribute to the latter.

Comment 3 Tim Waugh 2013-09-10 10:06:17 UTC

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


Note You need to log in before you can comment on or make changes to this bug.