Bug 122353 - control characters misinterpretted in vnc and Xnest
Summary: control characters misinterpretted in vnc and Xnest
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL: http://freedesktop.org/bugzilla/show_...
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-03 16:37 UTC by Marc Milgram
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-12 15:24:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Marc Milgram 2004-05-03 16:37:18 UTC
Description of problem:
vncserver and Xnest don't handle control keys

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start vncserver
2.Start vncclient
3.Start xterm in vncclient
4.attempt to use control characters in xterm.
Actual results:
control characters interpretted as regular (non-control) characters.

Expected results:
Control characters act as expected.

Additional info:
Can reproduce using Xnest instead of vnc.

Comment 1 Marc Milgram 2004-05-04 14:50:22 UTC
I found some odd behaviour.  I have this problem if I run vncviewer
normally from my workstation.

Last night I ssh'ed from my home machine which runs fedora core 1 to
my work machine which is running fedora core bleeding edge.  From the
bleeding edge machine, I ran vncviewer.  I was shocked that control
characters worked as expected!

But, this doesn't work if ssh from the bleeding edge desktop, and pop
up a VNC viewer.  Nor does it work if I just pop up a vncviewer from
the bleeding edge desktop.

As I mentionned before, this also affects Xnest (is why I clasified it
as an X11 bug).

Comment 2 Mike A. Harris 2004-10-12 07:04:12 UTC
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue.  Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:


If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Comment 3 Marc Milgram 2004-10-12 12:26:44 UTC
I added bug 1609 to freedesktop.org

Comment 4 Mike A. Harris 2004-10-12 15:24:48 UTC
Thanks for the X.Org bug number.  We'll track this in the X.Org
bug tracker now, and review any fixes which become available
for consideration in future updates.

Setting status to "UPSTREAM" for tracking.

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