Linux

I was trying to install Amazon Games on my Lutris installation on my old laptop and ran into a curious situation. I was able to complete the installation ok as I was able to log into the Amazon Games launcher and install a game. However, I noticed that there was a command line terminal window from the installation process still running in the background even though the installation had proceeded successfully. According to this window, the installation was not complete and the only option I had was to Abort.

I was trying to install Epic Games on my Lutris installation on my old laptop and ran into the following error message:

Exit with return code 256

(This appears to be a common issue and is not necessarily limited to Epic Games.)

I actually removed my default Ubuntu package which was a few minor versions behind the official packages. I then installed the latest version of Lutris directly using a .deb file from their website.

So, I've been facing some DNS issues with my Ubuntu box and needed to do some debugging. While I was certain that my router was assigning the Google DNS servers (8.8.8.8 and 8.8.4.4) via DHCP to my machine, I needed to make sure that they were actually being used. Usually, I would be able to tell by looking at the output of /etc/resolv.conf oslt. However what I found in resolv.conf was


nameserver 127.0.0.53
options edns0 trust-ad


So I have a Xubuntu box, an old PC that was running Windows previously. All is peachy with the Linux install bar one thing: every time I shutdown the system, it shuts down fine, but immediately restarts again. This wasn't happening with Windows and appeared to be an issue particular to Linux or Ubuntu.

Here are the steps I used to get X11VNC working on an Ubuntu (19.10) box. Hope this helps somebody else out there too.

Freeplane, a fork of the mind-mapping program, Freemind, works really well. Except for the fact that in my (K)Ubuntu installation, it sometimes hangs in the middle of editing a node. Once it becomes non-responsive, the only fix is to kill the process and restart the program. The version of Freeplane in Ubuntu 18.04 is 1.6.13. However, the current version (March 2019) of Freeplane is 1.7.7. So, it's highly possible that upgrading Freeplane to the latest version will fix this issue.