 Happy New Year! 00:01 GMT 01 Jan 2024 here!
[00:02] <arraybolt3> 🎉
[00:02] <arraybolt3> Six hours of 2023 left over here.
 1:41 2024 here
 Happy New year
 Happy New Year from Eastern US
[14:14] <arraybolt3> https://raphaelhertzog.com/2010/09/21/debian-conffile-configuration-file-managed-by-dpkg/ well here's a good conffile solution for Lubuntu Update perhaps - use --force-confdef and --force-confold during the upgrade, then scan the filesystem for dpkg-dist files and prompt the user what to do about them?
[14:15] <arraybolt3> Better yet, if apt gives some hint of when a conffile has been dropped, then there's no need for a lengthy filesystem crawl operation.
[14:15] <arraybolt3> (plus even if a filesystem crawl is used, we can leave out all the dirs that won't ever have package conffiles in them, like /home, /media, /mnt, and so on)
[14:20] <arraybolt3> Perfect, apt does let me know when conffiles are changed even when doing everything automatically.
 arraybolt3: Politely voluntelling you that this is your bug to solve :) https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2047379
[14:44] -ubottu:#lubuntu-devel- Launchpad bug 2047379 in lubuntu-installer-prompt (Ubuntu) "booting lubuntu noble daily and getting black screen + wallpaper but no try/install dialog" [Critical, Triaged]
[14:45] <arraybolt3> "to get the TRY/INSTALL dialog; I needed to hit ALT+TAB and then I have the TRY/INSTALL dialog appear on top of the wallpaper screen" what on EARTH?!
[14:45] <arraybolt3> ok, that's weird
[14:46] <arraybolt3> ahhh, I think I get it
 I can reproduce it :)
[14:47] <arraybolt3> haha, I forgot an else {}
 (Figured I'd give you the first shot at it)
 Niceeeee
[14:47] <arraybolt3> or... did I?
[14:48] <arraybolt3> oh, no, I botched something totally different
[14:48] <arraybolt3> I'm using "continue;" rather than "else {}", but I'm not properly setting which screen the installer prompt itself goes on.
[14:48] <arraybolt3> so I need a w->setGeometry() before a w->showFullScreen()
 I haven't looked at the exact code specifics here, but what I can tell you is that both are appearing on the same monitor
[14:49] <arraybolt3> ok, lemme set up a VBox system to test on
[14:52] <arraybolt3> also it dawns on me all this is going to go up in flames once Wayland becomes default :-/
[14:52] <arraybolt3> unless Qt can somehow set which screen a window appears on under Wayland
[15:11] <arraybolt3> oof, just ran into a *nasty* bug. Use multiple monitors, change which one is the primary monitor. The panel doesn't change screens. Now try interacting with the panel (i.e., click on the Application Menu). The panel remains on the original screen but the menu pops up on the new primary screen.
[15:22] <arraybolt3> tsimonq2: Patch made, partially tested, and seems to work. Note that I could *not* reproduce the issue with the testing I did in VirtualBox (if I can reproduce it, I surely didn't manage to with the trick I used), but the patch didn't make things any worse, and since it works in the same way I'm positioning the background screens, I'm reasonably
[15:22] <arraybolt3> certain it will do the trick.
[15:22] <arraybolt3> I don't have upload permissions to that package so I'll need your assistance in getting it uploaded. I pushed it to Git already.
 Sounds good. I'm slowly making my way to the office and will handle that then
[18:25] <arraybolt3> If anyone wants to check a security-sensitive Bash script, https://termbin.com/h235 This is the script I intend to use as the backend for Lubuntu Update. It runs as root, Lubuntu Update runs as a standard user, and Lubuntu Update can sent commands to the script via stdio. I tried to use a trick to harden it so that people couldn't hack it into
[18:25] <arraybolt3> deleting arbitrary files, but since it's still sensitive and involves an untrusted program sending data to a trusted one, I thought it would be worth some extra checking. Also, it's currently entirely untested.
[19:32] <tsimonq2> Good morning, and Happy New Year!
[19:32] <tsimonq2> It's already the 2nd for the Australians, so I think we're ready to get back into things for the year.
[19:33]  * lubot [matrix] <kc2bez> looks at watch
[19:33] <tsimonq2> Over the course of the break, I assigned some bugs to ~lubuntu-dev. These are bugs which are on our radar to fix this cycle, but don't have anyone specifically assigned to them yet. If you would like to take on a bug, please reassign it to yourself.
[19:33] <tsimonq2> https://bugs.launchpad.net/~lubuntu-dev/+assignedbugs
[19:33] <tsimonq2> bah it's still morning for wxl, good enough XD
 and me
[19:33] <tsimonq2> I forget sometimes ;D
[19:34] <tsimonq2> Anyway, I'm going to start by uploading https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2045741
[19:34] -ubottu:#lubuntu-devel- Launchpad bug 2045741 in calamares (Ubuntu) "Installer lists 'American English' twice on welcome screen" [Low, Confirmed]
[19:34] <tsimonq2> arraybolt3: Your ballgame here, assigning to you, if you don't want it anymore please feel free to assign it back: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2047379
[19:35] -ubottu:#lubuntu-devel- Launchpad bug 2047379 in lubuntu-installer-prompt (Ubuntu) "booting lubuntu noble daily and getting black screen + wallpaper but no try/install dialog" [Critical, Triaged]
[19:35] <tsimonq2> @Roberalz: Ditto: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2047294
[19:35] <arraybolt3> tsimonq2: well you seem to be chomping at the bit :)
[19:35] <tsimonq2> @Roberalz: Assigning to you for advice/consent as our de facto Localization Lead; if you provide us with a good list, feel free to assign back to ~lubuntu-dev. :)
[19:35] <tsimonq2> arraybolt3: omnomnom
[19:35] <arraybolt3> I've been hard at work all day though :D
[19:36] <tsimonq2> Very nice :D
[19:36] <tsimonq2> Oh, right, you actually had some patches for that bug report.
[19:37] <arraybolt3> And uploaded them to Gitea already
[19:37] <arraybolt3> (it was a one-line patch)
[19:38] <arraybolt3> probably worth a patch release maybe, or maybe we just patch it in the packaging for now, your call
[19:40]  * arraybolt3 just wrote code that kicks around a QSystemTrayIcon pointer all over creation - not sure if this was the best approach...
[19:43] <tsimonq2> We're due for a patch release.
[19:43] <tsimonq2> I'll test it just to double check your work. :)
[19:46] <tsimonq2> arraybolt3: Isn't the primary monitor supposed to switch back and forth given input?
[19:46] <arraybolt3> w.r.t. the LXQt panel bug?
[19:46] <tsimonq2> Meaning, if I click on my non-active monitor, shouldn't all that info move over?
[19:46] <tsimonq2> Nah, installer prompt.
[19:46] <arraybolt3> Ah. No, I didn't design it to do that.
[19:47] <arraybolt3> It puts the prompt on whatever Qt thinks is the "main display" and makes all the others background displays.
[19:48] <arraybolt3> Theoretically on X it won't be too hard to do that. On Wayland, that may be a trial but that's not too much of a worry right now.
[19:48] <tsimonq2> Not a problem, as long as you don't think this will affect people with wonky displays.
[19:49] <tsimonq2> Also, I'm wondering if Calamares starts on the same display as the installer prompt. Haven't gotten around to testing a full install with dual monitors.
[19:49] <tsimonq2> Anyway, this is good enough to patch release now, we can deal with that later.
[19:50] <tsimonq2> I'm also going to s/lubuntu/Lubuntu in all of @Roberalz's translations. ;)
[19:50] <arraybolt3> If we end up revamping UI any, we might end up with a background screen on all screens and then have a window that pops up and offers the try and install options sort of like how Ubuntu Desktop does it. That would make it easier to do this sort of thing.
[19:51] <arraybolt3> I'd have to do some Wayland experiments, but it may be possible to make a window close and then re-open on a different display even under Wayland. We'll have to try it to find out though :D
[19:52] <arraybolt3> Also, what we could do is make it so that if the user doesn't click anything on the welcome screen for thirty seconds or so, it automatically drops to a live session.
[19:52] <arraybolt3> Then we're no worse off with a dead screen than we've always been.
 Well couldn't it take someone more than 30 seconds to find what language to switch it to
[19:59] <arraybolt3> valid point
[19:59] <tsimonq2> https://launchpad.net/ubuntu/+source/lubuntu-installer-prompt/1.1.2-0ubuntu1
[20:33] <tsimonq2> https://launchpad.net/ubuntu/+source/calamares/3.3.0.0-0ubuntu5
[20:33] <tsimonq2> https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-mantic-staging/+packages
[20:33] <tsimonq2> https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging/+packages
[20:33] <tsimonq2> https://launchpad.net/ubuntu/+source/vim/2:9.0.2189-1ubuntu1
[20:34] <tsimonq2> https://tracker.debian.org/news/1491136/accepted-vim-2902189-1-source-into-unstable/
[20:34] <arraybolt3> weeeeeee
[20:34] <tsimonq2> :D :D
[20:49] <tsimonq2> @RikMills: https://github.com/calamares/calamares/commit/8a199aaaf9d38a9b2126db1da82b775880bc7abc
[20:55]  * arraybolt3 realizes my parser for update progress can be fooled too easily
[20:55] <arraybolt3> sigh
[20:56] <arraybolt3> hey, it's not too hard to fix though
[21:05] <tsimonq2> niceeee
[21:08] <tsimonq2> comments++;
[21:09] <arraybolt3> (mainly for updating the progress bar, maybe entirely for that)
[21:09] <arraybolt3> Comments? What are those? /s
[21:09] <tsimonq2> XD
[21:09] <arraybolt3> alright so I really should document some thingsnhere
[21:09] <arraybolt3> Mmm, accurate typo, thanks ChromeOS
[21:09] <arraybolt3> you have talk to Texans and I have autoincorrect
[21:10] <tsimonq2> hahahahahahahahahahahaha
[21:13] <tsimonq2> https://twitter.com/LubuntuOfficial/status/1741927591722828214
[21:35] <arraybolt3> sheesh, that was harder than expected, and a bit spaghetti code-y. I need to refactor if this works, buuuuut... I think this may be usable.
[21:36] <arraybolt3> oh, lol, I got a great idea, let's *actually install* the backend updater script
[21:37] <arraybolt3> even better idea, let's call it with lxqt-sudo so it actually works
[21:39] <arraybolt3> one problem with how I'm doing this is that I adamantly insisted on using static everything for the apt manager, so my ability to communicate with signals is severely hampered and the code has turned into a ball of mess. So I'm going to go fix that before actually testing this.
 Ok (re @lubuntu_bot: (irc) <tsimonq2> @Roberalz: Assigning to you for advice/consent as our de facto Localization Lead; if you provide us with a good list, feel free to assign back to ~lubuntu-dev. :))
[22:01] <arraybolt3> vigorous re-factor, code is now *way* cleaner
[22:40] <arraybolt3> well, sigh, it's broken, but it's almost working :P
[22:42] <arraybolt3> Main problems are I'm reading from stdout when I need to be reading from stdout+stderr, and my parser function is crashy.
[23:22] <arraybolt3> Turns out snapshots are a lifesaver when writing code that needs to use apt updates to show you what it's doing, and this time I actually remembered to use them.