Menu

#8 problem with double quote

open
None
5
2003-01-19
2003-01-19
Tony Austin
No

I am using Xvnc only.

The problem refers to the double quote character, which
is the shifted 2 on a UK keyboard; the @ sign, which is
shifted apostrophe on UK keyboard, has the same problem
too.

If I type fast, I often get "2 instead of just plain "
(this is not a quoted phrase, the quotes are literally
characters). At first I thought it was just my bad
typing, then I thought it was the keyboard, then I
thought it was vnc in general but, after extensive
research and comparisons, I am pretty sure that it only
happens with Xvnc from the xf4vnc version.

That is to say, I think it _doesn't_ happen with the
Xvnc from TightVNC but it does with both the released
and beta versions of Xvnc from xf4vnc.

Discussion

  • Alan Hourihane

    Alan Hourihane - 2003-01-19
    • assigned_to: nobody --> alanh
     
  • Alan Hourihane

    Alan Hourihane - 2003-01-19

    Logged In: YES
    user_id=2372

    I doubt this is xf4vnc specific.

    What OS are you using as the viewer ?

    What kernel are you using on the Xvnc server ?

    Is it in an xterm, emacs something else ?

    more details of the enviroment would be good.

     
  • Tony Austin

    Tony Austin - 2003-01-19

    Logged In: YES
    user_id=337107

    My reason for thinking it is to do with xf4vnc is that if I
    switch back and forth between the Tightvnc and xf4vnc
    versions of Xvnc I can consistently reproduce the problem
    with the xf4vnc version but don't get the problem with Tightvnc.

    I get the problem with the vncviewer on both WinXP and Linux.

    I get the problem on two machines running Xvnc server,
    kernels are:

    Linux G2 2.4.19-gentoo-r9 #3 Tue Nov 19 18:38:29 GMT 2002
    i686 AMD Athlon(tm) Processor AuthenticAMD

    and

    Linux mail 2.4.20 #2 Thu Dec 5 23:20:42 UTC 2002 i586
    AMD-K6(tm) 3D processor AuthenticAMD GNU/Linux

    It happens with xterm, gnome-terminal, openoffice.org, mozilla.

    It looks like a key bounce problem but only happens on a
    couple of keys, notably the double quote. I have tried
    altering the keyboard repeat rate with xset, but I suspect
    that vnc does not pay any attention to this.

     
  • Alan Hourihane

    Alan Hourihane - 2003-01-19

    Logged In: YES
    user_id=2372

    I'll try and take a look this week, but I don't know if I'll be able
    to replicate it.

    Can you try starting Xvnc without the XKB extension by using
    the -kb flag to Xvnc.

     
  • Alan Hourihane

    Alan Hourihane - 2003-01-19

    Logged In: YES
    user_id=2372

    Just had chance to try this now, and I can't replicate this at
    all.

    Unfortunately I won't be able to fix it until I can actually see
    the problem.

     
  • Tony Austin

    Tony Austin - 2003-01-20

    Logged In: YES
    user_id=337107

    I have started Xvnc with -kb option and this seems to have
    cured the double quote problem; I am not clear what the
    implications of this might be, I have tried reading some of
    the documentation but it's over my head.

     
  • Alan Hourihane

    Alan Hourihane - 2003-02-07

    Logged In: YES
    user_id=2372

    it's disabling the XKeyboard Extension. tightVNC doesn't have
    this extension at all.

    When I release xf4vnc 4.3.0 at the end of Feb, can you try
    this again.

     
  • jpap

    jpap - 2003-02-22

    Logged In: YES
    user_id=421032

    I get a similar problem.

    When I type quickly, some of the characters I type are
    entered twice.

    e.g. If I type "dir" quickly, sometimes I get "ddir" at my
    prompt. This is with XTerm and ATerm. The above also
    occur when I type in other applications, such as Mozilla.

    I am running the viewer on WinXP (TightVNC viewer), whereas
    the Linux machine is running Mandrake 9.1 RC1 (default
    kernel 2.4.21-pre4-6), and KDE 3.1 as my window manager.

    I am running xf4vnc 4.2.0.1 with the r128 4.2.0 driver.

    xf4vnc is great otherwise!! Extremely fast, and exactly what I
    wanted. The reason why I didn't use the KDE 3.1 desktop
    sharing feature was that it wasn't available for non-root users
    as an uninvited connection. i.e. someone at the terminal had
    to generate an invitation each time. I just wanted to remote
    control my desktop from another machine at all times.

    Please let me know if I can help you track this bug down -- I
    don't like typing slow! :-)

     
  • jpap

    jpap - 2003-02-22

    Logged In: YES
    user_id=421032

    I just tried this with a FreeBSD VNC viewer (no tight
    extensions). It worked fine.

    I then tried it with the original Windows VNC viewer. The
    same problem occurred. If I turn all the settings off (basically
    use RAW encoding, and nothing else), it still occurs.

     
  • Alan Hourihane

    Alan Hourihane - 2003-02-22

    Logged In: YES
    user_id=2372

    As mentioned furthur down in this open report....

    If you start X with the -kb option, then this works.

     
  • jpap

    jpap - 2003-02-23

    Logged In: YES
    user_id=421032

    It works! Thanks! :-)

     
  • Tony Austin

    Tony Austin - 2003-03-03

    Logged In: YES
    user_id=337107

    Problem still exists with xf4vnc 4.3.0. This may be because
    of the error that shows up in the log file when the -kb
    option is not set, as follows:

    03/03/2003 23:01:43 Xvnc version XF4VNC-4.3.0
    03/03/2003 23:01:43 Copyright (C) 1999 AT&T Laboratories
    Cambridge.
    03/03/2003 23:01:43 Copyright (C) 2000-2002 Constantin
    Kaplinsky.
    03/03/2003 23:01:43 Copyright (C) 2001-2002 Alan Hourihane.
    03/03/2003 23:01:43 All Rights Reserved.
    03/03/2003 23:01:43 See http://www.uk.research.att.com/vnc
    for information on VNC
    03/03/2003 23:01:43 See http://www.tightvnc.com for
    TightVNC-specific information
    03/03/2003 23:01:43 See http://xf4vnc.sf.net for
    xf4vnc-specific information
    03/03/2003 23:01:43 Desktop name 'X' (G2:4)
    03/03/2003 23:01:43 Protocol version supported 3.3
    03/03/2003 23:01:43 RGB format 5 6 5
    03/03/2003 23:01:43 Listening for VNC connections on TCP
    port 5904
    03/03/2003 23:01:43 Listening for HTTP connections on TCP
    port 5804
    03/03/2003 23:01:43 URL http://G2:5804
    03/03/2003 23:01:44 Xvnc version XF4VNC-4.3.0
    03/03/2003 23:01:44 Copyright (C) 1999 AT&T Laboratories
    Cambridge.
    03/03/2003 23:01:44 Copyright (C) 2000-2002 Constantin
    Kaplinsky.
    03/03/2003 23:01:44 Copyright (C) 2001-2002 Alan Hourihane.
    03/03/2003 23:01:44 All Rights Reserved.
    03/03/2003 23:01:44 See http://www.uk.research.att.com/vnc
    for information on VNC
    03/03/2003 23:01:44 See http://www.tightvnc.com for
    TightVNC-specific information
    03/03/2003 23:01:44 See http://xf4vnc.sf.net for
    xf4vnc-specific information
    03/03/2003 23:01:44 Desktop name 'X' (G2:4)
    03/03/2003 23:01:44 Protocol version supported 3.3
    03/03/2003 23:01:44 RGB format 5 6 5
    03/03/2003 23:01:44 Listening for VNC connections on TCP
    port 5904
    03/03/2003 23:01:44 Listening for HTTP connections on TCP
    port 5804
    03/03/2003 23:01:44 URL http://G2:5804
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "unknown" for geometry
    include
    > Exiting
    > Abandoning geometry file "default"
    Errors from xkbcomp are not fatal to the X server

     
  • Alan Hourihane

    Alan Hourihane - 2003-03-05

    Logged In: YES
    user_id=2372

    You'll need the new xkbcomp files from XFree86 4.3.0 try
    without -kb.

     
  • Alan Hourihane

    Alan Hourihane - 2003-03-05

    Logged In: YES
    user_id=2372

    try it here too.

    setxkbmap -rules xfree86 -layout us

    remember to do it within an xterm of the current Xvnc server.

     
  • Tony Austin

    Tony Austin - 2003-03-11

    Logged In: YES
    user_id=337107

    I have upgraded my Xfree86 to 4.3.0 so taht I now have the
    xkbcomp files.

    Following your instructions, I am now launching Xvnc without
    -kb. I get the following in my .vnc/host:4.log:-

    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "unknown" for geometry
    include
    > Exiting
    > Abandoning geometry file "default"
    Errors from xkbcomp are not fatal to the X server

    I have also run "setxkbmap -rules xfree86 -layout us" from
    within a terminal in client session, which gives me:-

    tony@G2 tony $ setxkbmap -rules xfree86 -layout us
    Couldn't interpret _XKB_RULES_NAMES property
    Use defaults: rules - 'xfree86' model - 'pc101' layout - 'us'
    Segmentation fault
    tony@G2 tony $

    the above command completes without comment in a real X session.

    I have read the man for xkbcomp and setxkbmap but have to
    admit to not understanding what I am looking at.

     
  • Alan Hourihane

    Alan Hourihane - 2003-03-11

    Logged In: YES
    user_id=2372

    Can you give me the full log from Xvnc, and also the
    commandline flags that your starting Xvnc with.

     
  • Tony Austin

    Tony Austin - 2003-03-12

    Logged In: YES
    user_id=337107

    Full Xvnc log:

    12/03/2003 16:51:53 Xvnc version XF4VNC-4.3.0
    12/03/2003 16:51:53 Copyright (C) 1999 AT&T Laboratories
    Cambridge.
    12/03/2003 16:51:53 Copyright (C) 2000-2002 Constantin
    Kaplinsky.
    12/03/2003 16:51:53 Copyright (C) 2001-2002 Alan Hourihane.
    12/03/2003 16:51:53 All Rights Reserved.
    12/03/2003 16:51:53 See http://www.uk.research.att.com/vnc
    for information on VNC
    12/03/2003 16:51:53 See http://www.tightvnc.com for
    TightVNC-specific information
    12/03/2003 16:51:53 See http://xf4vnc.sf.net for
    xf4vnc-specific information
    12/03/2003 16:51:53 Desktop name 'X' (G2:4)
    12/03/2003 16:51:53 Protocol version supported 3.3
    12/03/2003 16:51:53 RGB format 5 6 5
    12/03/2003 16:51:53 Listening for VNC connections on TCP
    port 5904
    12/03/2003 16:51:53 Listening for HTTP connections on TCP
    port 5804
    12/03/2003 16:51:53 URL http://G2:5804
    12/03/2003 16:51:54 Xvnc version XF4VNC-4.3.0
    12/03/2003 16:51:54 Copyright (C) 1999 AT&T Laboratories
    Cambridge.
    12/03/2003 16:51:54 Copyright (C) 2000-2002 Constantin
    Kaplinsky.
    12/03/2003 16:51:54 Copyright (C) 2001-2002 Alan Hourihane.
    12/03/2003 16:51:54 All Rights Reserved.
    12/03/2003 16:51:54 See http://www.uk.research.att.com/vnc
    for information on VNC
    12/03/2003 16:51:54 See http://www.tightvnc.com for
    TightVNC-specific information
    12/03/2003 16:51:54 See http://xf4vnc.sf.net for
    xf4vnc-specific information
    12/03/2003 16:51:54 Desktop name 'X' (G2:4)
    12/03/2003 16:51:54 Protocol version supported 3.3
    12/03/2003 16:51:54 RGB format 5 6 5
    12/03/2003 16:51:54 Listening for VNC connections on TCP
    port 5904
    12/03/2003 16:51:54 Listening for HTTP connections on TCP
    port 5804
    12/03/2003 16:51:54 URL http://G2:5804
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "unknown" for geometry
    include
    > Exiting
    > Abandoning geometry file "default"
    Errors from xkbcomp are not fatal to the X server

    12/03/2003 16:52:02 Got connection from client 10.0.0.2
    12/03/2003 16:52:02 Protocol version 3.5
    12/03/2003 16:52:02 Ignoring minor version mismatch
    12/03/2003 16:52:04 Full-control authentication passed by
    10.0.0.2
    12/03/2003 16:52:05 Pixel format for client 10.0.0.2:
    12/03/2003 16:52:05 16 bpp, depth 16, little endian
    12/03/2003 16:52:05 true colour: max r 31 g 63 b 31, shift
    r 11 g 5 b 0
    12/03/2003 16:52:05 no translation needed
    12/03/2003 16:52:05 Using hextile encoding for client 10.0.0.2
    12/03/2003 16:52:05 rfbProcessClientNormalMessage: ignoring
    unknown encoding 8
    12/03/2003 16:52:05 Enabling X-style cursor updates for
    client 10.0.0.2
    12/03/2003 16:52:05 Enabling cursor position updates for
    client 10.0.0.2
    12/03/2003 16:52:05 Using image quality level 6 for client
    10.0.0.2
    12/03/2003 16:52:05 Enabling LastRect protocol extension for
    client 10.0.0.2
    12/03/2003 16:52:05 rfbProcessClientNormalMessage: ignoring
    unknown encoding -223

    Command line flags to start vncserver:-

    /bin/su - tony -c "PATH=$PATH:/usr/X11R6/bin; vncserver :4
    -depth 16 -geometry 1270x968"

    ps aux|grep vnc:-

    tony 14474 2.1 3.0 11524 7680 tty1 S 16:51
    0:06 Xvnc :4 -desktop X -httpd /usr/share/tightvnc/classes
    -httpport 5804 -auth /home/tony/.Xauthority -geometry
    1272x968 -depth 16 -rfbwait 120000 -rfbauth
    /home/tony/.vnc/passwd -rfbport 5904 -fp
    /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/truetype

    Regards, Tony

     
  • Alan Hourihane

    Alan Hourihane - 2003-04-14

    Logged In: YES
    user_id=2372

    Tony, from this you need to add the flag -noreset to your
    Xserver to stop
    this double output.

    And can you let me know whether it's still happening.

     
  • Alan Hourihane

    Alan Hourihane - 2003-04-17

    Logged In: YES
    user_id=2372

    Can you try 4.3.0.2 and let me know

     
  • Tony Austin

    Tony Austin - 2003-04-17

    Logged In: YES
    user_id=337107

    I can see no difference on this issue with version 4.3.0.2.
    That is to say that I get the "2 feature unless I use the
    -kb option.

    However, the double output has gone away even without the
    -noreset flag.

    The error message:

    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "unknown" for
    geometry
    include
    > Exiting
    > Abandoning geometry file
    "default"
    Errors from xkbcomp are not fatal to the X server

    still appears in the Xvnc log.

    And I still get the segmentation fault when trying to run:

    #setxkbmap -rules xfree86 -layout us

    Please let me know if I can give you any further info.

    Regards, Tony

     
  • Alan Hourihane

    Alan Hourihane - 2003-04-30

    Logged In: YES
    user_id=2372

    I've convinced myself that these two bugs you reported are
    problems with xkb. I'll try to find them, but don't hold your
    breath. It may get fixed in XFree86, in which case I'll import
    the fix if it does.

     

Log in to post a comment.

MongoDB Logo MongoDB