[00:59] 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] (I changed two lines in the main.py file and that was it :D) [01:11] Installation succeeded, updates work, sources.list looks sane! [01:47] Nice work arraybolt3 [01:48] :) & yeah well done arraybolt3 ; thank you. [01:48] :) [02:14] 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] 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] yeah I do note `telnet 0.17+2.4-2 ` in the lunar manifest (also `telnet 0.17+2.4-2`) [02:18] sorry also `inetutils-telnet 2:2.4-2` [02:19] * arraybolt3 builds the bugfixed calamares-settings-ubuntu package [02:19] Thank you for noticing kgiii ! [02:19] arraybolt3, is that why? (telnet) [02:19] Nah, still the lsb_release bug. [02:20] ack & thanks. [02:20] Just now got the package updated and am test-building. [02:20] 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] ubuntu-standard depends on telnet :-/ [02:21] Er, it Recommends it. [02:21] I was just going to mention it is on server too so it is in the base [02:21] I guess it's considered part of a "comfortable command-line Unix-like environment". [02:22] I mean it's not really a problem, it doesn't cause a security hole on its own. [02:22] Right, it isn't daemon that is listening or anything. [02:22] If telnet*d* was installed then I'd be worried :P [02:23] exactly [02:24] No, no... It existing isn't bad. The last time I used it, I watched ASCII Star Wars. [02:36] 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] :) thanks [02:50] 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] Not intentionally that I know of. [02:51] my just made install had ~4GB (its in another room so can't see screen) [02:51] :O [02:52] My newly made install only has 512 MB. [02:54] `free -h` shows `Swap: 3.9Gi 0B 3.9Gi` (my fingers just add -h on many commands) [02:54] I ran "swapon" to tell. [02:54] But free -h reports similar results (512 MB) for me. [02:55] okay yep that's it... /swapfile is 512MB with zram providing 3.4GB [02:55] Ah, that makes sense. [02:55] thanks arraybolt3 [05:19] tsimonq2 or whom has access to GitHub: Need the mirroring on calamares-settings-ubuntu reversed. [05:19] Currently I can't push to the calamares-settings-ubuntu repo on Gitea. [05:20] So I'm just gonna upload to the archive to unbreak things and keep the code locally to push once I can. [05:34] Fix finished, tested, and uploaded. [09:35] [telegram] That is in Launchpad (re @lubuntu_bot: (irc) Currently I can't push to the calamares-settings-ubuntu repo on Gitea.) [14:41] @kc2bez: Hmm... I *think* I have write access there, let me find out... [14:43] [telegram] 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] Uh... where is it? [14:43] It's not in ~lubuntu-dev's code... [14:44] * arraybolt3 really should bookmark it once it's found [14:44] Actually I bet Gitea will tell me. [14:44] [telegram] https://git.launchpad.net/~ubuntu-qt-code/+git/calamares-settings-ubuntu [14:44] Nice. [14:45] [telegram] I was going to mention that. It is at the top in the Gitea repo [14:45] Oh nice, TIL that you can see it there. [14:45] (I went to the Settings menu to find it.) [14:47] Alright, it appears to have let me push to it. [14:58] [telegram] 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] 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] More on-topic, the Calamares fix is in the latest ISO and I'm testing it now. [17:37] ISO is unbroken! [17:40] [telegram] That is terrific! [18:06] [telegram] running a quick double check (re @lubuntu_bot: (irc) ISO is unbroken!) [18:09] Confirm ISO good - nice work [18:09] 1 [18:11] Woot! [19:50] 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] Not consistently, but it does happen intermittently for me [19:51] tsimonq2: What is it that happens anyway? [19:51] I couldn't figure out what they were saying. [19:51] "the position does not start in the default" means very little to my brain :P [19:51] The monitor positions will be switched [19:52] For me the new monitor always appears on the right. I'll try a few reboots. [19:53] tsimonq2: This is on physical hardware that this happens right? [19:53] 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] er, things wrong with the display that didn't happen in VBox. [19:58] OK so I was able to make things go weird - trying to switch the order of the screens was severely glitchy in 20.04.