Keep getting message on console regarding LD_PRELOAD failure

[cppgent0]

Product: NoMachine
Version: 8.1.2
Platform: Linux

(PS you might want to make the NoMachine panel that has this info copy-n-paste compatible, instead of me typing it)

On Ubuntu 22.04. This machine has the server on it, but I only use it as the client.

Getting the same warning. So I tried the command as suggested:

sudo /etc/NX/nxserver –eglcapture no
NX> 900 EnableEGLCapture key set to: 0.
NX> 900 Disabled EGL screen capture in ‘/usr/share/applications/org.gnome.Shell.desktop’.
NX> 900 Disabled EGL screen capture in ‘/usr/lib/systemd/user/org.gnome.Shell@wayland.service’.
exit

restarted the terminal and get the same warnings again.

But if I keep the terminal up and open another tab or terminal window, it works fine. As soon as I close all the terminals, then the issue comes back.

I don’t have ld.so.preload:

ls /etc/ld.so.preload
ls: cannot access ‘/etc/ld.so.preload’: No such file or directory

but there are files in /etc/ld.so.conf.d none of which look like they’re related to NoMachine

$ ls  /etc/ld.so.conf.d/*
/etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf
/etc/ld.so.conf.d/i386-linux-gnu.conf
/etc/ld.so.conf.d/libc.conf
/etc/ld.so.conf.d/skype.conf
/etc/ld.so.conf.d/x86_64-linux-gnu.conf
/etc/ld.so.conf.d/zz_i386-biarch-compat.conf

The “unset LD_PRELOAD” works. I can put in the .bashrc to make it permanent.

Well, sort of works.

If you put the unset at the bottom of the .bashrc, I still get a few warnings when I start the first terminal. But if I put it at the top of the .bashrc then I only get one warning.

 

[Britgirl]

(PS you might want to make the NoMachine panel that has this info copy-n-paste compatible, instead of me typing it)

We will. Thanks for the suggestion for improvement.

You mentioned “restarted the terminal and get the same warnings again.” Restart is not enough. You need to reboot. If you disable eglcapture and reboot, then “unset LD_PRELOAD” is not needed.

[cppgent0]

Reboot worked, thanks!

On Ubuntu, not used to rebooting 🙂

(PS the original post didn’t mention the reboot, at least I don’t see a mention of it.)

[Britgirl]

Yes, you are right, this was not made clear earlier. I’m glad everything is working now 🙂

[maxim-nomachine]

ping 192.168.88.1
ERROR: ld.so: object ‘/usr/NX/lib/libnxegl.so’ from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data.
64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=1.63 ms
64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=1.11 ms

I use openSUSE Tumbleweed…

I tried to look at AppArmor and generate logs via:

journalctl -g apparmor > apparmor.log

But latest message was logged 2 days ago.

So either it is not logged or it is not related to AppArmor.

[Britgirl]

maxim-nomachine, can you send us the server-side logs so we can check them? 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!

[tamer]

cd /etc;

rg LD_PRELOAD

——————————

/etc/sudo.conf
49:# support LD_PRELOAD or its equivalent.
63:# support LD_PRELOAD or its equivalent.

/etc/xdg/plasma-workspace/env/nx-sourceenv.sh
1:export LD_PRELOAD=/usr/NX/lib/libnxegl.so

[tamer]

pacman -Qo  /etc/xdg/plasma-workspace/env/nx-sourceenv.sh
————————————————

error: No package owns /etc/xdg/plasma-workspace/env/nx-sourceenv.sh

[Ilgaz]

I noticed a tool which interfaces with “wine” notices that error and thinks the Windows application has failed and cancels the application altogether.

[Britgirl]

Tamer, the file nx-sourceenv.sh is created by NoMachine.

Can you send us the server-side logs so we can check them? 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!

What Linux distribution and version is installed on the server?
What desktop environment and version are you using?
Are you aware of any security policy which is set on that machine?

[fra81]

So far we could only reproduce this problem in our labs when running the ‘ping’ command with KDE Plasma running on X11 (not Wayland), that is when the kwin_x11 window manager is in use. Is everyone here using Plasma on X11?

[maxim-nomachine]

Operating System: openSUSE Tumbleweed 20241222
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: X11

[Ilgaz]

I am only using Wayland for years. Intel 620 GPU here. Precisely it is KDE Wayland session. Happy new year.

[Author]

Posts