[00:04] <arraybolt3> I see both bugs and may be able to help debug. If we just found a real Openbox bug that would be pretty interesting, given that it's been mostly unchanged for, what, 13 years?
[01:25] <arraybolt3> Umm... Firefox has gone GNOME on us in the latest Lunar ISO.
[01:26] <arraybolt3> https://i.imgur.com/YGETP90.png
[01:26] <arraybolt3> The title bar is all wonky.
[01:33] <teward> any chance the fact that Firefox is now a snap on every flavor has something to do with it?
[01:33] <guiverc> teward, all having snap'd firefox isn't new; been that way since jammy
[01:33] <teward> ye but weird things happen with snaps from release to release :P
[01:35] <guiverc> there is i suspect a recent change... having issues with firefox on box to my left..
[01:35] <guiverc> box to my left just had openbox crash....   (one I reported didn't have issue before..)
[01:37] <guiverc> that box had qterminal only in F11; not a snap package
[01:39] <arraybolt3> Just did a test installation. The fact that possibly Snap-related Openbox crashes and Firefox weirdness with the theming are happening at the same time, that doesn't feel like a coincidence.
[01:39] <arraybolt3> (btw we need some sort of "Express Installation" coolness like what exists for Windows and Ubuntu Desktop to be a thing for Lubuntu too :P)
[01:40]  * guiverc concurs given issues on box to my left.. no issues on this (my primary) box outside of openbox here though
[01:48] <arraybolt3> Oddly the list of preinstalled snaps on the latest Lubuntu Lunar exactly matches the list on a Kubuntu Jammy installation.
[01:49] <arraybolt3> I guess I'm going to start by reporting the Firefox bug and we'll see what happens from there.
[02:05] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2011758
[02:05] -ubottu:#lubuntu-devel- Launchpad bug 2011758 in snapd (Ubuntu) "Firefox is ignoring Lubuntu's theme settings entirely" [Undecided, New]
[09:37] <arraybolt3> @kc2bez: Right, but up until just recently, the title bar still looked Lubuntu-y. Now it looks... not.
[09:38] <arraybolt3> Chromium looks right. VSCode looks right. Firefox is the only offender.
[09:41] <arraybolt3> It's frustrating that this had to happen *after* User Interface Freeze, otherwise we might have been able to try and make a Snap to fix it possibly.
[09:41] <arraybolt3> But whatever. There's a bug filed, hopefully it will get input. If nothing else we'll live with a weird Firefox this cycle.
[17:56] <Eickmeyer[m]> FWIW, UIF hasn't actualy taken place yet (email was premature). Furthermore, freezes don't apply to bugs.
[17:58] <Eickmeyer[m]> Best way to make Firefox integrate well is to make sure there's an equivalent theme in the gtk-common-themes snap.
[17:59] <Eickmeyer[m]> Firefox needs it anyway, so no sense in being anti-gtk on this one.
[18:11] <arraybolt3> Eickmeyer[m]: I thought UIF was yesterday according to the timeline?
[18:11] <arraybolt3> Er, no, today. https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 But still, yeah we could try and help fix it.
[18:12] <Eickmeyer[m]> Freezes don't actually take place until an email is sent out. This one is an exception because it was premature.
[18:12] <arraybolt3> Huh. Will file that mentally for future reference.
[18:13] <Eickmeyer[m]> See discussion in #ubuntu-devel and on ubuntu-devel@ ML.
[18:14] <arraybolt3> Jjust saw it.
[18:19] <arraybolt3> Anyway, I might be able to work on that later, but for now I'm mostly concerned with Openbox weirdness. Gonna do some debugging and hopefully report on our private bug with results.
[18:36] <arraybolt3> This is weird, but it looks like the last calamares-settings-ubuntu upload isn't being grabbed?
[18:37] <arraybolt3> 23.04.5 is on the ISO, 23.04.7 is in LP and published. Hmm.
[18:37] <arraybolt3> Probably will pass with time then. If it's still not getting pulled in tomorrow, I'll look more closely.
[18:38] <arraybolt3> Ah, I see it, the daily images aren't building. I think that's what Eickmeyer was pointing out in -flavors.
[18:39] <arraybolt3> er, no, that was RikMills.
[18:39]  * arraybolt3 gets confused, then takes a detour to fix our ISO not building
[18:39] <Eickmeyer> Yeah, it was Rik. All flavors need to update that. However, having that other snap seeded probably isn't a bad idea for theming reasons.
[18:40] <Eickmeyer> But, the ISOs not building was another issue too (two issues, really).
[18:40] <Eickmeyer> vorlon fixed that last one.
[18:41] <arraybolt3> If that has a theming effect, this may be the way to fix our Firefox weirdness.
[18:41] <arraybolt3> OK, I'll update the seed and meta, then hopefully respin the ISO once the meta publishes.
[18:42] <Eickmeyer> Do you set a gtk theme anywhere at all?
[18:42] <arraybolt3> I have no clue :P
[18:59] <arraybolt3> And down the rabbit hole I go :P now I have to install and set up LXD in order to get a Lunar container to use for updating the lubuntu-meta package :P
[18:59] <arraybolt3> Anyway, seed updated.
[19:28] <Eickmeyer> vorlon just got the seeds building again, he forgor something last night.
[19:32] <arraybolt3> Nice, then hopefully the update I'm running now will work.
[19:35] <arraybolt3> lol, I just realized I'm trying to update a metapackage when the seed change I made was a snap. Well, hey, there were some changes to the metepackage anyway so I guess it was overall positive.
[19:37] <arraybolt3> Anyway, I guess I'll keep an eye on the seed in ubuntu-archive-team.ubuntu.com and then respin once that's updated.
[19:37] <Eickmeyer> Yeah, you don't need to update the metas if you change a snap in the seed.
[19:38] <arraybolt3> When I ran the update script, it did pull in some things related to riscv64 and armhf. Since there are things to be updated, I'm thinking about pushing it, but I'm not sure if that would violate Feature Freeze?
[19:39] <arraybolt3> Stuff like "Added libreoffice-writer to desktop-recommends [riscv64]" and "Removed fwupd-signed from desktop-recommends [armhf]".
[19:39] <Eickmeyer> No, it wouldn't. That's perfectly fine to do, means there were changes made. Changes aren't necessarily features.
[19:40] <arraybolt3> Makes sense. And I guess having LibreOffice present on riscv64 now is a good thing (if there is anyone out there who actually installs lubuntu-desktop on their riscv64 boards).
[19:41] <Eickmeyer> Dependencies getting refreshed and stuff getting updated in metas doesn't mean you've added a new feature, it just means changes were made that make changes in the metas.
[19:41] <arraybolt3> +1
[21:42] <arraybolt3> OK, the seed change happened, I *think* I just triggered a rebuild though I'm not entirely sure :P so we'll find out.
[21:45] <arraybolt3> Uh... actually...
[21:45] <arraybolt3> Eickmeyer: How on earth do you request a rebuild of an ISO? I'm looking at the admin page on the ISO tracker and see a bunch of scary buttons that it looks like I probably shouldn't press.
[21:46] <arraybolt3> I *think* I'm supposed to click the Builds tab, check the Lubuntu Desktop amd64 box, enter a version number of 20230314.1, and then click "Add these builds to the tracker", but I don't know if that's right.
[21:47] <RikMills> you don't do that!
[21:47] <arraybolt3> Well good thing I didn't do it :D
[21:47] <RikMills> go to http://iso.qa.ubuntu.com/qatracker/milestones/441/builds
[21:48] <arraybolt3> Yeah, I see it
[21:48] <RikMills> tick the checkbox next to the lubuntu amd64 build item
[21:48] <arraybolt3> Ohhhhhh. I didn't even notice those checkboxes :P
[21:48] <arraybolt3> And *then* use "Request a rebuild"?
[21:48] <RikMills> then use the menu at the bottom of the page to request a rebuild
[21:49] <RikMills> yep
 ooh i see that too xD
 nice
 *bonks arraybolt3 for no reason*
[21:49] <arraybolt3> Got it. The first thing I did was use the button expecting that it would ask me what ISO to rebuild, and then I stared at the page in confusion when it appeared to do nothing...
[21:49] <arraybolt3> (The button at the bottom of the screen for requesting rebuilds)
[21:50] <arraybolt3> There, that did what I hoped.
[21:50] <arraybolt3> RikMills: Thank you!
[21:50] <RikMills> I am not sure if lubuntu-dev will give you perms though
[21:50] <arraybolt3> I'm in Lubuntu Council, and therefore also in lubuntu-product-managers, so it let me do it.
[21:51] <RikMills> arraybolt3: ah yes. says 'rebuilding' next to the lubuntu entry now
[21:51] <arraybolt3> (I figure a rebuild to test a fix for a totally broken ISO is a good thing.)
[21:52] <arraybolt3> Thanks for bailing me out of that, I felt like I was holding a loaded gun and had no clue where the safety was, how to fire it, or what it was pointed at XD thus why I asked for help
[21:54] <RikMills> there is one quirk with this though. if the livefs fails on a build retriggered by this, then often requesting another one will not work until after the build from the normal cron job has run again
[21:55] <arraybolt3> Oh, weird. So basically, if the cron job fails, I get one shot, and if that fails I have to wait till tomorrow for it to actually work?
[21:55] <Eickmeyer> I'm able to request a rebuild as a result of being in ~edubuntu-release and ~ubuntustudio-release, but only for those images.
[21:55] <Eickmeyer> arraybolt3: That's correct, but only due to a bug in the system.
[21:55] <RikMills> arraybolt3: seems to work like that
[21:55] <RikMills> yes it is a bug
[21:56] <arraybolt3> Got it. Here's hoping that the Snap change does the trick then.
[21:56] <teward> i'm indirectly joined to the testcase team/group so i think i have access to everything
[22:02] <RikMills> it's building the squashfs, so looks like it will succeed :D
[22:02] <arraybolt3> \o/
[22:03]  * arraybolt3 hopes it doesn't spit out a blackened lump of charcoal
[22:04] <arraybolt3> Says "successfully built" woot!
[22:05] <arraybolt3> RikMills: Where do you see it building the squashfs? I can see the livefs build logs but not sure what logs you're looking at.
[22:06] <RikMills> arraybolt3: you know when you look at a running build and it shows you a short part of the current build log?
[22:07] <RikMills> when I looked at that I just happend to do it at the time when it said it was making the squashfs
[22:07] <arraybolt3> Ah.
[22:07] <arraybolt3> OK then we're looking at the same file.
[22:11] <arraybolt3> Woot, we have a new ISO!
[22:12] <arraybolt3> Aaaand... all of the links are 404'ing. Guess some patience is required.