- This topic has 5 replies, 4 voices, and was last updated 2 months, 3 weeks ago by
.
-
Posts
-
I’m connecting from Ubuntu 22.04 to an Ubuntu server (NX version 8.13.1 on my side, version 7 on the server side) via virtual desktop. The connection works, but the screen is black and displays the actual pixels of the screen when I drag my mouse around. See here: https://drive.google.com/file/d/1KOomaCsIBxz0unNxIONqZ8zI1VPxR_jn/view?usp=sharing
I’m on a Framework 13, AMD Ryzen™ 5 7640U, 32GB RAM, Ubuntu 22.04 X11.
Display driver specs:*-display
description: VGA compatible controller
product: Advanced Micro Devices, Inc. [AMD/ATI]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:c1:00.0
logical name: /dev/fb0
version: cb
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi msix vga_controller bus_master cap_list fb
configuration: depth=32 driver=amdgpu latency=0 resolution=2256,1504
resources: iomemory:800-7ff irq:67 memory:8000000000-800fffffff memory:90000000-901fffff ioport:1000(size=256) memory:90500000-9057ffff
Please update the server side to the latest version 8. If you are not the administrator of that host, please ask them to reach out to us via the support center.
Hi, our server was updated to 8.13, and I’m still running into this issue. Any idea how I should resolve this?
I found a similar instance of this happening, but this person simply switched off NoMachine…
Hi akevinge,
Can you please make the following two tests, to help us to narrow down the issue: first, try to disable the hardware decoding. If it does not help, please try to turn off X11 vector graphics.
Let us know if it helped or not.
I tried both of these:
– Disabled hardware encoding via Server Settings > Performance
-Disabled X11 vector graphics via /usr/NX/etc/node.cfg.
Neither worked. Switching from VP8 to H264 did improve the throughput a little bit though (e.g. more pixels were displayed, whenever it occasionally did).
I also checked /usr/NX/var/log/nxserver.log and am seeing this particular error over and over:
3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3′.
28697 28726 2024-08-26 12:55:15 033.338 ServerPhysicalSession/ServerConnectOnDisplaySocket: Connect on display ‘0’ socket.
28697 28726 2024-08-26 12:55:15 033.344 ServerPhysicalSession/ServerConnectOnDisplaySocket: Connected to socket @’/tmp/.X11-unix/X0′ proto UNIX.
28697 28726 2024-08-26 12:55:15 033.347 ServerPhysicalSession/ServerIsSessionNxVirtual: Service for display ‘0’ not set in systemd.
28697 28726 2024-08-26 12:55:15 033.349 ServerPhysicalSession/ServerIsSessionNxVirtual: Service for display ‘0’ not set in DBus.
28697 28726 2024-08-26 12:55:15 033.351 ServerPhysicalSession/ServerConfirmLocalSessionOnDisplayByProcessList: Check for display ‘0’.
28697 28726 2024-08-26 12:55:15 033.352 ServerPhysicalSession/ServerGetSessionList: Skip session for display 0 not Xsession.
Not entirely sure if this is relevant (what is nxserver.log doing on a client?) or how to fix it.
I also attempted to use the NX protocol instead of SSH to no improvement.
Hi akevinge,
those logs are not relevant indeed.
In virtual desktops software rendering is normally used and it seems like the software renderer provided by the video drivers is broken. Did you install proprietary drivers on the server? Can you try to update or uninstall them? Or, if not installed already, can you try to install them?
Other possible workarounds are:
– enabling VirtualGL for 3D rendering support (https://kb.nomachine.com/AR05P00982)
– using a different desktop environment (https://kb.nomachine.com/AR04K00667)
This topic was marked as solved, you can't post.