Forum Replies Created
-
AuthorPosts
-
fra81
ModeratorHi,
can you please run these 3 commands in a terminal on the server and show us the output?
1
echo $LD_PRELOAD
2
ls -l /etc/xdg/plasma-workspace/env
3
sudo getcap /usr/bin/kwin_wayland
fra81
ModeratorHi,
thanks for the logs. Can you please run these 3 commands in a terminal on the server and show us the output?
1
echo $LD_PRELOAD
2
ls -l /etc/xdg/plasma-workspace/env
3
sudo getcap /usr/bin/kwin_wayland
fra81
ModeratorIt runs damn slow! Seems like there was no use of the graphics hardware at all.
As I see in the glxinfo output, it looks like the graphics hardware is being used. Is maybe the server headless? Or is the monitor turned off? In some cases graphics drivers slow down GPU rendering considerably in case no monitor is detected.
When I run the application prepended by vglrun in addition, it gives some more output.
ERROR: ld.so: object ‘/opt/NX/scripts/vgl//opt/NX/scripts/vgl/’ from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
This error is due to the problem described in https://kb.nomachine.com/TR12T10706 and is unrelated. As stated in the Trouble Report, it occurs if you enable VirtualGL globally and you use vglrun at the same time. These 2 methods should be used alternatively.
fra81
ModeratorSorry for the delay. We didn’t reproduce this behavior with KDE Plasma or any different environment. It has to be something specific in your system.
How can I recognize a virtual desktop session in the shell? Perhaps, if this was possible we could define LD_PRELOAD accordingly in the system wide login files?
You may try to look for the variables set by NoMachine in the env, e.g. NX_CONNECTION.
fra81
ModeratorHi,
sorry for the delay. We have finally reproduced this issue in our labs. Can you confirm that it only occurs when using KDE with Wayland? To check that, you can use X11 option instead of Wayland in the login screen of the problematic VM.
fra81
ModeratorManually setting the LD_PRELOAD variable to “/opt/NX/lib/libnxegl.so” does not ‘fix’ the virtual session.
Note that LD_PRELOAD is set to a different value in the physical desktop and for a different purpose. In virtual desktops, the value you are supposed to see is:
LD_PRELOAD=/opt/NX/scripts/vgl/libdlfaker.so:/opt/NX/scripts/vgl/libvglfaker.so
You can try to set it manually and check again.
The question is still why LD_PRELOAD is not set, even if in the logs we see that it’s being added to the environment of the desktop process. At the moment I don’t have further ideas, we will check again in our labs with KDE Plasma.
March 3, 2025 at 16:32 in reply to: NoMachine displays grey window when connecting Mac to Linux #52034fra81
ModeratorHi Rhymer,
do you mean that the monitor attached to the server is turned on and you can see what is actually happening on the server screen, while the grey screen is being shown in the player window?
To investigate further, we would need to see the logs from the server. Please follow the instructions in https://kb.nomachine.com/DT07S00243. You can send them to forum[at]nomachine[dot]com.
fra81
ModeratorHi,
it would be important to see logs from the user’s home ($HOME/.nx), that are missing in the archive. You can try with the automatic procedure (see https://kb.nomachine.com/DT07S00243). You can send them to forum[at]nomachine[dot]com by referencing this topic.
fra81
ModeratorHi.
It’s strange that the LD_PRELOAD variable is not set in the environment, despite we see it being set in the logs. It seems like something else is clearing the environment afterwards, maybe something in the user’s profile.
However, you may check if VirtualGL is functional by trying to run your app through the vglrun command:
/opt/NX/scripts/vgl/vglrun <opengl app>
(assuming NoMachine is installed in ‘opt’ dir, as we see in the logs)
The, you may try to run the whole desktop via the vglrun command by adding it to the DefaultDesktopCommand key in the node.cfg file, e.g.:
DefaultDesktopCommand "/usr/bin/dbus-launch --exit-with-session /opt/NX/scripts/vgl/vglrun gnome-session"
fra81
ModeratorHello,
I assume you have already tried to disable hardware encoding. Have you also tried to disable hardware decoding in the session menu on the client?
In order to narrow things down, can you try to add this line in the /usr/NX/etc/node.cfg file on the server:
DisplayServerExtraOptions "-refinement 0"
Finally, please send both server and client side logs for further investigation. See https://kb.nomachine.com/DT07S00243 for instructions. You can send them to forum[at]nomachine[dot]com.
fra81
ModeratorHi mickeyil,
you mention X11 vector graphics, so do you confirm you have got one of the products in the NoMachine Terminal Server family and you are running a virtual desktop?
In that case, you may want to use a lossless compression method (like png) for image encoding. See more about the ProxyExtraOptions key:
fra81
ModeratorHi forux,
logs show something strange, like if the monitors info initialization was incomplete. Could you show us the output of the following dbus call?
You should install the d-feet package (‘sudo apt install d-feet’), open the d-feet program, navigate to the Session Bus section, double-click on the GetCurrentState method of the /org/gnome/Mutter/DisplayConfig interface (see the attached screenshot), and click on Execute. What is the output?
Please also send the logs in this directory: $HOME/.nx/nxegl/.
-
This reply was modified 4 months, 3 weeks ago by
fra81.
Attachments:
December 24, 2024 at 12:02 in reply to: Keep getting message on console regarding LD_PRELOAD failure #51198fra81
ModeratorSo 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?
fra81
ModeratorHi,
you’re right, macOS works as if the NumLock key was always ON, so the initial state of the NumLock key in the NoMachine session should be ON instead of OFF. This will be changed in a future release. Is this an acceptable solution for you?
I would like NoMachine to just leave the NumLock status as it is
This alternative solution would require deeper design changes and needs further evaluation.
fra81
ModeratorHi,
can you tell us about:
– Fedora version
– Plasma version
– Graphics card and drivers -
This reply was modified 4 months, 3 weeks ago by
-
AuthorPosts