[02:00] <Eickmeyer> RikMills: Word of caution: Latest frameworks breaks ubiquity mid-install. We know this because when I was updating for the oem-install for kfocus the latest frameworks upload to kubuntu backports caused ubiquity to reproducibly crash when installing.
[02:00] <Eickmeyer> This could be an issue with Kinetic.
[02:05] <arraybolt3> Eickmeyer: Will test Kinetic ASAP and file a bug if needed.
[02:06] <arraybolt3> I don't have any Kinetic Kubuntu image yet, so it will take quite a while to download.
[02:16] <Eickmeyer> arraybolt3: I don't think Kinetic has it yet, but it will.
[02:17] <Eickmeyer> Created a headache for me today with the focus jammy OEM images.
[02:18] <arraybolt3> OK. I'll keep an eye out. (BTW, for anyone who's stuck without a Kinetic image but has a Jammy one, looks like zsync can morph the one into the other! Gonna find out how well it works.) Is there a way to make it happen in Jammy easily so we can get a bug report out ahead of time? Is that OK to do?
[02:18] <Eickmeyer> arraybolt3: ^ Yeah, that's how I get my Kinetic images when the new cycle starts. Pretty handy.
[02:19] <arraybolt3> Image was over halfway complete! Woot!
[02:19] <Eickmeyer> arraybolt3: As for getting a bug report ahead of time in Jammy, no. Needs to be done in Kinetic.
[02:20] <arraybolt3> If it's not in Kinetic yet, maybe I should wait. I'm fighting with a security vulnerability in Ubuntu, and almost have the bug report ready. (And yes, I am marking it as a vuln, so it's not going to go public until it's fixed or is determined to be not that big a deal by people more knowledgable than me.)
[02:21] <arraybolt3> OK, will be monitoring Kinetic and making a report once it's time.
[02:26] <Eickmeyer> arraybolt3: Basically, my goal is to figure out how frameworks 5.94 breaks ubiquity, figure out how it's fixed in ubiquity (because good luck fixing it in frameworks) and backporting that fix to jammy via SRU because then kfocus would benefit as the oem ISO image stays updated.
[02:29] <arraybolt3> Maybe a silly question, but how would one install the bad frameworks version into a live ISO and then get it to stick so that ubiquity can be run with the broken setup?
[02:30] <arraybolt3> Or is there a way to build an installer? Like, maybe install Kubuntu, install the bad frameworks version, then install ubiquity and put the necessary configs and image where it wants so the installer can be run from within a fully installed system?
[02:35] <Eickmeyer> Well, the frameworks isn't bad, per se, it's just ubiquity-kde is making a qt call that has been revised or something in kf5.
[02:35] <Eickmeyer> We'll figure it out eventually, it's just not urgent.
[02:36] <Eickmeyer> The new kf5 is in ppa:kubuntu-ppa/backports and ubiquity is... ubiquity.
[02:36] <Eickmeyer> Not useful for diagnosis unless it's installing a system though.
[02:36] <arraybolt3> Right, but don't you have to reboot in order to get the frameworks to kick in? And if you do that on a live ISO, doesn't that flush everything you just did?
[02:37] <arraybolt3> (I just want to reproduce the bug so I can help figure out why it's messing up Ubiquity.)
[02:38] <keithzg[m]> Wouldn't think a reboot would be necessary, absolute worst-case scenario I'd imagine restarting the display manager would do the trick
[02:38] <arraybolt3> keithzg[m]: Nice, didn't know that! Should be easy to reproduce the bug then.
[02:42] <keithzg[m]> Yeah, nearly only the kernel should ever *need* a restart for updates to take effect (and even then there are some ways to avoid needing to reboot), people tend to just restart because it's easier to do and remember than restarting specific components! Many a time I have `sudo service sddm stop` 'd and `start` 'd (or the system's equivalent) for one reason or another, out of stubbornness on my part or a problem's ;)
[02:44] <arraybolt3> keithzg[m]: Man, I usually reboot after every upgrade unless it's obviously not gonna need it. Is there some way to make systemctl restart everything that needs it? (OK, this is becoming support, so feel free to answer me in #kubuntu if that's better.)
[05:46] <RikMills> Eickmeyer: arraybolt3: kinetic has latest frameworks 5.94
[05:48] <RikMills> latest kinetic iso test installing.....
[05:51] <RikMills> successful intsall on kinetic. no crash
[06:02] <RikMills> keithzg[m]: easiest way is to change the iso boot line to boot to the rescue prompt. use systemctrl to enable networking. install ot make whatever change you want. then resume boot
[06:02] <RikMills> then you start graphical things as if the iso had the changes you made
[06:15] <arraybolt3> RikMills: Hmm. So maybe it's something specific to Jammy. I'm about to find out.
[06:19] <arraybolt3> (Just for anyone else here who's doing a lot of VM stuff, try gnome-boxes. I've been fighting with virt-manager for LONG, just gave Boxes a try and am instantly loving it.)
[06:42] <RikMills> packaging for the 5.25 beta tomorrow nearly done :D
[07:05] <arraybolt3> Confirmed - Kubuntu Kinetic works.
[07:47] <arraybolt3> RikMills: Eickmeyer: Crud. I can't even get the latest frameworks installed into Jammy to test it in a live session. It gets to something about kio (I don't remember if it was unpacking or setting up), then the desktop vanishes and I get a lot of interesting error messages on the console that appears.
[07:48] <RikMills> maybe not enough space
[07:49] <arraybolt3> It has like 1.5 GB free, and only wanted ~800 MB.
[07:49] <arraybolt3> (In the live session. I gave the VM 4 GB RAM.)
[07:49] <arraybolt3> I can read the error messages if that would be helpful.
[14:00] <Eickmeyer> Interesting. I wonder what broke it then.
[14:00] <Eickmeyer> Might be good news though, because that means it'll have to be fixed for 22.04.1 since it's independent of frameworks.
[14:04] <BluesKaj> Hi all