Bug 531479 - Cyrillic symbols do not accepted by remote side
Summary: Cyrillic symbols do not accepted by remote side
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vino
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-28 14:38 UTC by Alexey Kuznetsov
Modified: 2014-06-18 09:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:38:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
mini:1.log (165.33 KB, text/plain)
2009-10-28 14:45 UTC, Alexey Kuznetsov
no flags Details

Description Alexey Kuznetsov 2009-10-28 14:38:49 UTC
I have f12 server with tigervnc module enabled, client side is booth: vncviewer && vinagre.

When i did type several symbols in cyrrilic, it just ignored by server side.

Comment 1 Alexey Kuznetsov 2009-10-28 14:45:15 UTC
Created attachment 366449 [details]
mini:1.log

Comment 2 Bug Zapper 2009-11-16 14:30:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora Update System 2010-04-14 12:16:03 UTC
tigervnc-1.0.1-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/tigervnc-1.0.1-1.fc12

Comment 4 Alexey Kuznetsov 2010-04-14 12:46:31 UTC
the same here.

i tried windows + vncviewer / osx + desktop share / linux + vinagre. i unable to send cyrilics to the server.

Comment 5 Adam Tkac 2010-04-14 13:13:55 UTC
(In reply to comment #4)
> the same here.
> 
> i tried windows + vncviewer / osx + desktop share / linux + vinagre. i unable
> to send cyrilics to the server.    

Which versions of tigervnc-server-module and xorg-x11-server-Xorg packages do you use? Additionally, do you use another VNC software on server side, like GNOME's shared desktop (vino package)?

Comment 6 Alexey Kuznetsov 2010-04-14 13:24:10 UTC
tigervnc-server-module-1.0.1-1.fc12.ppc
xorg-x11-server-Xorg-1.7.6-1.fc12.ppc

yes i do. i use gnome shared desktop, i thought it uses same librarys.

Comment 7 Fedora Update System 2010-04-15 03:10:53 UTC
tigervnc-1.0.1-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tigervnc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tigervnc-1.0.1-1.fc12

Comment 8 Adam Tkac 2010-04-20 13:43:10 UTC
(In reply to comment #6)
> tigervnc-server-module-1.0.1-1.fc12.ppc
> xorg-x11-server-Xorg-1.7.6-1.fc12.ppc
> 
> yes i do. i use gnome shared desktop, i thought it uses same librarys.    

Please update your xorg-x11-server-Xorg package to at least xorg-x11-server-Xorg-1.7.6-3.fc12.ppc (currently in updates-testing repo) and then try to retest this issue, please. Additionally, it's not so reliable to export one display with multiple VNC software. Please use only libvnc.so module in this case.

Comment 9 Alexey Kuznetsov 2010-04-20 15:46:47 UTC
With last updates:

- gnome shared desktop still fail
- direct (?) connect fine.

the same desktop, at the same moment.

Comment 10 Adam Tkac 2010-04-21 14:10:22 UTC
(In reply to comment #9)
> With last updates:
> 
> - gnome shared desktop still fail
> - direct (?) connect fine.

Just for clarification:

- which X server do you use when you export GNOME via "shared desktop" functionality? Is it /usr/bin/X or /usr/bin/Xvnc (or /usr/bin/vncserver)?

- with "direct" you mean Xorg + libvnc.so module? (check if you have "Load vnc" in your /etc/X11/xorg.conf) Or you mean "Xvnc" binary, standalone VNC server provided by tigervnc-server package

Thank you in advance for your feedback.

Comment 11 Alexey Kuznetsov 2010-04-21 17:20:00 UTC
i'm not really sure which one is which.

i have default fedora 12 setup on my ppc machine. And "direct" here is mean direct connect to 5900 port. It was started by vncserver command. 5901 port is opened by System/Preferences/Remote desktop dialog, and still have cyrillic problem.

Sorry, never dig in which is what.

Comment 12 Fedora Update System 2010-05-07 03:58:21 UTC
tigervnc-1.0.1-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Alexey Kuznetsov 2010-05-07 05:21:58 UTC
i reported against other component, and there bug still not fixed. why closed?

Comment 14 Adam Tkac 2010-05-07 11:33:15 UTC
(In reply to comment #13)
> i reported against other component, and there bug still not fixed. why closed?    

This happened automatically, sorry for troubles. As written in comment #11 this is problem in vino, it doesn't accept cyrilic symbols. Reassigning to proper component for further inspection.

Comment 15 Bug Zapper 2010-11-04 08:59:49 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 16 Bug Zapper 2010-12-04 03:38:23 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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