[00:30] <kc2bez[m]> https://launchpad.net/ubuntu/+source/lubuntu-artwork/22.10.1
[00:30] <kc2bez[m]> I think I am done for today.
[00:31] <kc2bez[m]> Will test some stuff and make adjustments tomorrow.
[02:28] <arraybolt3[m]> Wow, looks like I missed quite a bit over the weekend. Just read through the backlog, I guess I should start going through the Calamares testcases.
[02:50] <kc2bez[m]> I haven't been able to get an EFI install to work.
[02:50] <kc2bez[m]> legacy works fine
[02:50] <arraybolt3[m]> OK, I'll debug it.
[03:39] <arraybolt3[m]> Well total shocker here, but nothing's getting written to the EFI directory! 🤯
[03:40] <arraybolt3[m]> I'm smelling something amiss with our device mount
[03:40] <arraybolt3[m]> mounts, what about you?
[03:41] <kc2bez[m]> Yeah, could be. Pretty important to write to the EFI directory.
[03:42] <arraybolt3[m]> Also found an interesting "WARNING: [PYTHON JOB]: "EFI system, and no bootloader is set." in the logs, apparently right in the bootloader job spot.
[03:42] <kc2bez[m]> Hmm, wonder what changes have been made in bootloader 
[03:43] <arraybolt3[m]> Looking at it right now, maybe they made EFI bootloaders more configurable?
[03:45] <tsimonq2> I do remember we had to manually copy some code over via a shellprocess
[03:45] <arraybolt3[m]> I don't see anything suspicious in the changes to bootloader.conf...
[03:46] <kc2bez[m]> We used to do some hacky stuff but that got implemented a while ago.
[03:48] <arraybolt3[m]> I got an idea, hold on one sec...
[03:48] <arraybolt3[m]> I'm gonna chroot into the installed system with everything mounted right and see if installing the bootloader packages makes everything go good.
[03:53] <arraybolt3[m]> I see some of the hacky stuff, I'm wondering if maybe it could be averted by just adding shim-signed and grub-efi-amd64-signed into packages.conf? Though we would have to implement the packages.conf fix in mount.conf, but that would be a piece of cake.
[03:55] <kc2bez[m]> I'm going to chroot into a dream and look around there for a bit. See y'all in the morning.
[03:55] <arraybolt3[m]> Dan Simmons: OK, c ya!
[03:55] <guiverc> :)
[03:56] <arraybolt3[m]> Simon Quigley guiverc: I chrooted in and did "grub-install" and BAM that wrote everything into EFI. So somehow grub-install isn't getting executed correctly?
[03:56]  * guiverc has ubuntu-news hat on, so only reading/replying on rare occasion
[03:57] <arraybolt3[m]> Ugh, but now I just got GRUB rescue... 😞
[04:00] <arraybolt3[m]> OK, bit of GRUB-fu and BusyBox boxing and I'm in the system, but I guess really the question is, what GRUB command should be executed, and why isn't it getting run?
[04:06] <arraybolt3[m]> libcalamares.globalstorage.value("bootLoader") This is getting set to None somehow, as evidenced by src/modules/bootloader/main.py line 801.
[04:11] <arraybolt3[m]> I think this is a Calamares bug, I'll file it and see what happens. I don't see anything that's wrong in our config.
[04:41] <arraybolt3[m]> https://github.com/calamares/calamares/issues/1990
[04:55] <guiverc> thanks for chasing up arraybolt3[m] & filing upstream.. 
[14:05] <tsimonq2> Good morning :)
[14:06] <kc2bez[m]> 👋
[14:08] <kc2bez[m]> I think we might need another cala snapshot. I don't see anything that would fix the EFI install problem though.
[14:08] <kc2bez[m]> So maybe we should wait 
[16:00]  * Eickmeyer blames RikMills
 *blames Simon because its always Simon's fault*
[16:11] <kc2bez[m]> https://phab.lubuntu.me/macro/view/4/
[16:42]  * tsimonq2 libqtxdg -> backports-staging
[16:49] <tsimonq2> TODO low hanging fruit - import calamares changes pushed to archive into Git
[16:55] <kc2bez[m]> Gah! 
[16:55]  * kc2bez[m] brings you today's hur dur moment.
[16:55] <tsimonq2> yeah?
[16:55] <kc2bez[m]> I never synced default settings before I started.
[16:56] <kc2bez[m]> I'll fix.
[16:56] <tsimonq2> Thanks!
[17:37] <kc2bez[m]> This should be better https://launchpad.net/ubuntu/+source/lubuntu-default-settings/22.10.2
[17:38] <kc2bez[m]> I think I have git fixed up too.
[19:38] <arraybolt3[m]> Making progress on the EFI install bug, I've got some testing to do, but it looks hopeful.
[20:16] <tsimonq2> Calamares and settings both are publishing at the moment
[20:20] <tsimonq2> I'm going to wait until it says 15 minutes even on the publish page before I rebuild the ISO
[20:25] <arraybolt3[m]> Quick question: is the deploycala.py script good for testing the latest commits?
[20:29] <arraybolt3[m]> Also, what happened to the Lubuntu wallpaper contest? Is it that time already? I see the wallpaper changed.
[20:29] <arraybolt3[m]> (It's a good one, too.)
 "Quick question: is the deploycal..." <- Never used it.
[20:31] <kc2bez[m]> arraybolt3[m]: Nope still running, I added that as a placeholder so I can keep track of what VM I am working in ;) 
[20:31] <arraybolt3[m]> Well, trying the script, we'll see what happens.
[20:32] <arraybolt3[m]> (I can't find the wallpaper contest post on Discourse anymore.)
[20:32] <arraybolt3[m]> Oh wait, founsd it.
[20:32] <arraybolt3[m]> s/founsd/found
[20:33] <kc2bez[m]> https://discourse.lubuntu.me/t/lubuntu-kinetic-kudu-22-10-artwork-contest/3358?u=kc2bez
[20:33] <arraybolt3[m]> Dan Simmons: I think you should submit your placeholder, it looks really cool.
[20:33] <tsimonq2> Also, hey everyone, I'm still going to be in Charlotte for approximately the next 24 hours. Unfortunately everyone has basically packed up and left (Noah is on his way to the airport), so I'll likely be doing a substantial amount of work before I leave (read: out of town so completely uninterrupted). If there's anything in particular that we need focus on, please ping.
[20:33] <kc2bez[m]> arraybolt3[m]: It isn't mine, I grabbed it from unsplash
[20:34] <kc2bez[m]> I will keep it on there and just change the default 
[20:34] <arraybolt3[m]> (<rant>I hate apt-get, why do tools have to use apt-get rather than apt where you can actually see download progress?</rant>)
[20:35] <kc2bez[m]> tsimonq2: Ping ;) 
[20:35] <kc2bez[m]> I had a crazy thought, feel free to shoot me down.
[20:36] <kc2bez[m]> Why don't we move all of our git stuff to LP? 
[20:36] <kc2bez[m]> It seems to work well for calamares-settings-ubuntu and calamares
[20:36] <arraybolt3[m]> Git stuff... you mean like Phabricator?
[20:36] <kc2bez[m]> Yes
[20:37] <tsimonq2> kc2bez[m]: We migrated off of LP in the first place due to some of its clunkyness. I would still like to give Gittea a try
[20:37] <tsimonq2> +0
[20:38] <kc2bez[m]> Fair enough 
[20:38] <kc2bez[m]> I said you could shoot me down 
[20:38] <kc2bez[m]> I loathe github though 
[20:38] <tsimonq2> kc2bez[m]: Don't ever let that discourage you from bringing ideas to the table in the future :) I know it goes without saying but just because I shoot something down doesn't mean it won't be an option to consider in the future
[20:38] <tsimonq2> kc2bez[m]: GitHub yeah, GitTea is a different storyt
[20:39] <tsimonq2> s/storyt/story/
[20:39] <arraybolt3[m]> As long as we still have GitHub no matter what solution we're using, or something as easy to use as GitHub, I;m happy.
[20:39] <arraybolt3[m]> tsimonq2: They look the same to me?
[20:39] <tsimonq2> arraybolt3[m]: Basically in the past we've just mirrored them
[20:39] <tsimonq2> So the idea is you can create an MR/PR anywhere
[20:40] <tsimonq2> arraybolt3[m]: The latter is FOSS, the former absolutely is not
[20:40] <kc2bez[m]> tsimonq2: I won't. I don't want to totally go against the grain. I value your past experiences there, mine are somewhat limited. 
[20:41] <tsimonq2> kc2bez[m]: You also have about a decade of life experience over me... you're 30 right? ;)
[20:41] <arraybolt3[m]> tsimonq2: True, but for me, as long as it doesn't mess with my source code and isn't running on my computer, I'm happy with non-FOSS. And depending on the company, I'll do non-FOSS on my system (drivers mainly).
[20:41] <arraybolt3[m]> (But I do prefer FOSS over non-FOSS.)
[20:41] <kc2bez[m]> tsimonq2: Yeah, something like that ;) 
[20:41] <tsimonq2> arraybolt3[m]: I respect that decision entirely but as a project we need to run on FOSS I'd say
[20:42] <kc2bez[m]> 44 cycles around the orb for me.
[20:42] <arraybolt3[m]> I guess GiTea is FOSS GitHub, so that should be good. If I can still git clone and git push seemlessly, then I'm happy.
[20:42] <kc2bez[m]> Codeberg is a good example of gittea
[20:42] <kc2bez[m]> In the wild
[20:43] <arraybolt3[m]> Oh that looks nice. If Git commands work, I can easily see myself moving to that.
[20:44] <kc2bez[m]> All the same git-fu should work.
[20:45] <tsimonq2> Just remember that Git is distributed and scalable. Git works the same basically no matter which interface you are working with.
[20:46] <arraybolt3[m]> Oh my gosh I just built the newest calamares on a BIOS VM... 🤦‍♂
[20:46] <arraybolt3[m]> (Why did Chrome OS send two emojis instead of one male emoji?)
[20:46] <kc2bez[m]> Fun fact. The concept of git remotes came after git had been in use for quite a while.
[20:46] <arraybolt3[m]> OK, so there went that cpu power.
[20:49] <arraybolt3[m]> OK, starting from scratch.
[20:49] <kc2bez[m]> It was a good learning experience.
[20:49] <arraybolt3[m]> No, wreong reaction
[20:49] <kc2bez[m]> So the deploy script works? 
[20:50] <arraybolt3[m]> There, righ reaction.
[20:50] <arraybolt3[m]> Yep, deploy script works
[20:50] <kc2bez[m]> Good to know 
[20:50] <arraybolt3[m]> (Turns out the kiss emoji is right under the melting face emoji... ?!?)
[20:50] <arraybolt3[m]> (Note to self - don't do Matrix reactions on a touchscreen laptop.)
[20:50] <arraybolt3[m]> (With the touchscreen.)
[20:58] <tsimonq2> Rebuilding the ISO now. Should grab the new Calamares + settings.
[21:05] <arraybolt3[m]> Testing a bleeding-edge build of Calamares right now.
[21:05] <arraybolt3[m]> EFI installation.
[21:09] <arraybolt3[m]> OK, calamares-logs-helper just went crazy, trying to copy from "/root/.cashe/calamares/sessions.log", dunno why that happened, but I think that's late enough in the installation that I should be able to see if the EFI bug is happening.
[21:09] <arraybolt3[m]> Nope, no EFI contents.
[21:11] <kc2bez[m]> Yeah, I changed the desktop file to use pkexec so essentially it runs as root thus why it is trying to copy the log file from /root
[21:11] <arraybolt3[m]> But I ran it from the terminal.
[21:13] <arraybolt3[m]> Great, I just accidentally chucked the whole VM with Alt+F4 (raw QEMU doesn't like that). I guess I'll wait for the ISO to rebuild.
[21:13] <kc2bez[m]> Right but unless you executed `pkexec calamares` it won't match the settings, the log file will be in the wrong place 
[21:14] <arraybolt3[m]> Oh OK, that makes sense.
[21:14] <arraybolt3[m]> So the desktop file works now?
[21:14] <kc2bez[m]> In the latest iteration it should.
[21:16] <kc2bez[m]> I think we are up to 22.10.5 now
[21:17] <kc2bez[m]> We still need to figure out what happened to all the theming and get that back on track too.
[21:17] <arraybolt3[m]> The very newest Calamares gave us our "Welcome to the next universe" screen back, though it was squished in a somewhat odd way. So that's progress!
[21:17] <kc2bez[m]> Indeed 
[21:21] <arraybolt3[m]> Looks like the new ISO just hit the QA tracker!
[21:24] <tsimonq2> Very nice. Please confirm it has the new versions :)
[21:24] <arraybolt3[m]> Will do. Will just "apt-cache show calamares" do the trick? (And also for calamares-settings-ubuntu)
[21:28] <tsimonq2> `apt list --installed | grep calamares` is a more concise output imo but whatever floats your boat, doesn't matter too much :)
[21:32] <arraybolt3[m]> Hey, another crazy idea for y'all - do we want to make multibooting easy again, by overriding the disabled osprober? That might earn us some good attention, just like the possible switch to Falkon (which I still haven't started testing, I have got to do that).
[21:34] <arraybolt3[m]> OK, new ISO. I tried to use the desktop Calamares shortcut, and just got "Invalid desktop entry file: '/home/lubuntu/Desktop/lubuntu-calamares.desktop'".
[21:35] <kc2bez[m]> that sounds like it has 22.10.4
[21:35] <arraybolt3[m]> Simon Quigley: Calamares version: 22.10.4m.
[21:35] <arraybolt3[m]> Minus the m, not sure how that happened.
[21:35] <arraybolt3[m]> s/not sure how that happened/typo
[21:36] <kc2bez[m]> some bobo head typo'd the exec line in 22.10.4 which is why  you need .5
[21:36] <arraybolt3[m]> ,calamares-settings-lubuntu version is the same.
[21:36] <arraybolt3[m]> Dan Simmons: Hey, don't beat yourself up. Remember my post about how I dpkg -i'd in an office suite once?
[21:36] <kc2bez[m]> Nah, it is all good
[21:37] <arraybolt3[m]> Is 22.10.5 in the repos or in proposed?
[21:37] <arraybolt3[m]> I guess I'll find out soon enough.
[21:37] <arraybolt3[m]> Nevermind.
[21:37] <kc2bez[m]> There is a `"` at the end of the exec line in the .4 version, remove that and you should be good.
[21:37] <arraybolt3[m]> Oh OK.
[21:38] <kc2bez[m]> But yeah, both of those show to be in -release for like an hour now.
[21:38] <arraybolt3[m]> Hey, nice! But sadly this isn't the latest Calamares with all the new commits, so for my testing I can't use this version.
[21:38] <arraybolt3[m]> (Also, using pkexec made the UI ugly.)
[21:38] <kc2bez[m]> I guess it hasn't hit all the mirrors?
[21:38] <kc2bez[m]> Hmm
[21:38] <kc2bez[m]> great
[21:39] <arraybolt3[m]> OK, installing the new Calamares from -release.
[21:39] <tsimonq2> Another rebuild? :D
[21:39] <kc2bez[m]> They are cheap right?
[21:40] <arraybolt3[m]> OK, well the Calamares version is NOT 22.10.5, it's 3.3.0~git<insert big long number here>-0ubuntu1.
[21:40] <tsimonq2> kc2bez[m]: Last I checked we're nowhere near capacity.
[21:40] <arraybolt3[m]> After installing Calamares from -release.
[21:40] <tsimonq2> I don't necessarily think they're cheap on the builders, but we're also an official flavor with needs :P
[21:40] <kc2bez[m]> arraybolt3[m]: should be a date code
[21:40] <arraybolt3[m]> The number is 20220610.
[21:40] <tsimonq2> arraybolt3[m]: The big long number is a date. YYYYMMDD
[21:41] <arraybolt3[m]> So 3.3.0~git20220610-0ubuntu1.
[21:41] <arraybolt3[m]> (I thought maybe it was a commit ID or something LOL)
[21:41] <kc2bez[m]> That is the date of the git snapshot
[21:41] <kc2bez[m]> You can use git hash too
[21:41] <tsimonq2> Pop quiz for arraybolt3 @arraybolt3:matrix.org - why the tilde? :)
[21:42] <tsimonq2> kc2bez[m]: Doesn't increment as well
[21:42] <arraybolt3[m]> But yeah, using pkexec made it so that the nice Lubuntu UI feel isn't showing up in Calamares. Using the terminal workaround with "sudo -E bash; export $(dbus-launch); calamares -D6" made it look nice. 
[21:42] <arraybolt3[m]> tsimonq2: 'Cause tildes are for strikethroughs, and we hate Git snapshots! jk, I have no idea.
[21:42] <kc2bez[m]> tsimonq2: yup, i was just mentioning
[21:43] <tsimonq2> arraybolt3[m]: 3.3.0~ means "before 3.3.0". If we had commits on top of 3.3.0, it would be 3.3.0+
[21:43] <arraybolt3[m]> tsimonq2: Nice, good to know! (I'd better stop replying to this thread, we're probably flooding the sap out of Libera right now.)
[21:44] <kc2bez[m]> arraybolt3[m]: We need to work on that.
[21:44] <arraybolt3[m]> (I guess everyone here is using Matrix though, so it doesn't matter too much.)
[21:44] <arraybolt3[m]> Can we just revert the change that made pkexec work, then make a script that launches Calamares with the nice UI? Or is that a hacky fix for a real change?
[21:45] <arraybolt3[m]> s/real change/in place of a good solution
[21:46] <kc2bez[m]> arraybolt3[m]: pkexec is the intended upstream way to launch it. You don't have to do that hacky dbus export stuff.
[21:47] <kc2bez[m]> `sudo -E` uses the current users environment which is why it looks different.
[21:47] <kc2bez[m]> it is also why it is necessary to export the dbus-launch part
[21:48] <arraybolt3[m]> From the pkexec man page: "The environment that PROGRAM will run it, will be set to a minimal known and safe environment in order to avoid injecting code through LD_LIBRARY_PATH or similar mechanisms. In addition the PKEXEC_UID environment variable is set to the user id of the process invoking pkexec. As a result, pkexec will not allow you to run X11 applications as another user since the $DISPLAY and $XAUTHORITY environment
[21:48] <arraybolt3[m]> variables are not set. These two variables will be retained if the org.freedesktop.policykit.exec.allow_gui annotation on an action is set to a nonempty value; this is discouraged, thoughm and should only be used for legacy programs.
[21:48] <arraybolt3[m]> The bit about "minimal known and safe environment" might be the problem?
[21:50] <kc2bez[m]> It is a good thing, bad thing. It makes it look bad but work well ;)