Fixed bug Daedalus container in Easy Daedalus

This bug should have been glaringly obvious, before Easy Daedalus 6.5 got released. But somehow missed it. This is partly due to Easy Daedalus being new, and my attention is divided between Scarthgap and Daedalus (and mostly I'm working on Scarthgap).

When the host system is Easy Daedalus, and you click on the "daedalus" desktop icon, Daedalus then starts up in a container. However, what I saw today, glaringly obvious but overlooked, was the container icons were still on the desktop. They should not be there, as cannot run a container within a container.

Inside the container, you will see /.control/easy.run-once-top and /.control/daedalus.run-once-top-flag -- the latter is a flag that the former has run. However, there is a logic problem, and the former has not actually run. The former cleans up Daedalus in the container, including remove the desktop container icons.

The fix is here:

https://github.com/bkauler/woofq/commit/5dd28a8a9a85ff365e3921bf69686025d28692b6

I'm annoyed that I didn't spot that earlier. Oh well.

I had actually built Easy 6.5.2 and was about to upload it. Easy Scarthgap 6.5.2 has already been uploaded; which is ok, not affected by that bug. However, there is something else that affects Scarthgap, so I will probably build both of them as 6.5.2.1 and upload, probably tomorrow.

If you already have run the Daedalus container in Easy Daedalus host system, I recommend apply this fix:

Go to /mnt/wkg/containers/daedalus/.session/.control (without the container running) and delete file 'daedalus.run-once-top-flag'
Then after updating to 6.5.2.1, click on the "daedalus" desktop icon and this time 'easy.run-once-top' should execute.   

Tags: easy