[06:29] <guiverc> beta release doc for kinetic/22.10 can be found at https://discourse.lubuntu.me/t/lubuntu-kinetic-kudu-22-10-beta-release/3640  for those that can access it  (sorry I've still been unable to login to notes.lubu)...   I'll re-read it later
[06:30] <guiverc> (ps:  if someone wants to read it & can't; I'll post a copy on gdoc)
[06:30]  * arraybolt3[m] is interested but can't read it
[06:31] <guiverc> ack & thanks arraybolt3[m] .. will provide link when I've copied it there
[06:33] <arraybolt3[m]> guiverc: Thanks!
[06:38] <guiverc> (it's mostly the 22.04 beta; only the "What's New" is unique  (and I probably need to change heading there)
[06:39] <guiverc> If you can think of more for "What's new" please feel free to suggest..  I really just link to upstream lxqt & calamares release docs
[06:40] <arraybolt3[m]> I seem to remember a new Featherpad too (will have to check to make sure), that's as much as I can remember.
[06:41] <guiverc> I've updated the testing checklist for kinetic; but its unpopulated as current iso.qa.ubu results are too old  (for obvious reasons)
[06:42] <arraybolt3[m]> Nice. I'm about to be in a great position to do some serious testing.
[06:44] <guiverc> (I like the idea of some entries in doc so people hopefully can understand better, also like it not-full, so people may be tempted to step in and help!)
[06:44] <guiverc> One thing I've not done is we need to release-upgrade with backports enabled too!  (checklist doesn't cope with that yet!)
[06:45]  * guiverc remembers a user question about backports-upgrades somewhere... when we have a populated answer in that we can (hopefully) answer that user in a way that will satisfy user..
[06:45] <arraybolt3[m]> Oy, that's a good one to do. Definitely let's add that. I've never done a do-release-upgrade before, so knowing how it works for an inexperienced user might be nice (e.g., let's see if I can do it :P)
[06:46] <guiverc> arraybolt3[m], if using a c2q-9400 with spinning rust drive; don't attempt it in a virtualbox VM.. last time I did that it took 17 (or 19) hours... and the box was horrific that whole time!
[06:47] <arraybolt3[m]> LOL I'll probably be doing it bare-metal on a modded Dell Chromebook 3120.
[06:47] <arraybolt3[m]> (I may also be doing stuff in VMs on a Kubuntu Focus XE in the not-to-distant future since I'm finally upgrading \o/)
[06:47] <arraybolt3[m]> s/to/too/
[06:48] <guiverc> yeah I choose to do bare-metal myself... even older slower hardware does better than a VM on a resource limited box
[06:48]  * guiverc admits though I've not done many release-upgrade QA tests in ages.. @Leokolb has done almost all of them
[06:50]  * guiverc realizes one reason I didn't like them was bandwidth-quota restrictions... my ISP is increasing monthly charge from Oct-22 :(  but my quota-limits won't exist anymore :)
[06:50] <arraybolt3[m]> Blah, what's with ISPs and craziness like that?
[06:51] <arraybolt3[m]> Though cool to hear that you'll be going unmetered now, I hope.
 I can continue to do the upgrades @guiverc  and yes I also prefer bare metal (re @lubuntu_bot: (irc) <guiverc> admits though I've not done many release-upgrade QA tests in ages.. @Leokolb has done almost all of them)
[06:54] <guiverc> I've had quota limits since first connected via broadband (not earlier dialup); so have been used to them (at home anyway)....  They introduced me to multiple-desktop installs though (my ISP allowed me to download Ubuntu ISOs quota free; so they were always what I installed for myself; then added the flavor desktop(s) I wanted)
[06:54] <guiverc> Thanks (as always) @Leokolb
[06:55] <arraybolt3[m]> guiverc: Oh that's a cool trick. (Also first time I've ever heard of an ISP allowing certain software to be downloaded without burning data, cool that they chose Ubuntu)
 And of course all are aware - we still having daily ISO build flavors- was advised it is being worked on...
[06:56] <guiverc> nah, they just happened to mirror certain software (listed on the official mirrors list of Ubuntu) & downloading from their own mirror was quota-free... it wasn't just ubuntu.
[06:56] <arraybolt3[m]> Oh, that makes sense.
[06:57] <guiverc> what I felt was cool though; as they also mirrored the archive.. download the official Ubuntu Desktop ISO, install quota-free... then switch to ISP's mirror & additional packages (inc. the flavor desktops) were quota free .. That I loved.
[06:58] <arraybolt3[m]> Hah, so infinite free software and updates. That's where a ton of our data goes, sounds like a nice way to make limited bandwidth sting less.
[06:59] <guiverc> They only seemed to do it for a few OSes (open source).. so it made me happy.
[07:06] <guiverc> TUI & GUI release-upgrade with backports added to checklist
 👍 (re @lubuntu_bot: (irc) <guiverc> TUI & GUI release-upgrade with backports added to checklist)
 Will hold off testing Kinetic - awaiting new ISO
 Finally success - Lubuntu Kinetic daily build!
[16:31] <arraybolt3> Are there any critical "this needs to be worked on" things we know of in Lubuntu Kinetic that I can try to push through before release? I'm thinking maybe the wonky theming on Calamares could use some help, and obviously we need to test a bunch. I also remember a bug report about a brightness key regression that I should look into.
[16:32] <arraybolt3[m]> Also if there's still packaging work that needs done and it's not too late, I'm finally free to do that.
[16:34] <arraybolt3[m]> (And I've not lost track of the Debian work, just fyi.)
[16:38] <arraybolt3[m]> Just finished a BTRFS installation of the latest Kinetic ISO, and it gives me a GRUB boot screen when the installed system first boots (though the system boots just fine after that). Is that expected behavior?
[16:38] <arraybolt3[m]> Oh shoot, Firefox is missing.
 strange...just installed todays Kinetic in efi+secure - all good (re @lubuntu_bot: (irc) <arraybolt3[m]> Oh shoot, Firefox is missing.)
[16:39] <arraybolt3[m]> Hmph, I rebooted and now it appears.
[16:39] <arraybolt3[m]> I bet it's this bug again: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246/43
 will keep eyes open — running sevral installs this evening and in the am (re @lubuntu_bot: (irc) <arraybolt3[m]> Hmph, I rebooted and now it appears.)
[16:40] <arraybolt3[m]> OK. It was a BTRFS installation FWIW.
 Got it - will check this - see if you can reproduce it - maybe another install VM? (re @lubuntu_bot: (irc) <arraybolt3[m]> OK. It was a BTRFS installation FWIW.)
[16:41] <arraybolt3[m]> Easy.
[16:41] <arraybolt3[m]> Also the VM used UEFI+Secure Boot.
 Will run a btrfs install in about 10 min..
[16:44] <arraybolt3[m]> Made a note of the incident on the linked Discourse thread. I figure if we just keep documenting everything we know about this mystery eventually something will click (hopefully).
 Got this on install - just now - think we need new bug report —am rerunning the install (re @lubuntu_bot: (irc) <arraybolt3[m]> OK. It was a BTRFS installation FWIW.)
[17:01] <arraybolt3[m]> @Leokolb: So it happened for you also?
[17:01] <arraybolt3[m]> Yep, I see it did. I'm finishing my second installation over here.
 Yes ..and just noticed when I boot the USB install media -NO Firefox on application menu - same after installing but on reboot it pops in.I will file bug report on the live media for starters (re @lubuntu_bot: (irc) <arraybolt3[m]> @Leokolb: So it happened for you also?)
[17:02] <arraybolt3[m]> Just happened again for me. This looks fully reproducible. Sigh. That's... good, I guess? And really bad.
 Well the past few days build failures were all involving Firefox snap - so not surprised (re @lubuntu_bot: (irc) <arraybolt3[m]> Just happened again for me. This looks fully reproducible. Sigh. That's... good, I guess? And really bad.)
[17:03] <arraybolt3[m]> Also, just now, when I finished the installation, trying to run firefox from the terminal gave me a command-not-found message recommending that I use apt to install Firefox.
[17:03] <arraybolt3[m]> lubot: I hope that's all it is.
[17:04] <arraybolt3[m]> Thankfully after that first reboot, Firefox starts right up.
 Will file bug and you might add comment? (re @lubuntu_bot: (irc) <arraybolt3[m]> Thankfully after that first reboot, Firefox starts right up.)
[17:05] <arraybolt3[m]> Another weird thing, it used to be that the cursor was different when you hovered over Firefox than when you were in the rest of the system, but it wasn't all that noticable. Now the different cursor looks like it's straight out of a bare X server.
[17:05] <arraybolt3[m]> lubot: Sounds good.
 Hang on...waited 5 min and Firefox appeared in the application menu - will reboot the live media and double check (re @lubuntu_bot: (irc) <arraybolt3[m]> Another weird thing, it used to be that the cursor was different when you hovered over Firefox than when you were in the rest of the system, but it wasn't all that noticable. Now the different cursor looks like it's straight out of a bare X server.)
[17:07] <arraybolt3[m]> I'll also try a normal ext4 installation and see what happens there.
[17:08] <arraybolt3[m]> Since we're this close to Beta Freeze, should I bring this up in u-release?
[17:10] <arraybolt3[m]> (Er, not close to Beta Freeze, but in Beta Freeze.)
 I am testting on ext4 and again - if I wait 2 or 3 min Firefox appears on the app menu.. (re @lubuntu_bot: (irc) <arraybolt3[m]> I'll also try a normal ext4 installation and see what happens there.)
[17:11] <arraybolt3[m]> I did confirm that once it shows up, Firefox works just fine (was able to stream music on YouTube without trouble, though the anomaly with the cursor is bugging me).
[17:15] <arraybolt3[m]> Just noticed something interesting - snapd consumes a lot of CPU power during the period after first booting the ISO.
[17:15] <arraybolt3[m]> Once it stops consuming CPU, that's when Firefox appears to show up.
 Yes - here is what I see - boot live media - no Firefox - wait one to two min and the lxqt display monitor pops up in upper right hand corner as normal ..after a few seconds/min Firefox also appears in the app menu . (re @lubuntu_bot: (irc) <arraybolt3[m]> I did confirm that once it shows up, Firefox works just fine (was able to stream music on YouTube without trouble, though the anomaly with the cursor is bugging me).)
 Right on ..now creating bug report ..will fwd info (re @lubuntu_bot: (irc) <arraybolt3[m]> Once it stops consuming CPU, that's when Firefox appears to show up.)
[17:18] <arraybolt3[m]> What in the world... so first an "ld-2.23.so" process is hogging TONS of CPU power right after booting the ISO. AppArmor also chews up a bunch out of nowhere, and snapd does quite a bit. I'll have to monitor that behavior more closely, but as soon as the CPU hogging mess stops, then Firefox appears in the menu.
[17:19] <arraybolt3[m]> (I think snapd starts hogging before ld-2.23.so, and the ld-2.23.so is within a snap it looks like. OK, I should be putting this in the bug report comment and not just flooding the channel, but if nothing else, now I'll have some notes to go on.)
[17:19]  * arraybolt3[m] has to use the restroom, will come back and make comment on bug report when I get back
 Will you file the bug? (re @lubuntu_bot: (irc) <arraybolt3[m]> has to use the restroom, will come back and make comment on bug report when I get back)
[17:43] <arraybolt3[m]> OK, back.
[17:43] <arraybolt3[m]> Yeah, sure, if you'd like me to.
 I am sending it right now (re @lubuntu_bot: (irc) <arraybolt3[m]> Yeah, sure, if you'd like me to.)
[17:44] <arraybolt3[m]> Oh, OK.
 Bug 1991011- file under lxqt-session (was not sure where to file) please feel free to amend or whatever needs to be done (re @lubuntu_bot: (irc) <arraybolt3[m]> Oh, OK.)
[17:49] <arraybolt3[m]> Nice. From all appearances it looked like a snapd bug to me due to diagnostic data, so if you don't mind I'll change it to that.
 👌
[18:10] <arraybolt3[m]> @Leokolb: I brought this up in u-release, it looks like this might be the result of Snaps not being preseeded. It's not normal behavior but currently it is expected, so this might not be the total mess I thought it was.
 tks info - (re @lubuntu_bot: (irc) <arraybolt3[m]> @Leokolb: I brought this up in u-release, it looks like this might be the result of Snaps not being preseeded. It's not normal behavior but currently it is expected, so this might not be the total mess I thought it was.)
 Another new ISO build 27092022.3 same issue as expected.. (re @lubuntu_bot: (irc) <arraybolt3[m]> @Leokolb: I brought this up in u-release, it looks like this might be the result of Snaps not being preseeded. It's not normal behavior but currently it is expected, so this might not be the total mess I thought it was.)
[19:12] <arraybolt3[m]> Yep, did the same for me over here.
[21:12] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Kinetic Beta] (20220927.4) has been added
[22:24] <guiverc> :)  20220927.4   (bdmurray was successful I take it)
[22:28]  * guiverc notices I got lots of ^ to read to catch up  (as I ZZZZd)
[22:43] <guiverc> thanks arraybolt3 @Leokolb