[02:51] <guiverc> likely most have seen this, but kinetic final freeze - https://lists.ubuntu.com/archives/ubuntu-devel-announce/2022-October/001324.html
[02:51] <arraybolt3[m]> guiverc: Looks like all our bug fixes sneaked in *just* under the wire, so \o/
[13:08] <arraybolt3[m]> Simon Quigley: We could probably use a Lubuntu RC ISO. Last one on the tracker is still from 10-13. Is that something you do or should I be bugging someone else to press the button?
[13:10] <guiverc> arraybolt3[m], can you wait for the cron job to build normally (note: I've not looked to see if there is a build failure, but as I recall it's too early for us yet... though I'm more interested in bed at this time of day ...)
[13:11] <arraybolt3[m]> guiverc: Ah, didn't know there was a cron job, and I saw that the Ubuntu ISO was already built. Thanks!
[13:12]  * guiverc would see clicking 'request build' as a waste ... thanks arraybolt3[m] 
[13:13] <guiverc> sorry I can't think of URL for cron job (where to confirm build start times)... others may know it..  (launchpad somewhere)
[13:14] <arraybolt3[m]> np, I thought it might be manually triggered since Ubuntu's on 10-14 and we're on 10-13.
[13:16] <guiverc> any product manager (I believe; iso.qa.ubuntu.com page you'll know, just don't view the Administration detail at bottom of page) can click builds; but its a waste if not required (cron job would still run I'd expect meaning it'd be stale super fast)
[13:56] <kc2bez[m]> RC images have to be initially built by the release team.
[13:57] <kc2bez[m]> We "the product managers" can re-build them or mark them as ready, etc
[13:59] <kc2bez[m]> If you scroll back in -release you can see they were starting with Ubuntu first.
[14:00] <arraybolt3[m]> That explains it. I don't usually pay super close attention to what goes on there (I skim it for important stuff and whatnot, looks like I missed some this time).
[14:01] <kc2bez[m]> No worries.
[17:25] <lubot> [telegram] <Leokolb> Initial tests on 14-10-22 (RC) Lubuntu Kinetic look good
[18:27] <arrayboltq> Live session test of Lubuntu Kinetic RC
[18:27] <arraybolt3> arrayboltq: Ping
[18:27] <arrayboltq> Works
[18:34] <arraybolt3[m]> We have duplicate buttons for Calamares in the RC ISO, in the Application Menu.
[18:35] <arraybolt3[m]> One launches Calamares with the Breeze theme, the other one launches it with a system theme that I believe is the result of a prior bugfix.
[18:35] <arraybolt3[m]> The Breeze-theme-enabled Calamares launcher is "Install System", while the normal one is "Install Lubuntu 22.10."
[18:37] <arraybolt3[m]> Will be filing a bug report soon-ish (after this test is complete).
[18:46] <kc2bez[m]> I think there is a bug for that already 
[18:47] <kc2bez[m]> There is unfortunately no easy solution to remove it. One comes from upstream Calamares and one we install.
[18:48] <arraybolt3[m]> We can't just patch it out the way that Debian patches out stuff for DFSG things?
[18:48] <kc2bez[m]> There is an upstream LXQt bug that should prevent it from displaying in the menu
[18:49] <kc2bez[m]> There is a patch already in Calamares 
[18:49] <arraybolt3[m]> Hmm. OK.
[18:49] <arraybolt3[m]> If it fails, we may want to release note that.
[18:49] <arraybolt3[m]> I mean it's not that big a deal, most users probably won't notice it or will just skim over it. Might be interesting to see how the "Install system" button works for installing Lubuntu, though.
[18:51] <kc2bez[m]> Fair point. Both should work in theory. One uses sudo and one uses pkexec I think.
[18:52] <arraybolt3[m]> Sounds right, though I remember we had problems with that earlier in the cycle, so that might cause trouble.
[18:53] <kc2bez[m]> Here is the upstream issue preventing us to hide the menu entry. https://github.com/lxqt/lxqt/issues/1743
[18:53] -ubot93:#lubuntu-devel- Issue 1743 in lxqt/lxqt "Desktop files with NotShowIn=LXQt are still displayed in the menu" [Open]
[18:55] <arraybolt3[m]> Blah.
[18:58] <kc2bez[m]> Agreed. I sadly chased that one around a bunch.
[19:02] <arraybolt3[m]> Uhh... another thing, this might be intended behavior, but if I switch the Qt theme to "cde", menus no longer open without specifically clicking on them (i.e., the usual "hover over a menu to open it" stuff in the Application Menu and other areas doesn't seem to work).
[19:02] <arraybolt3[m]> (Probably no one cares about that, but since I was testing theme changing, and noticed it, figured it might be good to point out.)
[19:05] <kc2bez[m]> I suppose that might be intentional. 🤷🏻‍♂️
[19:05] <kc2bez[m]> I think "old" when I see cde so... 
[19:05] <arraybolt3[m]> Exactly.
[19:35] <lubot> [telegram] <Leokolb> Upgrades from Jammy to kinetic /with+without backports good
[23:14] <lubot> [telegram] <guiverc> Thanks @Leokolb (re: release-upgrades)