Bug 500708

Summary:	Can't use Russian(Cyrillic) keyboard layout to type any data
Product:	[Fedora] Fedora	Reporter:	Pavel <100megabit>
Component:	vino	Assignee:	Søren Sandmann Pedersen <sandmann>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	100megabit, atodorov, kem, pahan, sandmann
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://bugzilla.gnome.org/show_bug.cgi?id=579718
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-18 09:26:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel 2009-05-13 18:56:58 UTC

Please describe the problem:
I am using Linux Fedora 10 and Remote desktop Gnome 2.24.1.
When I am connecting to my Linux remote desktop from Windows machine
using UltraVNC client(or RealVNC) it's impossible to send Cyrillic letters.
Windows uses Windows-1251 charset anf Linux UTF8.
When I switch typing into Russian layout nothing is printed.
When I switch back to English - everything works fine.


Steps to reproduce:
1.Start vino server on linux Fedora 10 (utf8)
2.Connect to server from any VNC client from Windows(UltraVNC or RealVNC).
3.Focus cursor on any place where you can type something from the keyboard.
4.Switch clients layout to RU(Cyrillic, Windows 1251)
5.You can't continue typing because nothing is send to server.
6.Switch back to English layout - everything is ok.


Actual results:
Cyrillic letters can't be sent from any windows VNC client to vino server.

Expected results:
I expected the same behaviour as I typed something in English.

Does this happen every time?
Yes, it happens everytime. So it is impossible to communicate at full strength
from Windows machine to my Linux box using vino server.

Other information:
One way to solve the problem is to use PuTTY+xming, but I prefer vino server to
be fixed.

Comment 1 Piotr Drąg 2009-05-13 19:40:48 UTC

Changing to the right component.

Comment 2 Pavel 2009-06-07 18:57:18 UTC

Ultra VNC 1.0.5.6 works, but it doesn't print russian letter 'у'(u).

Comment 3 Bug Zapper 2009-11-18 11:57:08 UTC

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 09:26:03 UTC

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.