X2Go Bug report logs - #1249
numlock not working on win7 client and ubuntu 14.04 LTS server and XFCE desktop

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: <n.vanvliet@utwente.nl>

To: <submit@bugs.x2go.org>

Subject: numlock not working on win7 client and ubuntu 14.04 LTS server and XFCE desktop

Date: Mon, 5 Feb 2018 13:59:46 +0000

[Message part 1 (text/plain, inline)]

Package: x2goserver
Version: 4.0.1.22

Numlock key on the Windows clients is not functional.

My coworkers informed me of this.
I am not entirely sure it's a server problem.



1.       My Window versions:

Windows 7 Enterprice service pack 1.



2.       My Windows x2go client version is:

4.1.0.0



3.       Session is set for XFCE



4.       Server OS is Ubuntu 14.04.5 LTS



5.       Servers x2go packages are:

x2goagent/trusty,now 2:3.5.0.33-0~710~ubuntu14.04.1 all [installed,automatic]

x2goserver/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 amd64 [installed]

x2goserver-extensions/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 all [installed,automatic]

x2goserver-xsession/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 all [installed]



6.       There are several xfce4 packages installed on the server.



7.       I made no changes to the configuration on the server.



Please let me know if you need further information.



Regards,

Nico van Vliet

[Message part 2 (text/html, inline)]

Message #10 received at 1249@bugs.x2go.org (full text, mbox, reply):

From: Jens Reyer <jens.reyer@leberrohstoffe.com>

To: 1249@bugs.x2go.org

Subject: fixed: numlock not working with x2goclient

Date: Thu, 16 May 2019 17:15:14 +0200 (CEST)

[Message part 1 (text/plain, inline)]

Hi,

we had the same issue here, using the Windows x2go-client 4.0.5.2 (Qt 4.8.6).

Solved with the current Windows Client from https://code.x2go.org/releases/binary-win32/x2goclient/releases/4.1.2.0-2018.06.22/x2goclient-4.1.2.0-2018.06.22-setup.exe.

Greets

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.