Hi,
thanks a lot! We have now run the turbovnc client on 6 different PCs
running Windows7 and various versions of Ubuntu in English and in
German. Out of those we found 2 (running the English version of Win7)
that worked without problems (i.e. that transmit all characters
correctly). Since we also have one that is essentially set up in the
same way but produces the problem we shall try to find the difference
between them. I shall come back to the list as soon as we know more!
------------------------------------------------------------------------
Dieter Blaas,
Max F. Perutz Laboratories
Medical University of Vienna,
Inst. Med. Biochem., Vienna Biocenter (VBC),
Dr. Bohr Gasse 9/3,
A-1030 Vienna, Austria,
Tel: 0043 1 4277 61630,
Fax: 0043 1 4277 9616,
e-mail: [email protected]
------------------------------------------------------------------------
Am 09.10.2014 21:02, schrieb DRC:
> I haven't been able to reproduce any issues thus far, either using the
> 1.2.2 server or the 2.0 server with a German key layout on the client.
> One important thing to note is that the keyboard layout needs to be set
> properly in the client-side O/S for it to properly transmit the German
> key symbols to the server. I don't think it matters what the layout is
> set to on the server-- at least it didn't seem to matter in my testing.
>
> I tried several different O/S's (Windows, Linux, OS X) on the client
> side, all configured to use a German layout, and both Windows and Java
> viewers passed through the keystrokes you list below to the TurboVNC
> Server with no problems.
>
> It may be that this is an issue with AltGr handling, but the fact that
> you are having the same issues with TigerVNC tells me that this probably
> isn't an issue with our code. TigerVNC is a lot more on top of
> internationalization issues than we are (given that it is primarily
> developed in Sweden), so if it's failing with both Turbo and Tiger, that
> makes it less likely that it is actually a bug.
>
> Another possibility is that this issue isn't reproducible without an
> actual German keyboard, but I don't know why the handling of a German
> keyboard should be all that different from an Italian keyboard or other
> European keyboards that I have added support for in the past (one of my
> customers uses Italian keyboards, so I had to sort out the AltGr stuff a
> while ago.)
>
> Anyway, please double check that the client-side O/S is configured for a
> German key layout. I'm not sure what else to suggest. If anyone else
> reading this has any information on using TurboVNC with European
> keyboards and can confirm/deny that there are still issues with that,
> please reply.
>
>
> On 9/24/14, 3:09 AM, Dieter Blaas wrote:
>> Sorry for the confusion:
>> On the Centos Box I installed turbovnc-1.2.80.x86_64.rpm and I am
>> running its server.
>> I connect from with the following viewers:
>>
>> 1) Windows7 (English Version - but German Keyboard) with the java
>> version of turbovnc-1.2.1
>> the following characters do not work ° (degree), ´ (forward tick), €
>> (Euro), ö, Ö, ä, Ä, ü, Ü (when pressed they all show a question mark). ^
>> (caret) and ` (back tick) work but they need two consecutive key presses
>>
>> 2) PC running Ubuntu 10.04 (English Version - but German Keyboard) with
>> he java version of turbovnc-1.2.80
>> the following characters do not work: ° (degree), ´ (forward tick), ö,
>> Ö, ä, Ä, ü, Ü, (when pressed they all show a question mark). ^ (caret)
>> works without a second key stroke, ` (back tick) gives a question mark,
>> ´ (forward tick) gives a question mark but when pressed again a ~
>> (tilde). ' (quote) gives " (double quote) but after several presses it
>> gives a single quote. € (Euro sign) gives 'EUR' (which is OK).
>>
>> 3) 2 Laptops running Ubuntu 14.04 (German Version - German Keyboard)
>> with the java version of turbovnc_1.2.1
>> most of the characters given above neither work (in particular äÄöÖüÜ
>> and the back tick, which important for scripting). I can make a detailed
>> list if you need it but I do not have them at hand right now.
>>
>> Apparently it greatly depends on the configuration of the PC from which
>> I connect to the server. However, everything seems to work with ssh -Y
>>
>> Thanks again for your help,
>> Dieter
>>
>> ------------------------------------------------------------------------
>> Dieter Blaas,
>> Max F. Perutz Laboratories
>> Medical University of Vienna,
>> Inst. Med. Biochem., Vienna Biocenter (VBC),
>> Dr. Bohr Gasse 9/3,
>> A-1030 Vienna, Austria,
>> Tel: 0043 1 4277 61630,
>> Fax: 0043 1 4277 9616,
>> e-mail: [email protected]
>> ------------------------------------------------------------------------
>>
>> Am 24.09.2014 08:07, schrieb DRC:
>>> Those server errors are unfortunately normal for any VNC server. But
>>> your post is unclear. Do you mean that the new server fixed the
>>> keyboard issue, or is it still an issue? And I don't understand your
>>> comment about VncViewer.jar. Please post specifics such as:
>>>
>>> Version XX of the server with Version YY of the client works
>>> Version ZZ of the server with Version QQ of the client does not work
>>> etc.
>>>
>>> Thanks.
>>>
>>>
>>> On 9/24/14 1:02 AM, Dieter Blaas wrote:
>>>> OK, sorry :-))
>>>> I now installed the pre-release version on the Centos Box. I am
>>>> connecting from a German version of Ubuntu 14.04 with a German keyboard!
>>>> Since I had the issues detailed previously I now went back to the
>>>> previous version of VncViewer.jar. It does not transmit ö,ä,ü, caret,
>>>> backtick, backslash, ~.
>>>>
>>>> *and there is a lot of error messages in the log file on the Centos Box:*
>>>>
>>>> TurboVNC Server (Xvnc) 64-bit v1.2.80 (build 20140805)
>>>> Copyright (C) 1999-2014 The VirtualGL Project and many others (see
>>>> README.txt)
>>>> Visit http://www.TurboVNC.org for more information on TurboVNC
>>>>
>>>> 24/09/2014 07:40:37 Using auth configuration file
>>>> /etc/turbovncserver-auth.conf
>>>> 24/09/2014 07:40:37 Enabled authentication method 'vnc'
>>>> 24/09/2014 07:40:37 Enabled authentication method 'otp'
>>>> 24/09/2014 07:40:37 Enabled authentication method 'pam-userpwd'
>>>> 24/09/2014 07:40:37 Desktop name 'TurboVNC: blaaslinpc:1 (blaasd3)'
>>>> (blaaslinpc:1)
>>>> 24/09/2014 07:40:37 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
>>>> 24/09/2014 07:40:37 Listening for VNC connections on TCP port 5901
>>>> 24/09/2014 07:40:37 Interface 0.0.0.0
>>>> 24/09/2014 07:40:37 Listening for HTTP connections on TCP port 5801
>>>> 24/09/2014 07:40:37 URL http://blaaslinpc:5801
>>>> 24/09/2014 07:40:37 Interface 0.0.0.0
>>>> 24/09/2014 07:40:37 Framebuffer: BGRX 8/8/8/8
>>>> 24/09/2014 07:40:37 VNC extension running!
>>>> gnome-session[21061]: devkit-power-gobject-WARNING: Couldn't enumerate
>>>> devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>> gnome-session[21061]: WARNING: Could not connect to ConsoleKit: Could
>>>> not get owner of name 'org.freedesktop.ConsoleKit': no such name
>>>> gnome-session[21061]: WARNING: Could not connect to ConsoleKit: Could
>>>> not get owner of name 'org.freedesktop.ConsoleKit': no such name
>>>> GNOME_KEYRING_SOCKET=/tmp/keyring-VztPds/socket
>>>> SSH_AUTH_SOCK=/tmp/keyring-VztPds/socket.ssh
>>>> GNOME_KEYRING_PID=21097
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (nm-applet:21146): WARNING **: <WARN> request_name(): Could not
>>>> acquire the NetworkManagerUserSettings service.
>>>> Error: (9) Connection ":1.41897" is not allowed to own the service
>>>> "org.freedesktop.NetworkManagerUserSettings" due to security policies in
>>>> the configuration file
>>>>
>>>>
>>>> (polkit-gnome-authentication-agent-1:21149): polkit-gnome-1-WARNING **:
>>>> Unable to determine the session we are in: Remote Exception invoking
>>>> org.freedesktop.ConsoleKit.Manager.GetSessionForUnixProcess() on
>>>> /org/freedesktop/ConsoleKit/Manager at name org.freedesktop.ConsoleKit:
>>>> org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gdu-notification-daemon:21150): libgdu-WARNING **: Couldn't get daemon
>>>> properties
>>>> ======================================================================
>>>> Error constructing GduPool: (unspecified error)
>>>>
>>>> This error suggests there's a problem with your udisks or D-Bus
>>>> installation.
>>>> ======================================================================
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-WARNING **: invalid (NULL)
>>>> pointer instance
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-CRITICAL **:
>>>> g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-WARNING **: invalid (NULL)
>>>> pointer instance
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-CRITICAL **:
>>>> g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-WARNING **: invalid (NULL)
>>>> pointer instance
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-CRITICAL **:
>>>> g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-WARNING **: invalid (NULL)
>>>> pointer instance
>>>>
>>>> (gdu-notification-daemon:21150): GLib-GObject-CRITICAL **:
>>>> g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
>>>>
>>>> (gnome-panel:21134): GVFS-RemoteVolumeMonitor-WARNING **: invoking
>>>> IsSupported() failed for remote volume monitor with dbus name
>>>> org.gtk.Private.GduVolumeMonitor:
>>>> org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
>>>> /usr/libexec/gvfs-gdu-volume-monitor received signal 6
>>>> **
>>>> libgdu:ERROR:gdu-pool.c:2459:gdu_pool_get_devices: assertion failed:
>>>> (pool != NULL)
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Couldn't
>>>> enumerate devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>> Initializing nautilus-gdu extension
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Couldn't
>>>> enumerate devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Couldn't
>>>> enumerate devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (nautilus:21142): GVFS-RemoteVolumeMonitor-WARNING **: invoking
>>>> IsSupported() failed for remote volume monitor with dbus name
>>>> org.gtk.Private.GduVolumeMonitor:
>>>> org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
>>>> /usr/libexec/gvfs-gdu-volume-monitor received signal 6
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Couldn't
>>>> enumerate devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> ** (gnome-panel:21134): WARNING **: panel-applet-frame.c:1288: failed to
>>>> load applet OAFIID:GnoteApplet:
>>>> (null)
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Couldn't
>>>> enumerate devices: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>> gnome-session[21061]: devkit-power-gobject-WARNING: Error invoking
>>>> GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>> gnome-session[21061]: devkit-power-gobject-WARNING: Error invoking
>>>> GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>> gnome-session[21061]: WARNING: Could not connect to ConsoleKit: Could
>>>> not get owner of name 'org.freedesktop.ConsoleKit': no such name
>>>> gnome-session[21061]: WARNING: Could not connect to ConsoleKit: Could
>>>> not get owner of name 'org.freedesktop.ConsoleKit': no such name
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> (gnome-power-manager:21153): devkit-power-gobject-WARNING **: Error
>>>> invoking GetAll() to get properties: Failed to execute program
>>>> /lib64/dbus-1/dbus-daemon-launch-helper: Success
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-settings-daemon:21096): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>> ** (gnome-volume-control-applet:21154): WARNING **: Connection failed,
>>>> reconnecting...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>> Dieter Blaas,
>>>> Max F. Perutz Laboratories
>>>> Medical University of Vienna,
>>>> Inst. Med. Biochem., Vienna Biocenter (VBC),
>>>> Dr. Bohr Gasse 9/3,
>>>> A-1030 Vienna, Austria,
>>>> Tel: 0043 1 4277 61630,
>>>> Fax: 0043 1 4277 9616,
>>>> e-mail:[email protected]
>>>> ------------------------------------------------------------------------
>>>>
>>>> Am 24.09.2014 03:41, schrieb DRC:
>>>>> What is wrong is that you are trying to test too many things at once.
>>>>> Ubuntu 14.04 is not yet supported (I'm working on it.) Please try the
>>>>> pre-release on your CentOS machine, and let's address the key mapping
>>>>> issue first before addressing any other issues.
>>>>>
>>>>>
>>>>> On 9/23/14 8:27 PM, Dieter Blaas wrote:
>>>>>> Hi,
>>>>>> I originally posted these questions and the previous ones to
>>>>>> VirtualGL-Users but was asked to move to this list:
>>>>>>
>>>>>> I am using TurboVNC (in Ubuntu 14.04 and in WIn7) to connect to
>>>>>> VirtualGL running on a Centos6.5 machine. Everything is fine except from
>>>>>> the lack of transmission of special characters like backtick, acute, and
>>>>>> caret (but @ and | do work!). When connecting to the same machine via
>>>>>> ssh all characters are displayed correctly. DRC had suggested to install
>>>>>> the pre-release of TurboVNC to fix this.
>>>>>>
>>>>>> Before installing it on the server running Centos I have now installed
>>>>>> turbovnc_1.2.80_amd64.deb and turbovnc_1.2.80_i386.deb on two laptops
>>>>>> running ubuntu-14.04 64 and 32 bits, respectively. Regardless from where
>>>>>> I connect I get a black screen and the message (in a box "TurboVNC
>>>>>> Viewer") saying 'connection closed'
>>>>>>
>>>>>> I find this in ./vnc/ubuntu:1.log:
>>>>>> > .............................
>>>>>> > 23/09/2014 21:37:48 Using protocol version 3.8
>>>>>> > 23/09/2014 21:37:48 Enabling TightVNC protocol extensions
>>>>>> > 23/09/2014 21:37:53 Full-control authentication enabled for
>>>>>> 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Pixel format for client 192.168.1.9:
>>>>>> > 23/09/2014 21:37:53 32 bpp, depth 24, little endian
>>>>>> > 23/09/2014 21:37:53 true colour: max r 255 g 255 b 255, shift
>>>>>> r 16
>>>>>> g 8 b 0
>>>>>> > 23/09/2014 21:37:53 no translation needed
>>>>>> > 23/09/2014 21:37:53 Enabling Desktop Size protocol extension for
>>>>>> client
>>>>>> > 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Enabling Extended Desktop Size protocol
>>>>>> extension
>>>>>> for client
>>>>>> > 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 rfbProcessClientNormalMessage: ignoring
>>>>>> unknown
>>>>>> encoding -307 (fffffecd)
>>>>>> > 23/09/2014 21:37:53 Enabling LastRect protocol extension for
>>>>>> client
>>>>>> 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Enabling Continuous Updates protocol
>>>>>> extension
>>>>>> for client 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Enabling Fence protocol extension for client
>>>>>> 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Using tight encoding for client 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Using JPEG subsampling 2, Q42 for client
>>>>>> 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Using JPEG quality 30 for client 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Using JPEG subsampling 1 for client
>>>>>> 192.168.1.9
>>>>>> > 23/09/2014 21:37:53 Using Tight compression level 1 for client
>>>>>> 192.168.1.9
>>>>>> > Segmentation fault at address (nil)
>>>>>> >
>>>>>> > Fatal server error:
>>>>>> > Caught signal 11 (Segmentation fault). Server aborting
>>>>>> > XIO: fatal IO error 11 (Resource temporarily unavailable) on X
>>>>>> server ":1"
>>>>>> > after 14 requests (14 known processed) with 0 events
>>>>>> remaining.
>>>>>>
>>>>>> What is wrong?
>>>>>> Thanks, D.
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> TurboVNC-Users mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> TurboVNC-Users mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> TurboVNC-Users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>>>>
>>> ------------------------------------------------------------------------------
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> TurboVNC-Users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> TurboVNC-Users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> TurboVNC-Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
TurboVNC-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/turbovnc-users
