Forum Replies Created
-
Posts
-
Run sudo apt-get autoclean –sudo apt-get autoremowe. Run the following command to clear the package cache. Update: -sudo apt-update your system using the following command-sudo apt-get upgrade
Updating the server-side installation might help.
You’d have to try Enkidu. Could you also tell us whether logging in to the desktop first (on the local server side) and then starting your NoMachine session makes a difference? This would allow us to narrow down the investigation.
If you can still reproduce the behaviour, we will need logs from the Ubuntu server. Enable logs following the instructions here: https://kb.nomachine.com/DT11R00182, reproduce the problem, then gather the logs from the server. Send directly to forums[at]nomachine[dot]com.
Hi, when you log in, does the spinning wheel show in the NoMachine window. Do you get past this stage?
I never see the desktop
Do you see a black screen? Do you see a message of any kind?
Please submit a screenshot of what you see from log in to the final stage where the login doesn’t proceed.
We have reproduce something similar and there is a Trouble Report open: https://kb.nomachine.com/TR07S10316.
Please take a look at: https://forums.nomachine.com/topic/vnc-considered-as-physical-desktop#post-9542.
Hi, can I ask which folder your connection files are stored? By default they are in Documents/NoMachine on your computer, but if you have them on a network disk somewhere, for example, they may become unreachable for some reason.
Just for the record, the local network connections will only disappear if you choose not to see them, or if those computers are configured to not broadcast themselves on the local network 🙂 See here for details on both of those: https://forums.nomachine.com/topic/how-to-clean-recent-connections-list#post-29887
Please everyone update their installations to the latest version. If you continue to have problems, open a new topic. Thanks!
This topic is now closed. Please contact us via the website (https://www.nomachine.com/contact-request) if you have feedback about the test package, would like to submit logs or provide other info that is useful for the investigation. Thanks!
Hi,
NoMachine for Linux includes a nxagent virtual X server that you can run, just to make one X server that the system can “see”, one that can run your desktop software and one you can connect to. When the Linux machine is headless, NoMachine detects that there is no X server running and prints the message:
Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?
to which you should click “Yes”. Did this appear the first time you connected? What happened? What happened the second time?
When you connected previously, and it was working, is it possible that a monitor was attached and on? After connecting the first time, and then disconnecting the session, did the monitor turn off or maybe it’s a laptop and you closed the lid? It could be that the graphics card installed there did not correctly detect one or the other events (so it’s not NoMachine at fault here).
Take a look at this article and follow the tips there:
Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973Also, if Wayland is the display server running there, please check the article here:
HI, with the release of v7 all details from the folder were moved to redis database to increase performance of the NoMachine server. I can confirm that to be able to identify session name with display and username included you can use the command
--history --verbose.Eshama, what desktop environment (DE) is running on your Linux SLED ie. is it Gnome, KDE, LXDE, something else? Is it the NoMachine Free Edition running there? Were you able to connect before?
We are not aware of similar problems with Suse or Ubuntu.
What Ubuntu desktop environment is installed in that VM? NoMachine can install in any VM, what’s important is that there is a desktop environment running there.
You can check with
grep ^Exec /usr/share/xsessions/*Take a look at:
How to run a virtual desktop environment on Linux different from the default one with NoMachine
https://kb.nomachine.com/AR04K00667to know how to set the right desktop.
I’ll as the same question that I asked in your other topic (https://forums.nomachine.com/topic/the-session-negotiation-failed-error-node-was-not-retrieved):
I assume you are using the latest version on the SLED host. What desktop environment are you connecting to?
Hi, I assume you are using the latest version of NoMachine on the Ubuntu host. What desktop environment are you connecting to?
System users authentication doesn’t work on systems with pam.d placed in a different location than /etc/pam.d.
It looks like you have the same issue which was reported a while back by another user. The problem is not in NoMachine, but the fact that you have pam.d iconfig files in two places in your OS. (https://kb.nomachine.com/TR02R09538)
As a workaround, link pam.d to /etc/ directory before installing NoMachine:
sudo ln -s /usr/share/defaults/etc/pam.d /etc/pam.dor add manually nx and nxlimits files to
pam.d directory (/usr/share/defaults/etc/pam.d):cat /usr/share/defaults/etc/pam.d/nx auth include su account include su password include su session include su cat /usr/share/defaults/etc/pam.d/nxlimits session optional pam_limits.so