Britgirl

[Britgirl]

For custom sessions, the following key is used instead DefaultXSession, also in node.cfg.

[Britgirl]

Hi, yes we did. Apologies for not coming back to you sooner. Feedback from our developers suggests that further investigation might require a debug package. I’ll come back to you if that’s the case.

[Britgirl]

Ok thanks for letting us know. If happens again, submit the logs 🙂

[Britgirl]

This might be related to a known issue for which we have a Trouble Report open, but we’d like to check the logs first if that’s possible. Can you send us the NoMachine logs from the Raspberry device? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Logs from the Mac client as well can be useful as well.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

Then after that can you try disabling Wayland? This is the link to the issue already known.

Black screen when connecting to Raspberry Pi boards
https://www.nomachine.com/TR10U11031

[Britgirl]

When you say you “can’t control it”, what do you mean exactly? You can’t click on anything or something else? Have you tried the other view modes such as resizing the remote display? You can access the from the connection menu (Ctrl-Alt-0 or page peel)

You can read more about these view modes here: https://kb.nomachine.com/DT09T00266#5.4

If you’ve tried changing the view mode and that doesn’t help, please send us the logs from both the Windows and Ubuntu machines. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, send us that screenshot to forum[at]nomachine[dot]com and I’ll attach it. Thanks

[Britgirl]

Let us know because, as I said, and albeit we don’t officially support Manjaro, our tests show that it installs ok and there are no boot problems.

[Britgirl]

Development is in its final stages. We don’t have an official date for the release yet, but we are working hard to make it available by the end of this summer.

[Britgirl]

This looks like a problem with permissions on the macOS side. Please check this article for the steps to perform: https://kb.nomachine.com/AR11Q01061. You should make sure that you see NoMachine in Accessibility, Screen Recording, Full Disk Access. If NoMachine is not among the allowed apps, add it. If it is present, remove and re-add.

[Britgirl]

Are you able to send us client and server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. For the client-side logs (the Windows’ ones will suffice) see “Fourth step” in that document.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

 

[Britgirl]

Zip the file and then drag it.

[Britgirl]

Local drive, both ways, can be shared. See here: https://www.nomachine.com/accessing-files-on-local-or-remote-disk-drives

Is not currently possible to share Network drives within the session. We’re currently investigating whether it’s possible to add support for Network drives for a future version

NoMachine does not support copy/paste from remote to local computer as some other software

NoMachine does support copy/paste. Please provide details of what you are actually trying to copy and paste, OS and versions both sides, NoMachine products installed and steps to reproduce (i.e from what application to what local application). If you are trying to paste non-text content, e.g an image, this is planned.

[Britgirl]

Hi, we got your email that the problem has been resolved. Can you shed some light on how you got audio working again. It could be useful for us to know.

[Britgirl]

I noticed you submitted this topic to the ARM category, so I’m assuming that you need a package for ARM. So first check that you are downloading the right package for the architecture you have. You can check this by running ‘uname -m’ in a terminal on the ARM device.

‘aarch64’ means you have ARMv8 and you should install this package:

https://downloads.nomachine.com/download/?id=118&distro=ARM

You can run this command from a terminal to get it:

wget https://www.nomachine.com/free/arm/v8/deb -O nomachine.deb

‘armv7l’ means that you have ARMv7, and so you should install this:

https://downloads.nomachine.com/download/?id=113&distro=ARM

You can run this from a terminal to get it:

wget https://www.nomachine.com/free/arm/v7/deb -O nomachine.deb

and then:

sudo dpkg -i nomachine.deb to install.

[Britgirl]

You’re reaching the remote machine but for some reason the connection is being closed. When you installed NoMachine on Windows, did you reboot the machine? Is it possible for you to make a quick test whilst on the same LAN as the computer you’re trying to reach?

In any case, logs from both sides (client and server) would be useful. For Windows, run

%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable all

in a cmd console run as administrator.

Reproduce the problem (connect from whichever client it is)

Then gather the logs.

%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collect

The log archive is created in

%PROGRAMDATA%/NoMachine/var/log/archives

On the device you are connecting from, depending on the OS follow the instructions here, btw you didn’t mention the client-side OS):

Fourth Step: Collect Client Side Logs
https://kb.nomachine.com/DT07S00243

[Author]

Posts