Forum Replies Created
-
Posts
-
Please try to disable hardware ‘acceleration for display processing’ (on the server):
We’ve reproduced this issue in our labs, thank you for reporting. While we are working on a solution, you can work around it by disabling hardware acceleration for display processing: https://www.nomachine.com/AR02L00782.
Thanks for sending the logs. Unfortunately they are not enough to determine what is the problem, since debug logs are disabled. Please follow the instructions of this paragraph: https://www.nomachine.com/DT07M00098#1.
Hi,
.xsession-errors shows the problem:
openConnection: connect: No such file or directory
cannot connect to brltty at :0
upstart: Failed to spawn upstart-udev-bridge main process: unable to execute: No such file or directory
upstart: unity-gtk-module main process (1889) terminated with status 127
upstart: dbus pre-start process (1891) terminated with status 127This issue is known:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1537610
You could try the workaround reported here:
https://askubuntu.com/questions/763735/ubuntu-16-04-blank-screen-at-bootup/871156#871156
I assume the logs you sent are from your attempts with VirtualGL (and not from previous attempts with adjusting LD_LIBRARY_PATH). So it looks like VirtualGL couldn’t access the display:
Invalid MIT-MAGIC-COOKIE-1 key[VGL] ERROR: Could not open display :0.
Maybe you didn’t run the command shown in the article?
/usr/NX/scripts/vgl/vglserver_config -config +s +t +f
Hi Tom,
please send a complete set of logs (client and server side) as explained here: https://www.nomachine.com/DT07M00098.
Also the ‘.xsession-errors’ file in the user’s home directory on the server could be useful.
You can send everything to forum[at]nomachine[dot]com.
Hi,
can you send the new logs?
Besides trying open source drivers, you can try to enable VirtualGL:
Hi!
I’ve never heard of a similar issue. Please collect the logs as explained here: https://www.nomachine.com/DT07M00098. You can send them to forum[at]nomachine[dot]com.
Yeah, that is strange. Please gather NoMachine server side logs as explained in https://www.nomachine.com/DT07M00098. You can attach them here or send to forum[at]nomachine[dot]com.
So it can happen, depending on the video card, that the X server is running but it is not rendering, because the video card is turned off.
You can try to stop the X server:
sudo service lightdm stop
and restart the NoMachine server:
sudo /usr/NX/bin/nxserver –restart
At this point NoMachine will create its own virtual framebuffer and you should be able to connect and see the desktop.
Hi,
it looks like the same problem reported here:
https://bugs.kde.org/show_bug.cgi?id=377335
I suspect the problem is related to libGL.so provided by nVidia. As a workaround, you can try to set the LD_LIBRARY_PATH in order to use the Mesa version of libGL. To do so, you have to modify the DefaultDesktopCommand key in the /usr/NX/etc/node.cfg configuration file:
DefaultDesktopCommand “env LD_LIBRARY_PATH=<directory where Mesa’s libGL.so is in> <command to start KDE>”
You can find the path to Mesa’s libGL by issuing this command:
ldconfig -p | grep libGL
For example:
DefaultDesktopCommand “env LD_LIBRARY_PATH=/usr/lib64 /usr/bin/dbus-launch –exit-with-session startkde”
Hello.
You can send the logs to forum[at]nomachine[dot]com.
Is your server a headless machine? Or is it running in a virtual machine?
Hello!
Please try to uncheck the ‘Use acceleration for display processing’ option in the NoMachine Preferences, Performance tab. You can reach them from the tray icon by clicking on Show the server status, inside your virtual machine.
Hello,
as for your points above:
1) Are you using proprietary nVidia drivers? You can try to send us the logs for inspection. NoMachine logs can be gathered by following the instructions in https://www.nomachine.com/DT07M00098. Also the .xsession-errors file in the user’s home on the server, if present, could be useful. You can send everything to forum[at]nomachine[dot]com.
3) Please try to disable the Fit to window mode and check if the hidden taskbar is still unreachable. It could be an effect of the scaling of the session, where the 1-pixel sensible area could be rounded down to 0 pixels. Ragarding the strange behaviours of the taskbar, we will try to reproduce them in our labs, but, if possible, a screen recording could help to clarify the issues.
You’re perfectly right in saying that this is not a minor issue! We are already working on it, but unfortunately it can’t be a quick fix. Video encoders don’t support such high resolutions themselves. The solution is to encode monitors in separate video streams, but this is quite a big change and it will take some time and many tests.