boospy

[boospy]

And I have now bought NoMachine Workstation. The issues can certainly be solved.

[boospy]

Many thanks for all the information. The Commando:

env XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop /usr/bin/dbus-launch –sh-syntax –exit-with-session /usr/NX/scripts/vgl/vglrun -d /dev/dri/card0 /usr/bin/startplasma-x11

unfortunately has no effect. I have built a small workaround by placing this file in the Plasma Autostart.

#!/bin/bash
killall plasmashell
LD_PRELOAD=/usr/NX/scripts/vgl/libdlfaker.so:/usr/NX/scripts/vgl/libvglfaker.so
plasmashell

This starts Plasma with full GPU support. All other applications are also started with GPU support. I also tested Steam Remoteplay. It is even really usable for some games such as Hitman3. Tekken 8 is probably a bit too big for the protocol.

Kerberos login works with NX as it should. Unfortunately, the automount of Samba shares via Kerberos only works with a workaround. I edit the file “/etc/pam.d/nx” and change it as follows:

auth       include       su
account    include       su
password   include       su
# session    include       su

session required pam_loginuid.so
session optional pam_env.so
session optional pam_umask.so
session required pam_unix.so
session optional pam_mount.so disable_interactive

Unfortunately, something seems to be missing. Because then there is no sound and “non-QT/Plasma applications” start in a segfault.

I will continue to test whether I can still solve the Kerberos automounts with the pam_mount. In any case, many thanks for the support. The GPU works, so the thread can be closed here.

[boospy]

BTW: 

This is a new feature of VirtualGL.

This is an amazing feature! So I can at least start individual apps directly with GPU. Very high praise to NoMachine! I also tried to start the desktop directly with GPU, but unfortunately it didn’t work. But that would be an idea, wouldn’t it?

env XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop /usr/NX/scripts/vgl/vglrun -d /dev/dri/card0 /usr/bin/dbus-launch –sh-syntax –exit-with-session /usr/bin/startplasma-x11

[boospy]

I’ve done alle the tings. Attached the outputs. I’ve also set the ENV in .profile, .bashrc and /etc/environment.

But the variable is never set with NX virtual Desktop. But it works on PHY screen. I have also tried to set it manually in virtual Desktop:

————————————————-

LD_PRELOAD=/usr/NX/lib/libnxegl.so

source .bashrc

————————————————-

Even when I log in with SSH, the ENV variable is set. I have to admit, this is an exciting topic.

Attachments:

1. 

   virtual_screen.png
   

2. 

   phy_screen.png
   

[boospy]

Hello @Britgirl and thank you for your answer. I’ve executed the command on active NoMachine Session on Kubuntu Desktop:

——–

Authorization required, but no authorization protocol specified

[VGL] ERROR: Could not open display :0.

——–
I find the output strange, I mean… I’m on the desktop and the command says that no display can be opened.

In the logs we can see that the server sets the LD_PRELOAD library. Maybe is not set in your user profile?

The variable is displayed/read out correctly when I log in on the physical screen. Unfortunately not via the virtual Nomachine session. node.cfg is attached.

Attachments:

1. node.cfg_.txt

[boospy]

What I also noticed is that the variable has no value here, but it should according to the instructions.

env | grep LD_PRELOAD

LD_PRELOAD=

 

[boospy]

Thank you for your reply. I have already set up VirtualGL according to these instructions.

What I would like is that applications in the KDE desktop, such as Steam, KDEnlive, video player…, or even the whole desktop uses the Nvidia GPU. That was my plan.

Attached is the log I created according to the instructions and a Screenshot from the NX Client on my local machine.

Attachments:

1. 

   nxclient.png
   

1. NoMachine-log-2024.10.11-22.29.37.zip

[boospy]

I was able to solve it, I don’t know why this is the case with this machine. Apparently something is really bent. In any case, the solution was this:

In addition to the exclude, you must add an “or”. This does not make sense. But since then, NoMachine works again with pam Automount.

File: /etc/security/pam_mount.conf.xml

root sddm nx root sddm nx

[boospy]

Ok, I have debugged. I have found out that it is the pam_automount. When I move the file, I can connect immediately. I also noticed that although I ignore the user NX in the file pam_mount.conf.xml, this option of the file is ignored. This means that no screen is started.

Here are the Log during the login process: (sorry, didn’t find a code block for the post)

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:68): Messages from underlying mount program:

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): mount error(13): Permission denied

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Nov 11 19:12:04 kitten kernel: CIFS: VFS: cifs_mount failed w/return code = -13

Nov 11 19:12:04 kitten nxexec[106020]: (pam_mount.c:522): mount of Programme failed

Nov 11 19:12:04 kitten audit[909]: AVC apparmor=”DENIED” operation=”open” profile=”/usr/sbin/sssd” name=”/proc/106039/cmdline” pid=909 comm=”sssd_nss” requested_mask=”r” denied_mask=”r” fsuid=0 ouid=0

Nov 11 19:12:04 kitten kernel: CIFS: Attempting to mount \\data.tux.lan\iso-images

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:68): Messages from underlying mount program:

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): mount error(13): Permission denied

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Nov 11 19:12:04 kitten kernel: CIFS: VFS: cifs_mount failed w/return code = -13

Nov 11 19:12:04 kitten nxexec[106020]: (pam_mount.c:522): mount of iso-images failed

Here is n line from the “/etc/security/pam_mount.conf.xml”

rootsddmnx

I have also a NoMachine Workstation Version here, and there it works fine. Both are 8.2.3-4. I have the logs when it failed also attached. Maybe someone can read out a useful error message.

Thank you

Best Regards 🙂

Attachments:

1. NoMachine-log-2022.11.11-16.23.07.zip

[boospy]

Virtual Screens (direct login) are only available in the Workstation/Enterprise Editions. If you use the free edition, it is like VNC.

[boospy]

Hell irek, and very thanks for your help. It is working now perfectly 🙂

[boospy]

Found the issue. Don’t know why but it looks likes a bad idea if you change the default ports from nxhtd to 80 and 443 before you start the server once. So the way I see it, the user is configured at the first start of the webserver. The only way for me to fix was to remove nomachine completly with all files, and install it again. After that i started the webserver once. With this user was created, rights were set. So every thing fine. 

But same thing, server didn’ start after i change the ports to 80/443. For that i created an extra topic. Maybe you can help me with this: https://forums.nomachine.com/topic/nxhtd-webserver-did-not-start-anymore-after-changing-the-ports

Very thanks and best Regards

[boospy]

Hello Kroy, very thanks for your answer. This command works,  but unfortunately the same as the original command. What I came up with is that you can then set up the standard Lubuntu Desktop LXQT in the logged-in state per user. This is now a workaround.

But apparently there has to be another command / option that is used by SDDM. Strange.

[Author]

Posts