Forum / NoMachine Terminal Server Products / Local mouse on host does not response after Workstation virtual sessions ends
Tagged: workstation server
- This topic has 6 replies, 3 voices, and was last updated 2 years, 10 months ago by Britgirl.
June 4, 2020 at 08:24 #27950
I have installed Workstation trial on my PC, pop!os 20.04 (basically, ubuntu 20.04). The session is X, not wayland.
When I am l logged out on this host, I can connect to a virtual session from my laptop (running ubuntu 20.04) and it is perfect.
However, when I terminate the virtual session and try to use the real physical mouse on the host, it does not respond. The desktop is at the greeter (log in). This happens whether I use logout via my remote session, or simply terminate the remote session by closing the NoMachine client.
I can access virtual terminals and ctrl-alt-del reboots the machine, so the keyboard is still working, but the pop!os greeter (gdm3) is not able to access keyboard or mouse.June 5, 2020 at 07:14 #27982kroyContributor
We weren’t able to reproduce this problem on pop!os. Can you try to connect to physical session (with NoMachine) to that machine when you encounter the issue you are reporting? Does that session work ok? It could be that the desktop environment is actually failing. Are there any .xsession-errors file in the home directory?June 8, 2020 at 10:50 #28014
The NoMachine sessions work fine.
The problem is local.
I have to kill X to get it working again .,. Restarting gdm3 is not sufficient, neither is restarting the NoMachine server.
There is an Ubuntu bug report with the same problem (from 18.04)
I will see if I can find errors in a log file.June 9, 2020 at 08:29 #28047
This is the ubuntu bug report I mentioned:June 9, 2020 at 08:30 #28048
Hi, possibly the ubuntu bug report will add some clarification. I see by the response that you may not understand the issue.
The problem is that physical sessions can not log in after a virtual session via NoMachine has happened because the input devices (mouse and keyboard) do not appear to be available to the X server.
If the NoMachine remote session was a “desktop share” session because the user is already logged in to the server, then there is no problem.
To reproduce the bug you must have a virtual desktop session (that is, the user is not logged on to the server locally, then connect to the Nomachine Workstation server)
Terminate the session, and then attempt to physically log in.
Whatever happens, it requires a kill of X to fix. However, while this problem exists, it only affects a local user, it is possible to have subsequent nomachine virtual server sessions.
I hope this helps you reproduce itJune 9, 2020 at 08:30 #28049
I don’t know where .xsession-errors is, neither can I find the X logs.
I found this in journalctl -e
Jun 09 09:48:31 keynes /usr/lib/gdm3/gdm-x-session: _XSERVTransMakeAllCOTSServerListeners: server already running
Jun 09 09:48:31 keynes /usr/lib/gdm3/gdm-x-session: xorg-server 2:1.20.8-2ubuntu2.1 (For technical support please see http://www.ubuntu.com/support)
Jun 09 09:48:31 keynes /usr/lib/gdm3/gdm-x-session: (II) The server relies on udev to provide the list of input devices.
Jun 09 09:48:31 keynes /usr/lib/gdm3/gdm-x-session: Fatal server error:
Jun 09 09:48:31 keynes /usr/lib/gdm3/gdm-x-session: Unable to run X server
Jun 09 09:48:57 keynes gnome-shell: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :1002.July 15, 2020 at 17:30 #28530BritgirlParticipant
There is a Trouble Report for this issue:
Termination of virtual session causes GDM crash
Please sign up to receive a notification of when a fix has been released.
This topic was marked as solved, you can't post.