I am running 11.3 with Remote Admin(VNC) turned on. This has installed TightVNC.
I also have also enabled xinetd to manage the startup of new (incoming) VNC requests.
All this is working just fine. So, what’s the problem, you ask? Its that missing Shift+3 symbol.
To reproduce, I run TightVNC (viewer) from a variety of clients (Win & OpenSUSE) to a number of OpenSUSE servers with xinetd managed VNC services enabled. The Xvnc sessions start and the clients display the KDE log-on screen. You will notice that in the username field that the “£” sign is not displayed.
I have run a parallel VNC service (is it Xvnc or vncserver?) which gave me a twm session. It also is missing the “£” sign, so I conclude that it is not KDE that is causing the problem?
Secondly, a scan through the log file produced by the parallel VNC service shows:
On 11/17/2010 05:36 AM, martinprowe wrote:
>
> I am running 11.3 with Remote Admin(VNC) turned on. This has installed
> TightVNC.
> I also have also enabled xinetd to manage the startup of new (incoming)
> VNC requests.
>
> All this is working just fine. So, what’s the problem, you ask? Its
> that missing Shift+3 symbol.
>
> To reproduce, I run TightVNC (viewer) from a variety of clients (Win &
> OpenSUSE) to a number of OpenSUSE servers with xinetd managed VNC
> services enabled. The Xvnc sessions start and the clients display the
> ‘KDE log-on screen’ (http://www.mpr75.talktalk.net/KDE-Login.png). You
> will notice that in the username field that the “£” sign is not
> displayed.
>
> I have run a parallel VNC service (is it Xvnc or vncserver?) which gave
> me a twm session. It also is missing the “£” sign, so I conclude that it
> is not KDE that is causing the problem?
>
> Secondly, a scan through the log file produced by the parallel VNC
> service shows:
> Code:
> --------------------
> KbdAddEvent: unknown KeySym 0x3a - allocating KeyCode 92
> --------------------
> Has anyone any suggestions on how I can get my pound sign?
>
> Regards, Martin
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Thank you for your comments. I’ve read through that thread…
It seems to be related, but my understanding of the specifics are to limited to be sure! Can anyone advise on how to confirm if it is? Happy to run any tests.
Considering the length of that thread (began June 2008), my sympathy is with the participant who commented, “Can someone PLEASE fix Xvnc/tightvnc?”, I too have been trying to get to the bottom of this for … Oh ages.
Small supplementary question, if I may? This bug report (and many other sources) mentions the “-kb/+kb” (sometimes its quoted as "-xkb) switch. Trying this in the xinetd GUI (or the /etc/xinet.d/vnc) causes the client to report that the “Connection is closed” as soon as it tries to connect. I’m guessing that the -kb is an invalid switch in the xinetd context and is not starting Xvnc?
There’s a “proposed patch” at the bottom of the bug, but it looks to be
for some C-based code so you’d need to get the source, patch it, compile,
and then test. :-\
Good luck.
On 11/17/2010 08:06 AM, martinprowe wrote:
>
> ab@novell.com;2253784 Wrote:
>> Perhaps related to Bug# 400520 at http://bugzilla.novell.com/ but I’m
>> not
>> sure. Let us know if it is.
>
> Thank you for your comments. I’ve read through that thread…
> It seems to be related, but my understanding of the specifics are to
> limited to be sure! Can anyone advise on how to confirm if it is? Happy
> to run any tests.
>
> Considering the length of that thread (began June 2008), my sympathy is
> with the participant who commented, -“Can someone PLEASE fix
> Xvnc/tightvnc?”-, I too have been trying to get to the bottom of this
> for … Oh ages.
>
> Small supplementary question, if I may? This bug report (and many other
> sources) mentions the “-kb/+kb” (sometimes its quoted as "-xkb) switch.
> Trying this in the xinetd GUI (or the /etc/xinet.d/vnc) causes the
> client to report that the “Connection is closed” as soon as it tries to
> connect. I’m guessing that the -kb is an invalid switch in the xinetd
> context and is not starting Xvnc?
>
> Regards, Martin
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
However, I fear that my DIY skills are severity lacking in this respect! All previous attempts to do that sort of thing have ended in tears.
If there are any kind packagers (or whatever the collective noun is, for the very kind folk that do that sort of thing?) out there that could do what is required so that this fix could be included in one of the almost daily updates, I’d be most grateful.
While I wait, is there anyway I can fudge the issue? If I can’t fix the problem at the root, can I fool KDE to do some sort of translation? When it gets the Keycode 92, turn it into keycode 12 (keysym 0xa3, sterling)?
The patch mentioned in Martin’s article above works for me on openSUSE 11.3 (I had issued with a german keyboards and the Umlaut öäü …, as well as some strange keycode mappings with the / for example)
In summary here is what I did:
deinstall Xvnc and tightvnc
install the patch from Index of /~mhopf/vnc_umlauts - it requires some additional packages (libopenssl0_9_8-0.9.8m-2.18.src.rpm and libsmbios2-2.0.2-18.2.x86_64.rpm) which can be downloaded from mirror.switch.ch for example.
install tightvnc again
Restart your vnc service - it works fine fore me.
