Forum Replies Created
-
Posts
-
After further investigations, we spotted a possible problem and are working on a fix. The issue could be possibly triggered by not having XQuartz installed on your Mac. XQuartz is a prerequisite for running custom sessions in floating window mode. Is this your case? And if it is already installed, could you try to start it manually before starting the custom session?
This is not a known issue. The crash log would really help. Also the the nxplayer’s logs could help (‘/Users/<name>/.nx/R-*’ directory).
X2go and Thinlinc clients and servers are able to discover and set screen resolutions correctly. Why is NoMachine unable to do this?
You are probably talking about different types of products. NoMachine free is for sharing the physical desktop, and possible resolutions are the ones made available by the hardware. Of course there is no limitation on screen resolutions if we talk of virtual sessions, that are supported by the NoMachine Workstation and the Enterprise products.
I found the default desktop configuration in node.cfg using the DefaultDesktopCommand. I am able to start XFCE4 but unable to start metacity, when I specify:
DefaultDesktopCommand “/usr/bin/X11/metacity”
only a black screen appears, though it’s not a problem to log in to metacity when lightdm is started.
Using the configuration
DefaultDesktopCommand “/usr/bin/X11/startxfce4”
starts fine XFCE4 though. Could I make somehow to start metacity also when using NX’s X server as I can with XFCE4?
Metacity is just a window manager, not a full desktop environment, so I’m not sure what you meant to run. That command will only start the window manager and it is normal that you will see a black screen. Probably you wanted to run the gnome-classic flavour, that uses metacity as default window manager. In that case the command would be:
DefaultDesktopCommnd “/etc/X11/Xsession ‘gnome-session –session=gnome-classic'”
You can find a list of available session type in ‘/etc/share/gnome-session/sessions’. More can be installed.
Hi,
that attempt to set a 1×1 desktop resolution sounds strange, and we are trying to figure out how that can happen.
In any case, you will always be stuck to a 1024×768 resolution, because that is what the video drivers make available when no monitor is connected.
You can try the suggestions in this post to solve the problem:
https://www.nomachine.com/forums/topic/ubuntu-16-04-headless-resolution-stuck-1024×768#post-11035If the NoMachine’s own X sever is used, you will be able to set any resolution.
Hi,
we cannot reproduce this issue in our labs and the /etc/hosts file didn’t show anything abnormal.
We are preparing a patched library with debug logs to send to you, if you are willing to test it.
In the meanwhile, are you able to say what the ‘192.168.14.24’ address is? Is it the IP of the server where you are connecting to?
We found it in the following log, that is somehow related to your problem:
Warning: Refusing connection from ‘192.168.14.24’ port 36450.
Hi.
We were not able to reproduce this problem in our labs. Can you tell us the following:
– What is the Ubuntu version, and what hardware (or virtualization tool) it is running on?
– Does the ‘xrandr-output.png’ image show the full command’s output? If not, can you show us all of it?
– What is the GPU/driver version? Please send the output of ‘lshw -C display’.
Hi,
we tested again SLES11 in our labs without observing any performance problem. Problems with drivers could be expected though on the HP or in the vmware machines, but it is strange you have performance problems in the workstation with nvidia’s proprietary drivers. Are you sure the symptoms are the same on all machines, with X using a lot of CPU?
For further investigations, please send us the following info from the workstation with the nvidia card:
– the ‘/etc/X11/xorg.conf’ file
– the output of the ‘lspci -d 10de: -v’ command
From the other machines, the output of:
– ‘lshw -C display’ command
Hi,
the problem is that the graphics card stops working when the cable is unplugged, and the X server stops rendering properly.
You can work around this problem by trying the instructions in this post:
https://www.nomachine.com/forums/topic/ubuntu-16-04-headless-resolution-stuck-1024×768#post-11035If you stop the lightdm service, for example, NoMachine will create a virtual display that will work without problems.
Hi!
Screen blanking on virtual machines is not supported, since it has effect on the physical monitor.
We will update the documentation to be more clear about that.
Hi.
We couldn’t reproduce on any harrdware we tested on. Could you tell us something more specific about the cards and the drivers?
As far as I understand, you are observing these performance problems running NoMachine within a VM. If so, which VM type, software vendor and specific version?
Hi!
Those exceptions usually are not fatal and don’t cause a crash. Can you send us the logs for further investigation? Here are the instructions for gathering them: https://www.nomachine.com/DT07M00098. You can send them to forum[at]nomachine[dot]com.
Hello.
This problem has been observed in the past with specific video drivers. See: https://www.nomachine.com/forums/topic/xorg-high-cpu-utilization-matrox-bug.
Can you tell us more about your graphics card and installed drivers?
Hi adamtg,
I’m afraid there is no tweak in NoMachine that can help with this problems, that depends exclusively on how firefox and some other applications draw. We verified that the issue is reproducible also without NoMachine. We could even see the white windows for a moment on the real monitor when opening the lid. You could try instead to find some tweak in firefox settings, for example the ones related to the hardware acceleration.
Hello.
The list of sessions is described in the ‘/usr/share/xsessions/’ directory and corresponds to the .session files that you can see in ‘/usr/share/gnome-session/session’. The number of available sessions depends on what you have installed on the system.
Here you can see a few examples: http://askubuntu.com/questions/62833/how-do-i-change-the-default-session-for-when-using-auto-logins