Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer.
Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer. <snip> We saw this again today for the same user. Has anyone else experienced
On Wed, 2010-08-25 at 16:38 -0400, John A. Sullivan III wrote: this? Thanks - John
On Fri, 2010-08-27 at 13:35 -0400, John A. Sullivan III wrote:
Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer. <snip> We saw this again today for the same user. Has anyone else experienced
On Wed, 2010-08-25 at 16:38 -0400, John A. Sullivan III wrote: this? Thanks - John <snip> We now have another user who experienced this twice today. I'm willing to put in the time to troubleshoot this but I'm not sure where to begin. Any ideas? Thanks - John
On Fri, 2010-08-27 at 13:35 -0400, John A. Sullivan III wrote:
Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer. <snip> We saw this again today for the same user. Has anyone else experienced
On Wed, 2010-08-25 at 16:38 -0400, John A. Sullivan III wrote: this? Thanks - John <snip> We now have another user who experienced this twice today. I'm willing to put in the time to troubleshoot this but I'm not sure where to begin. Any ideas? Thanks - John <snip> This is now happening many times a day and is causing quite an upset. I scoured the Internet for ideas and there seems to be lots of reports about this on Debian and Ubuntu but no clear identification of the
On Mon, 2010-08-30 at 21:52 -0400, John A. Sullivan III wrote: problem or clear fixes.
I posted to the Debian mailing list assuming it is a Debian problem. They recommended editing xorg.conf to add Option "SWCursor" "yes" to the video driver. That didn't help. Using Ctl-Alt-D as someone else suggested to recover the mouse did not help. I'm not sure if NX and X2Go are complicating the issue. Has anyone else seen this? Has anyone solved it? It is making the system approach unusable. Thanks - John
hello,
i install x2go server on xen machine
pxe come to login but after login he cannot start
it says that he cannot connect localhost when i go to console client i cannot ping localhost lo is there but not up
i suppose the link in run by client is not done
i correct like this and it works, but i suppose it is a mistake or not?
x2gonoldapone:~/scripts-noldap-0ne# cd /opt/x2gothinclient/etc/network/ x2gonoldapone:/opt/x2gothinclient/etc/network# ls if-down.d if-post-down.d if-pre-up.d if-up.d interfaces run x2gonoldapone:/opt/x2gothinclient/etc/network# ls run x2gonoldapone:/opt/x2gothinclient/etc/network# ls -l total 24 drwxr-xr-x 2 root root 4096 May 5 2008 if-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-post-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-pre-up.d drwxr-xr-x 2 root root 4096 Sep 11 08:33 if-up.d -rw-r--r-- 1 root root 30 Sep 11 08:21 interfaces drwxr-xr-x 2 root root 4096 Sep 11 08:21 run x2gonoldapone:/opt/x2gothinclient/etc/network# rm -r run x2gonoldapone:/opt/x2gothinclient/etc/network# ln -s /dev/shm run x2gonoldapone:/opt/x2gothinclient/etc/network# ls -l total 20 drwxr-xr-x 2 root root 4096 May 5 2008 if-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-post-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-pre-up.d drwxr-xr-x 2 root root 4096 Sep 11 08:33 if-up.d -rw-r--r-- 1 root root 30 Sep 11 08:21 interfaces lrwxrwxrwx 1 root root 8 Sep 11 08:54 run -> /dev/shm x2gonoldapone:/opt/x2gothinclient/etc/network#
michel
Are you trying to connect to localhost from the same virtual machine? If yes, then you must to connect to x2go server from outside virtual machine (f.e. from the host you when you are running the xen server).
Regards, Ricardo Díaz
2010/9/11 kamerun@immerda.ch <kamerun@immerda.ch>
hello,
i install x2go server on xen machine
pxe come to login but after login he cannot start
it says that he cannot connect localhost when i go to console client i cannot ping localhost lo is there but not up
i suppose the link in run by client is not done
i correct like this and it works, but i suppose it is a mistake or not?
x2gonoldapone:~/scripts-noldap-0ne# cd /opt/x2gothinclient/etc/network/ x2gonoldapone:/opt/x2gothinclient/etc/network# ls if-down.d if-post-down.d if-pre-up.d if-up.d interfaces run x2gonoldapone:/opt/x2gothinclient/etc/network# ls run x2gonoldapone:/opt/x2gothinclient/etc/network# ls -l total 24 drwxr-xr-x 2 root root 4096 May 5 2008 if-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-post-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-pre-up.d drwxr-xr-x 2 root root 4096 Sep 11 08:33 if-up.d -rw-r--r-- 1 root root 30 Sep 11 08:21 interfaces drwxr-xr-x 2 root root 4096 Sep 11 08:21 run x2gonoldapone:/opt/x2gothinclient/etc/network# rm -r run x2gonoldapone:/opt/x2gothinclient/etc/network# ln -s /dev/shm run x2gonoldapone:/opt/x2gothinclient/etc/network# ls -l total 20 drwxr-xr-x 2 root root 4096 May 5 2008 if-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-post-down.d drwxr-xr-x 2 root root 4096 May 5 2008 if-pre-up.d drwxr-xr-x 2 root root 4096 Sep 11 08:33 if-up.d -rw-r--r-- 1 root root 30 Sep 11 08:21 interfaces lrwxrwxrwx 1 root root 8 Sep 11 08:54 run -> /dev/shm x2gonoldapone:/opt/x2gothinclient/etc/network#
michel
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
John A. Sullivan III schreef:
On Fri, 2010-08-27 at 13:35 -0400, John A. Sullivan III wrote:
Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer. <snip> We saw this again today for the same user. Has anyone else experienced
On Wed, 2010-08-25 at 16:38 -0400, John A. Sullivan III wrote: this? Thanks - John <snip> We now have another user who experienced this twice today. I'm willing to put in the time to troubleshoot this but I'm not sure where to begin. Any ideas? Thanks - John <snip> This is now happening many times a day and is causing quite an upset. I scoured the Internet for ideas and there seems to be lots of reports about this on Debian and Ubuntu but no clear identification of the
On Mon, 2010-08-30 at 21:52 -0400, John A. Sullivan III wrote: problem or clear fixes.
I posted to the Debian mailing list assuming it is a Debian problem. They recommended editing xorg.conf to add Option "SWCursor" "yes" to the video driver. That didn't help. Using Ctl-Alt-D as someone else suggested to recover the mouse did not help. I'm not sure if NX and X2Go are complicating the issue. Has anyone else seen this? Has anyone solved it? It is making the system approach unusable. Thanks - John
I don't know the problem, but did you search the knowledgebase of Nomachine? http://www.nomachine.com/kb/ There is much in it about mouses and cursors.
With regards, Paul van der Vlis.
On Mon, 2010-09-13 at 14:07 +0200, Paul van der Vlis wrote:
John A. Sullivan III schreef:
On Fri, 2010-08-27 at 13:35 -0400, John A. Sullivan III wrote:
Hello, all. We've seen this bug rarely but enough to know that it is a real bug and not just a coincidence. Here is the report from our internal trouble ticket. Unfortunately, it smells like it might be something in the NX libraries:
The user called because she could not see her mouse cursor in her virtual desktop. It was visible in her physical desktop. As we later observed, it was indeed present in the virtual desktop, e.g., if she happened to stop the mouse over a file in Konqueror, it would display the thumbnail, but the mouse cursor was not visible.
We tried suspending and reconnecting; that did not work. I could see where the mouse was supposed to be via my VNC session to her physical desktop so I tried to change the mouse cursor theme but that did not work (and required a restart of KDE).
Finally, before rebooting to try to re-establish the connection between her physical and virtual desktops to display the mouse cursor, we thought to suspend her X2Go session and then completely close her X2Go client. When she restarted the client and reconnected to her X2Go session, the mouse had re-appeared. We did not need to reboot the physical computer. <snip> We saw this again today for the same user. Has anyone else experienced
On Wed, 2010-08-25 at 16:38 -0400, John A. Sullivan III wrote: this? Thanks - John <snip> We now have another user who experienced this twice today. I'm willing to put in the time to troubleshoot this but I'm not sure where to begin. Any ideas? Thanks - John <snip> This is now happening many times a day and is causing quite an upset. I scoured the Internet for ideas and there seems to be lots of reports about this on Debian and Ubuntu but no clear identification of the
On Mon, 2010-08-30 at 21:52 -0400, John A. Sullivan III wrote: problem or clear fixes.
I posted to the Debian mailing list assuming it is a Debian problem. They recommended editing xorg.conf to add Option "SWCursor" "yes" to the video driver. That didn't help. Using Ctl-Alt-D as someone else suggested to recover the mouse did not help. I'm not sure if NX and X2Go are complicating the issue. Has anyone else seen this? Has anyone solved it? It is making the system approach unusable. Thanks - John
I don't know the problem, but did you search the knowledgebase of Nomachine? http://www.nomachine.com/kb/ There is much in it about mouses and cursors.
With regards, Paul van der Vlis.
Thanks, Paul. I gave the NoMachine knowledge base a perusal tonight and did not turn up anything. This is still a major problem for us with users reporting losing their mouse cursor sometimes four times a day :(
Has anyone else seen this problem? Thanks - John
-
John A. Sullivan III -
kamerun＠immerda.ch -
Paul van der Vlis -
Ricardo Díaz Martín