Forum Replies Created
-
Posts
-
I’ve tried the following:
- With NoMachine disconnected: restarted Display-Manager then restarted nxserver, the gnome apps and python apps could be forwarded to Windows without issues;
- Then connected to desktop through NoMachine: the apps will be opened locally instead of being forwarded;
- With NoMachine connected: restarted Display-Manager, was kicked out to login screen, then forwarding started working again.
- With logged in physically to the desktop: both gnome apps and python apps cannot be forwarded, only opened locally.
This is a shared server so changing desktop environment may not be a good idea for me. I think I will just disable nxserver for the time being. Thank you very much for the help though.
We have some data analysis program written by ourselves. They are using wxpython for the GUI. But even a very simple window example can’t be forwarded either (py file attached).
We also noticed that some GNOME built-in applications, like gedit, also have this issue.
An update: after I shutdown the nxserver, I can resume the forwarding by ‘sudo systemctl restart display-manager’
Thanks for the reply. We tested with a few computers, and found this behavior only happens with NoMachine on RHEL/Rocky 9. Other computers with RHEL 8.3/8.6 work fine with NoMachine.
This behavior is highly related to NoMachine: The python applications forward their GUI through the ssh client without problem with NO NoMachine installed. But the GUI stops being forwarded right after NoMachine is installed and started. After I completely stopped nxserver, the GUI will be forwarded again. I’ll have to completely shutdown the nxserver then reboot the computer to resume the forwarding.
The NoMachine we are using is Workstation version 8.13.1
Edit: typo