[09:46] <kc2bez> arraybolt3: The Calamares bug you filed should probably be closed. The code has already been applied upstream to fix the issue. You have to remember we don't always carry the latest versions of things. We may need to apply a patch to bring in newer code to older versions. That happens at the distribution level not upstream.
[17:09] <arraybolt3> @kc2bez Didn't realize that, since my mod to the code worked. The Calamares devs have already closed it. However, one of the devs (Adriaan de Groot) also found where our config was messed up and was kind enough to provide the fix (our mount.conf file needs to bind-mount /run rather than mounting tmpfs there). I've verified that this fix works.
[18:55] <kc2bez> No worries arraybolt3 I had my time line messed up, I noted that on the issue. 
[18:57] <kc2bez> We should probably test things with updated versions before making an issue upstream. Calamares is pretty good to work with but LXQt will close them quickly if we don't test them with the latest. 
[19:00] <kc2bez> I appreciate your help arraybolt3 
[19:00] <arraybolt3> @kc2bez Thanks. BTW, how exactly do you test a new version of Calamares? Is there some way to add a PPA or someting within the live environment to update to the latest version? Or do you do it the hard way and build your own ISO?
[19:02] <kc2bez> There are 2 ways. Build it from source on the live iso or package it and put it in a PPA and update the live iso using that PPA. 
[19:02] <arraybolt3> And thanks for saying it was OK - I was pretty embarrassed to have done so much testing and have been sure that I found the bug, and then to open up everything when I woke up and see that I had missed it.
[19:03] <arraybolt3> OK. I've built QEMU from source, so I have some experience with that.