[00:59] <arraybolt3> OK, so literally the only thing we used lsb_release for in the automirror module was to get the release codename. So I have swapped out lsb_release for python3-distro with almost zero effort involved and am doing a test installation.
[01:00] <arraybolt3> (I changed two lines in the main.py file and that was it :D)
[01:11] <arraybolt3> Installation succeeded, updates work, sources.list looks sane!
[01:47] <kc2bez> Nice work arraybolt3
[01:48] <guiverc> :) & yeah well done arraybolt3 ; thank you.
[01:48] <arraybolt3> :)
[02:14] <kgiii> I am just now getting to my daily testing. I removed one manifest and did my usual 'diff' to see what's changed. I saw 'telnet' listed. That's horribly insecure and very old tech but we probably have something that depends on it still. 
[02:15] <arraybolt3> Heh, I have Telnet installed by default here in Kubuntu.
[02:17]  * guiverc has device(s) (I think) on my network that may still use telnet... 
[02:17] <guiverc> yeah I do note `telnet  0.17+2.4-2 ` in the lunar manifest  (also `telnet  0.17+2.4-2`)
[02:18] <guiverc> sorry also `inetutils-telnet        2:2.4-2`
[02:19]  * arraybolt3 builds the bugfixed calamares-settings-ubuntu package
[02:19] <guiverc> Thank you for noticing kgiii !
[02:19] <guiverc> arraybolt3, is that why?  (telnet)
[02:19] <arraybolt3> Nah, still the lsb_release bug.
[02:20] <guiverc> ack & thanks.
[02:20] <arraybolt3> Just now got the package updated and am test-building.
[02:20] <kgiii> I'm guessing something somewhere still relies on telnet. Buggered if I know what... "Telnet, now there's a name I haven't heard in a long time..."
[02:21] <arraybolt3> ubuntu-standard depends on telnet :-/
[02:21] <arraybolt3> Er, it Recommends it.
[02:21] <kc2bez> I was just going to mention it is on server too so it is in the base
[02:21] <arraybolt3> I guess it's considered part of a "comfortable command-line Unix-like environment".
[02:22] <arraybolt3> I mean it's not really a problem, it doesn't cause a security hole on its own.
[02:22] <kc2bez> Right, it isn't daemon that is listening or anything.
[02:22] <arraybolt3> If telnet*d* was installed then I'd be worried :P
[02:23] <kc2bez> exactly
[02:24] <kgiii> No, no... It existing isn't bad. The last time I used it, I watched ASCII Star Wars.
[02:36] <arraybolt3> This is ridiculous. apt-cacher-ng is so unstable I'm having to interrupt a build over and over to restart it to get things to download.
[02:40]  * guiverc suggests arraybolt3 ensure the right music is on... & you will still smile..
[02:40] <arraybolt3> :) thanks
[02:50] <guiverc> has swap been increased beyond 512MB???   I've got more than 512MB in swapfile   (I've not installed lunar in awhile; only jammy.2 ~recently
[02:50] <arraybolt3> Not intentionally that I know of.
[02:51] <guiverc> my just made install had ~4GB (its in another room so can't see screen)
[02:51] <arraybolt3> :O
[02:52] <arraybolt3> My newly made install only has 512 MB.
[02:54] <guiverc_t> `free -h` shows `Swap:          3.9Gi          0B       3.9Gi`   (my fingers just add -h on many commands)
[02:54] <arraybolt3> I ran "swapon" to tell.
[02:54] <arraybolt3> But free -h reports similar results (512 MB) for me.
[02:55] <guiverc_t> okay yep that's it... /swapfile is 512MB with zram providing 3.4GB
[02:55] <arraybolt3> Ah, that makes sense.
[02:55] <guiverc_t> thanks arraybolt3
[05:19] <arraybolt3> tsimonq2 or whom has access to GitHub: Need the mirroring on calamares-settings-ubuntu reversed.
[05:19] <arraybolt3> Currently I can't push to the calamares-settings-ubuntu repo on Gitea.
[05:20] <arraybolt3> So I'm just gonna upload to the archive to unbreak things and keep the code locally to push once I can.
[05:34] <arraybolt3> Fix finished, tested, and uploaded.
 That is in Launchpad (re @lubuntu_bot: (irc) <arraybolt3> Currently I can't push to the calamares-settings-ubuntu repo on Gitea.)
[14:41] <arraybolt3> @kc2bez: Hmm... I *think* I have write access there, let me find out...
 If not, create a MP and I can merge it. Then Simon can add you later if he doesn't get to it first.
[14:43] <arraybolt3> Uh... where is it?
[14:43] <arraybolt3> It's not in ~lubuntu-dev's code...
[14:44]  * arraybolt3 really should bookmark it once it's found
[14:44] <arraybolt3> Actually I bet Gitea will tell me.
 https://git.launchpad.net/~ubuntu-qt-code/+git/calamares-settings-ubuntu
[14:44] <arraybolt3> Nice.
 I was going to mention that. It is at the top in the Gitea repo
[14:45] <arraybolt3> Oh nice, TIL that you can see it there.
[14:45] <arraybolt3> (I went to the Settings menu to find it.)
[14:47] <arraybolt3> Alright, it appears to have let me push to it.
 Yup, looks to be good.
[17:18]  * arraybolt3[m] uploaded an image: (388KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/EVgypCHZwQsltiVfQiFpFaRZ/image.png >
[17:19] <arraybolt3[m]> Apparently Lubuntu is now recognized specifically within VirtualBox. So is Xubuntu and Ubuntu, strangely no other flavors are listed in the "Version:" dropdown.
[17:19]  * arraybolt3[m] probably should have put this in -offtopic
[17:20] <arraybolt3> More on-topic, the Calamares fix is in the latest ISO and I'm testing it now.
[17:37] <arraybolt3> ISO is unbroken!
 That is terrific!
 running a quick double check (re @lubuntu_bot: (irc) <arraybolt3> ISO is unbroken!)
[18:09] <LeoK[m]> Confirm ISO good - nice work
[18:09] <LeoK[m]> 1
[18:11] <arraybolt3[m]> Woot!
[19:50] <arraybolt3> tsimonq2: Were you able to reproduce bug 1880418? I just tried and didn't see anything wrong, and so marked it as incomplete.
[19:50] -ubottu:#lubuntu-devel- Bug 1880418 in lxqt-config (Ubuntu) "Secondary monitor config not working" [Undecided, Incomplete] https://launchpad.net/bugs/1880418
[19:51] <tsimonq2> Not consistently, but it does happen intermittently for me
[19:51] <arraybolt3> tsimonq2: What is it that happens anyway?
[19:51] <arraybolt3> I couldn't figure out what they were saying.
[19:51] <arraybolt3> "the position does not start in the default" means very little to my brain :P
[19:51] <tsimonq2> The monitor positions will be switched
[19:52] <arraybolt3> For me the new monitor always appears on the right. I'll try a few reboots.
[19:53] <arraybolt3> tsimonq2: This is on physical hardware that this happens right?
[19:53] <arraybolt3> In that even VirtualBox might not be usable, since I've had things that couldn't be reproduced in a VM with the monitor.
[19:54] <arraybolt3> er, things wrong with the display that didn't happen in VBox.
[19:58] <arraybolt3> OK so I was able to make things go weird - trying to switch the order of the screens was severely glitchy in 20.04.