Forum Replies Created
-
Posts
-
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, 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…