NX> 700 Creating configuration in: /usr/NX/etc/server.cfg. NX> 700 Installing: nxserver version: 6.9.2.
#Ubuntu remote desktop server 16.04 command line install#
NX> 700 Node install completed with warnings. To specify the location of the CUPS root path. usr/NX/scripts/setup/nxnode -printingsetup NX system at any time to do this make sure that you have Please note that you can enable printing support for your Needed in order to enable printing support in your NX System or it was installed in a non-standard path. The NoMachine Node setup procedure could not detect yourĬUPS installation: either CUPS is not installed on your NX> 700 Displaying file: /usr/NX/share/documents/node/cups-info NX> 700 Creating configuration in: /usr/NX/etc/node.cfg. NX> 700 Installing: nxnode version: 6.9.2. NX> 700 Please review the install log for details. NX> 700 Player install completed with warnings. NX> 700 the user account must be a member of the CUPS System Group. NX> 700 To connect the remote printer to the local desktop, NX> 700 Installing: nxplayer version: 6.9.2. NX> 700 Install log is: /usr/NX/var/log/nxinstall.log. NX> 700 Using installation profile: Debian. NX> 700 Installing: nxclient version: 6.9.2. 276093 files and directories currently installed.) Selecting previously unselected package nomachine. The following NEW packages will be installed:Ġ upgraded, 1 newly installed, 0 to remove and 597 not upgraded.Īfter this operation, 192 MB of additional disk space will be used. Note, selecting 'nomachine' instead of './nomachine_6.9.2_1_b' That ended up breaking not too long ago so now I have to use isolate, which anyway is most certainly all around better.Sudo apt install. My previous version was saying to use start to restart the multi-user.target. The -all options shows you the inactive targets as well. Yet, there is a command to check that out: Obviously, you should know what the current status is: whether you are in your graphical system or in your consoles. You can simply reboot once in a while when the environment decays too much. Of course, you may just decide not to have to deal with that sort of things anymore and just stay in your X11 console throughout time. Sudo chvt 1 & sudo systemctl isolate multi-user.target To fix that problem, you may use the chvt command line option: The switch back will generally take you to TTY 7 or 8 which is likely to be a black screen or have some boot logs, not a login prompt or the console you started from. The command switches you back to the standard super fast text consoles. Instead, you have to switch back to multi-users with a similar command: Only this won't give you the option of logging out of X11 as you could before with the log out menu. The command will start X11 and Unity as expected. However, since 15.10, or maybe even 15.04, Ubuntu uses systemd which is expected to be used to start the X11 environment. You can do that manually (or many tweak to a personal script that gets run by startx) with: That is, startx will start the X11 screen but not Unity. Instead of startx, we now want to run X11 with systemd which will make sure that all the necessary parts get loaded as expected. Startx # not working well with Ubuntu 16.04 / Unity As of 2016, the memory footprint may have been less of a problem, but it still cleans up all sorts of things, especially when upgrades happen. I actually work in X11, but log out nightly so that way memory is not as tight and X11 is reset at least daily (which with my old setup was a good thing). Now you may want to start X11 once in a while. Sudo systemctl set-default graphical.targetĪnd you will get the usual lightdm (or gmd) prompt instead of a console. To go back to graphical boot, use the graphical target instead: This prevents the graphical boot and starts using the console instead. Sudo systemctl set-default multi-user.target To boot in the console, you have to set that as the default: Systemd has a list of variables you can tweak using the systemctl command. See X11 Auto-starting for details about older versions. I already had the GRUB variables setup as expected:īut this is not enough if you want to start in the console when running systemd (which is running since 15.04). This is because the computer is now using systemd to boot. I had it properly setup to boot in a console before, but somehow it changed the behavior on me. As I just upgraded my 14.04 installation to 16.04, it booted right up to lightdm.