Britgirl

[Britgirl]

Hi, please update to the latest 9.1 release, a patch was included which fixes this issue.

https://kb.nomachine.com/TR10U11023

[Britgirl]

Thanks for that. We’ve queued it up for investigation. It’s likely that it is also reproducible on version 9. If we need any more info from you, we’ll come back to you.

[Britgirl]

Update: we checked the open source drivers and can reproduce it. So stick to the proprietary ones as recommended in the article https://kb.nomachine.com/AR02U01190 🙂

[Britgirl]

Hi, on the server side this is possible. There are two keys in the node.cfg file that let you set the specific path.

# Specify path of base directory where the node has to mount disks
# accessible only by the user who connected them. Base directory is
# "$(DESKTOP)" by default. $(HOME) and $(USER) are also accepted values
# and can be concatenated to specify path to a directory, for example
# "$(HOME)/Shares". Target directory must exist on the system.
#
#DiskSharingPrivateBasePath "$(DESKTOP)"
 
#
# Specify path to base directory where the node has to mount user's
# disks which are accessible to users running a session on that server.
# Base directory is "$(PUBLIC)" by default. $(PUBLIC) is /Volumes on Mac
# OS X, /media on Linux, C:\Users\Public on Windows Vista/7/8 and
# %ALLUSERSPROFILE% on XP. $(USER) is an accepted value and can be
# concatenated to specify path to a directory, for example "/tmp/$(USER)".
# Target directory must exist on the system.
#
#DiskSharingPublicBasePath "$(PUBLIC)" 

On the client side it’s not possible to change the path, but we are going to make it possible in one of the next updates.

[Britgirl]

Hi, thanks for coming back. It would have been useful to know if you can reproduce the problem with the test package – because to be honest, we did not include it in the 9.1 release (it was scheduled for the next maintenance) 🙂

Maybe something changed on your system since you first posted the problem, this might be the reason that you can no longer reproduce it?

[Britgirl]

Hi, a possible workaround (it depends on the drivers in use) is to do the following:

in the node.cfg on the server machine (/usr/NX/etc/node.cfg), change the following line

#DisplayServerExtraOptions

to

DisplayServerExtraOptions "-altcolorformat"

then restart the nxserver. (Settings -> Server -> Status, restart). Let us now the outcome.

[Britgirl]

Hi, can you provide us the following information?

– NoMachine version and OS version on the client side
– NoMachine version and OS version on the server side

[Britgirl]

Hi, it is preferable to always use proprietary drivers. Those are what we base our tests on. Thanks for bringing this to our attention, though, we’ll take a look at the open source ones to see if we can reproduce the same behaviour.

[Britgirl]

For everyone here, a fix should be ready soon, so we’ll be preparing a v9 package for you to try which will fix the no sound issue. Let us know if you are interested 🙂

[Britgirl]

Hi wintermute, you are completely right that time has passed. It is still of course in our plans and we have good news! Now that NoMachine Network (in NM9.0) has been released, we’ve been able to step up with development and concentrate efforts on finalizing NoMachine’s integration with Mission Control preferences. Then there is the testing phase. If all that goes well, it’s probable that it will be in one of the near 9.x minor updates.

[Britgirl]

I forgot to mention this TR https://kb.nomachine.com/TR10U11031. The workaround is to disable Wayland.

[Britgirl]

We got the logs, thanks and we are investigating. Could you try, in the meantime, enabling Wayland instead of using x.Org?

[Britgirl]

Hi,

It seems like my Raspberry Pi does not have a functioning graphical desktop environment. When I try startx i I only get a blank black screen with an underscore blinking at the top left corner and I cannot do anything but forcing a reboot by pulling the power.

Is this happening when not connecting with NoMachine? If so, this sounds like a problem with the OS on your RPi, not NoMachine.

Regarding the problem with connecting over NoMachine, if you are seeing the Rpi device in your Machines panel as a pipe icon on your Mac, this means that the NoMachine server is broadcasting correctly on the same LAN.  Logs from the RPi device would be useful to know why you are getting that error. Please see this document for instructions, https://kb.nomachine.com/DT08U00298 (GUI method). Submit them here or send direct to forum[at]nomachine[dot]com.

[Britgirl]

What version do you have installed on both your client and server machines?

There is a bug that we fixed in an earlier v8 release. Please check here: https://kb.nomachine.com/TR10T10648.

[Britgirl]

You’re right. Connecting with SSH would probably work and to do that you need one of the Enterprise products installed, they support SSH connections. If you are using the free version, you could try with an SSH tunnel maybe?
https://kb.nomachine.com/AR10K00728

[Author]

Posts