On a lark, I decided to whittle that down to just the following:ĪvailableSessionTypes physical-desktop,unix-xsession-default,unix-xdmĪfter making the same change to /usr/NX/etc/server.cfg, I was able to login to Budgie. End A: ubuntu 20.04 -internet - End B: ubuntu 18.04 / AWS. after a bit more digging, I noticed a few lines down:ĪvailableSessionTypes unix-remote,unix-console,unix-default,unix-application,physical-desktop,shadow,unix-xsession-default,unix-gnome,unix-xd Recall of the situation: A is my desktop and B is my server. So, I added the following like to my /usr/NX/etc/node.cfg:ĭefaultDesktopCommand “/usr/bin/budgie-desktop” Therefore there would be no alternate desktop environment and I’d bypass having to figure out why GDM wasn’t working. Unfortunately it would start-up and die with a rather vague “DEBUG: Process 1455 terminated with signal 6” message.Īfter a bit of research I found the following: My solution to that problem was to uninstall Gnome, remove GDM and re-install Budgie, which defaults to LightDM. Logging out would end the NoMachine session and if reconnecting it would launch Gnome again. At first, I just tried to install Budgie and was able to connect successfully but upon connecting, instead of getting the GDM login screen with session options, I’d be logged in directly into Gnome. My goal was to install NoMachine 6 on a freshly installed instance of Ubuntu 18.04 with Budgie as the desktop environment (I’m not a fan of Gnome). I spent a considerable amount of time trying to get this to work and most of what I’ve learned was through trial and error. In the next article we are going to take a look at NoMachine Remote Desktop and see how to install it on Ubuntu 18.04. I’ll state up-front that this is not a highly technical post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |