[00:46]  * arraybolt3 adds to the 23.10 todo list "make Apply Full Upgrade able to handle Snap refreshes"
[00:46] <lubot> [telegram] <teward001> arraybolt3: might not be possible
[00:46] <lubot> [telegram] <teward001> because if FIrefox is running and you queue the snap refreshes you only get the `all snaps up to date` reply
[00:47] <lubot> [telegram] <teward001> which doesn't actually address the issue
[00:47] <arraybolt3> Who's to say one can't search for running Firefox instances?
[00:47] <arraybolt3> If killall can kill them, something can find them.
[00:47] <arraybolt3> And that something can be called from Python.
[00:48] <lubot> [telegram] <teward001> well `killall` works with a pid search, but you *must* make sure that if `pidof firefox` shows a result, that you have to prompt to kill all firefox instances
[00:48] <lubot> [telegram] <teward001> because consider a multiuser system
[00:48] <lubot> [telegram] <teward001> with many people logged in at once using firefox via x forwarding, etc.
[00:48] <arraybolt3> Good point.
[00:48] <lubot> [telegram] <teward001> `sudo killall firefox` works because it calls `kill 15 {all PIDs}`
[00:49] <lubot> [telegram] <teward001> so consider Windows' office updater which says "We can't update Office while you're running these programs.  If you continue, thes programs will be shut down: [Word, etc.]"
[00:49] <lubot> [telegram] <teward001> you'd have to emulate something like that
[00:49] <lubot> [telegram] <teward001> doable, probably
[00:49] <arraybolt3> Depending on how fancy we wanted to get, it could say "Firefox needs updated, but is still running. Would you like to force close all open Firefox windows?" and if the user clicks Yes, it does it, updates Firefox in front of the user, and then kaboom!
[00:49] <lubot> [telegram] <teward001> but you MUST disclaim to the users that it COULD kill their processes and they'd lose existing data if they continue without first closing their data
[00:50] <arraybolt3> Yes.
[00:50] <lubot> [telegram] <teward001> yeah but you may want to do it by suggesting it more mildly: "Please save all work and close all Firefox windows before continuing."
[00:50] <lubot> [telegram] <teward001> that way it at least lets $USER know that Firefox is being closed to update if you don't close it yourself
[00:50] <arraybolt3> Could even add a button that scans for anymore running Firefox windows so the user can safely close them.
[00:50] <lubot> [telegram] <teward001> potentially
[00:50] <lubot> [telegram] <teward001> but let's start simple before we go super complex
[00:50] <lubot> [telegram] <teward001> a simple check if firefox is running and the warning might work
[00:51] <lubot> [telegram] <teward001> lets someone cancel out if they are in the middle of something important
[00:51] <arraybolt3> I'm thinking, if we can pull this off, people might be really happy with us :D
[00:52] <lubot> [telegram] <teward001> true
[00:52] <lubot> [telegram] <teward001> but it's a bit late in 23.04 for that
[00:52] <lubot> [telegram] <teward001> so this would be a 23.10 feature i think
[00:52] <arraybolt3> Very late. Thus why it would be fore 23.10.
[00:52] <arraybolt3> *for
[00:52] <lubot> [telegram] <teward001> as i said :)
[00:52] <arraybolt3> Yeah, I think that the Release Team would probably kill us if we tried to do it this cycle :P
[00:52] <lubot> [telegram] <teward001> so, lets focus on 23.04 release, and then focus on new stuff like this afterwards
[00:53] <arraybolt3> But I am still recording the idea for later.
[00:53] <lubot> [telegram] <teward001> arraybolt3: the only thing i think Release would forgive us for is if we fix a critical bug that otherwise fubar'd al of Lubuntu / LXQt
[00:54] <arraybolt3> We have something sorta kinda close to that :-/
[00:54] <lubot> [telegram] <teward001> arraybolt3: is it the pulse / pipewire thing?
[00:54] <lubot> [telegram] <teward001> the thing i needed to upload for y'all?
[00:55] <arraybolt3> @teward001: No, it's a private bug with Openbox.
[00:55] <arraybolt3> The pulse pipewire stuff was for Ubuntu MATE.
[00:55] <lubot> [telegram] <teward001> ah
[03:00] <guiverc> arraybolt3, new calamares slideshow looks GREAT !!; is it supposed to repeat?  (I thought the old one repeated, this appears not to... it was done completed yet install only 8% on my sony vaiocrap which has ssd)
[03:07] <arraybolt3> I had it set to not loop intentionally, which worked really well in my testing.
[03:07] <arraybolt3> But I think 8% may be too early to say "will finish soon" and then stay there :P
[03:08] <guiverc> i struggled to read the text on each window on that device, didn't worry as I assumed it'd repeat slideshow, but didn't...   I
[03:09] <guiverc> sorry; I'll install later today on dc7700 (old c2d box with spinning rust drive) & see it there too... 
[03:09] <arraybolt3> Yeah, I thought that would be a nice feature, but that sounds like it's actually a bug now. I'll set it to loop again.
[03:13] <guiverc> 8% was one box..  i5-9400u cpu (no idea how good/old that is; I don't like form factor of box so never cared to look)
=== arraybolt3_ is now known as arraybolt3
[03:15] <guiverc> the slideshow was really good though arraybolt3 
[03:19] <arraybolt3> Thanks! (I'm building a looping version now and will test in a bit, then upload if it's good.)
[03:34] <arraybolt3> https://launchpad.net/ubuntu/+source/calamares-settings-ubuntu/1:23.04.8
[05:16] <guiverc> fyi arraybolt3 , slideshow had completed at 7% on hp dc7700  (install progress)
[05:20] <guiverc> given UI freeze; do you want a bug report?  (8% on sony vaio?, 7% on old hp?)
[05:43] <lubot> [telegram] <Leokolb> My slideshow completed running in a VM
[05:45] <lubot> [telegram] <Leokolb> running another test on baremetal box @arraybolt3
[07:47] <lubot> [telegram] <teward001> bug report never hurts guiverc
[08:20] <guiverc> ack & thanks @teward001  (was out watering when heard ping; finished what I was doing.. ...)
[08:51] <guiverc> https://launchpad.net/bugs/2012041   (and added to iso tracker if helpful with likely SRU)
[08:51] -ubottu:#lubuntu-devel- Launchpad bug 2012041 in calamares (Ubuntu) "lubuntu lunar calamares slide show is very short" [Undecided, Confirmed]
[09:44] <lubot> [matrix] <kc2bez> It looks like Aaron's fix for that has made it to the release pocket based on my scrollback.
[11:17] <guiverc> :) 
[15:35] <arraybolt3_> It was in Lunar, so didn't need an SRU. And it was a bug (alright so I made it as a feature, but as bugs can be features, so features can also be bugs :P), so I just fixed it.
[15:39] <arraybolt3_> I had published a version that paused in the testing PPA, I believe, but I probably could have said it out rather than assuming the PPA would be tested and the change noticed. Sorry about that, I will try to avoid that next time.
=== arraybolt3_ is now known as arraybolt3
[16:02] <Eickmeyer> bug 2012041 #BlameArraybolt3
[16:02] -ubottu:#lubuntu-devel- Bug 2012041 in calamares (Ubuntu) "lubuntu lunar calamares slide show is very short" [Undecided, Fix Released] https://launchpad.net/bugs/2012041
[16:02] <Eickmeyer> XD
[16:04] <lubot> [matrix] <arraybolt3> lol, we had a meme for that once a long time ago, would have to hunt for it in the scrollback.
[16:05]  * arraybolt3 buries head back into race condition fixing
[16:11] <lubot> [telegram] <kc2bez> https://phab.lubuntu.me/macro/view/4/
[18:56] <tsimonq2> XD
[21:44] <lubot> [matrix] <kc2bez> We've missed you tsimonq2 I hope your travels are going well.