Forum Replies Created
November 1, 2022 at 00:01 in reply to: How to access private key on Android client #41145
UGG nevermind, clearing cache and data for the nomachine app fixed the problem. I should have tried that first before posting.
Please consider this resolvedOctober 31, 2022 at 19:49 in reply to: How to access private key on Android client #41144
@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 listedOctober 30, 2022 at 19:41 in reply to: Using Tailscale for connectivity #41070
I use it all the time, it just works, you connect with your Tailscale IP on port 4000April 15, 2021 at 02:15 in reply to: NoMachine on Plasma with Wayland #32914
Thank youApril 7, 2021 at 18:49 in reply to: NoMachine on Plasma with Wayland #32813
Including log files as suggested in another post. I hope someone can help, because at the moment Wayland Plasma sessions do not work.
Attachments:April 6, 2021 at 17:42 in reply to: NoMachine on Plasma with Wayland #32786
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.April 6, 2021 at 15:37 in reply to: NoMachine on Plasma with Wayland #32779
Additional info I should have put in the initial post:
NoMachine 7.4.1January 5, 2021 at 10:17 in reply to: Cannot detect display running #31124
Thank you if I see anything unusual with 7.0.211 I will open a new topic.December 28, 2020 at 18:49 in reply to: NoMachine version 7 available for download #30981
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 thanksDecember 24, 2020 at 10:39 in reply to: NoMachine version 7 available for download #30910
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.December 21, 2020 at 09:29 in reply to: What is the correct way to clear old logs #30788
Thank you this is exactly what I needed!December 16, 2020 at 10:37 in reply to: Cannot detect display running #30752
Interesting observation. Setting GDK_BACKEND=wayland in /etc/environments prevents NoMachine from starting properly.December 9, 2020 at 09:07 in reply to: Cannot detect display running #30692
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:
DM gdm: 3.38.2
DE gnome-shell: 3.38.2
composter mutter: 3.38.2October 26, 2020 at 09:22 in reply to: Cannot detect display running #30045
That’s great to hear! I’ll follow the TROctober 16, 2020 at 09:07 in reply to: Cannot detect display running #29955
thank you for the reply. NoMachine still not con not detect my wayland display. I do not have any wayland extensions it is just the standard install. I also completely removed NoMachine and reinstalled (mainly to make sure I had not done something goofy to the config files that I didn’t remember).
With both the out-of-the-box install and with the DisplayServerExtraOptions set to “-wlmode composter” NoMachine can not detect my display, nor can it create a new wayland display.
Trying to create a new server shows the attached error.
DM gmd 3.38.1
DE gnome-shell 3.38.1
composter mutter 3.38.1
display server wayland 1.18.0