Forum Replies Created
-
Posts
-
UGG nevermind, clearing cache and data for the nomachine app fixed the problem. I should have tried that first before posting.
Please consider this resolved
@Tor I have that folder and all my old connections are there, but for some reason when I now start nomachine they are no longer listed
Including log files as suggested in another post. I hope someone can help, because at the moment Wayland Plasma sessions do not work.
One more update, to make sure I didn’t do something stupid when I installed Plasma on my Arch install I installed NoMachine on KDE Neon (in a VM) which is based on Ubuntu and when I try to connect to that server I get the same error that a display can not be found. Nxnode is also disabled.
Additional info I should have put in the initial post:
Distro: Arch
Plasma 5.21.3
kwayland 5.8.0Wayland 1.19.0
NoMachine 7.4.1
Hi @Gega,
thank you for the reply. I believe some of the issues I was having may have been because of a misconfiguration on my end. After some complete removal and reinstall it seems to be working. I will hold off until the next release in a few weeks and post back if I continue to have issues.
Again thanks
Just installed 7.0.211 on Arch gnome and the tray icon no longer comes on at start. I have to start player first manually. This worked with 7.0.209.
Interesting observation. Setting GDK_BACKEND=wayland in /etc/environments prevents NoMachine from starting properly.
Wanted to provide an update to this topic. It seems that NoMachine is again running under with Wayland gnome on Arch. Since there has not been a NoMachine update I’m assuming that it was some form of gnome regression that caused the issue. To verify I did a complete fresh install of NoMachine removing all my old configurations and it worked out of the box. My current configuration is as follows:
NoMachine: 6.12.3
DM gdm: 3.38.2
DE gnome-shell: 3.38.2
composter mutter: 3.38.2