Carin

[Carin]

Hi alatteri,

we don’t recommend particular brands. Webcams are supported via the USB device forwarding functionality. Some issues have been reported which you can read about in the following article: NoMachine USB forwarding limitations.

In the future, webcam support will be provided through a dedicated encoded channel. There is a Feature request here: Improving support for web camera forwarding. If you want you can subscribe to show your interest and to be notified when it will be released.

[Carin]

Hi mantra,

we have brought this feature forward in our roadmap, but we are not talking weeks, unfortunately.

 

[Carin]

Hi webangel,

Did you use only NX protocol? If that is the case, try to use SSH protocol as well.

Can you also try to run the following terminal command: ssh -i <private_kay_path> <user_name>@<remote_host> -vvv and let us know if this ssh command was completed successfully?

Last, can you please send us server-side logs? You can check the following article for guidance: Collect server and client logs manually. The logs can be sent directly to forum[at]nomachine[dot]com making sure to use the topic as the subject of the email.
Thanks!

[Carin]

We have sent you the package. Check your inbox 🙂

 

[Carin]

Hi Maykro,

Please do a full reinstall and try the NoMachine latest release 7.4.1.

[Carin]

For the specific case reported by Coleman, the path is /opt/intel/mediasdk/lib64 and it is set inside the LIBVA_DRIVERS_PATH environment variable that vaapi is searching through.

As for these two other strings mentioned (mediasdk/lib64 and /opt/intel/mediasdk/plugins//plugins.cfg) they are from libmfx.so and usually this should not be needed for this specific problem as it is about redirecting vaapi library that it should use iHD driver and should look for it inside /opt/intel/mediasdk/lib64.

[Carin]

Hi PRosa,

We received the logs. Thank you! We will investigate and provide some feedback soon.

[Carin]

I’ve sent you the debug package. Please check your inbox 🙂

[Carin]

I’ve sent you the program to download with instructions. Check your inbox 🙂

[Carin]

Hi mymachines,

Unfortunately, the logs you submitted didn’t help us. We would like to send you a debug package and extract the logs again (after you’ve reproduced the problem). Would this be ok for you?

[Carin]

Hi Andy,

Since the user’s db is enabled, it is in use.
To check current users inside you can use nxserver --userlist.
To delete you can use nxserver --userdel and to add you can usenxserver --useradd.
When the user’s db is disabled the users are automatically added to it, and this is the reason why it is not empty.
In V7 we are not using file users.db anymore.

[Carin]

Thank you, Coleman! The link was corrected.

[Carin]

We’ve opened a Trouble Report for this issue:https://www.nomachine.com/TR03S10162.
You can sign up to receive notification of a fix when it’s available.
Thanks for reporting.

[Carin]

Hi PRosa,

Can you send us logs from both the client and server-side, please? You can see the following article for guidance: Collect server and client logs manually.

Please send them as an attachment to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!

[Carin]

Hi oscahie,

Can you try to add the following line to node.cf on the server-side: DisplayAgentExtraOptions "-yuvgrab 1"
The node.cfg is located here: /Applications/NoMachine.app/Contents/Frameworks/etc

If the problem persists, a video will be very useful indeed. Thank you!

[Author]

Posts