[00:14] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/116/
[00:14] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/817/
[00:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/365/
[01:41] <kc2bez[m]> wxl it looks like cala made it to release. 
[01:53] -lugito:#lubuntu-devel- [T180: Cleanup Ubuntu Wiki] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T180#4382
[03:12] <wxl[m]> iso rebuilding for any late night testers…
[04:43] <wxl[m]> So we've got version 20210301 so we'll have 20210301.1 later on
[06:19] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just failed after succeeding: https://ci.lubuntu.me/job/jobgenerator/891/
 Tested 20210301 - have the grub/incomplte packages fail as in previous EFI boots - the partitions look right- should i wait for next build  0301.1 or file bug report now? (re @lubuntu_bot: (irc) <wxl[m]> So we've got version 20210301 so we'll have 20210301.1 later on)
[07:57] <guiverc> thanks for update @Leokolb, I don't know; if it's easier, I'd suggest file new report (which you can always make duplicate if needs be).  Thanks for testing
 That was my thought as well-best to document the errors-we can always mark the bug as fixed later.. (re @lubuntu_bot: (irc) <guiverc> thanks for update @Leokolb, I don't know; if it's easier, I'd suggest file new report (which you can always make duplicate if needs be).  Thanks for testing)
[07:59] <guiverc> thank you for testing.. I'd just `cd` into my directory where I kick off zsync_hirsute..  I'm happy to run a test if you think confirmation needed 
[08:00]  * guiverc you'd posted your update before just prior to me typing zsync_h<tab>
 I will have the bug up in about 15 mins..yes it is an EFI failure -BIOS in virt machine was good. (re @lubuntu_bot: (irc) <guiverc> thank you for testing.. I'd just `cd` into my directory where I kick off zsync_hirsute..  I'm happy to run a test if you think confirmation needed)
 @guiverc Also thinking about yr idea re:encryptions..we are now at calamares 3.2.37 and they have these comments : https://calamares.io/calamares-3.2.37-is-out/
 @guiverc see the bit under CORE section - should go into our manual I think
[08:04]  * guiverc reading it now
[08:05] <guiverc> I concur... It'd stop Lubuntu from getting some flak (unlikely, but at least it's somewhere we can point to).   
[08:07] <guiverc> Faster maybe pasting it into discourse until manual gets update though , no hurry yet though; we're not at 21.04 release; we could maybe first use at Testing Week on discourse; march 4  (I plan to try & write something if testing-week goes ahead)
[08:08] <guiverc> https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539
 @guiverc finished the BR see 1917292 - also entry on QA site
[08:29] <guiverc> thanks, I'd have provided URL/lp report for the other bug report in it; 1916356
[08:30] <guiverc> save someone from needing to look it up if you think the same
 agree (re @lubuntu_bot: (irc) <guiverc> save someone from needing to look it up if you think the same)
 will do
 Updated the description.. (re @lubuntu_bot: (irc) <guiverc> thanks, I'd have provided URL/lp report for the other bug report in it; 1916356)
[08:36] <guiverc> :) & thanks
[09:07] <kc2bez[m]> ok, bug 1917292 is a different issue from 1926356 so that is good. sort of anyway. 
[10:11] <kc2bez[m]> It looks like a grub problem http://paste.ubuntu.com/p/k3jRYtzv4F/
 Curious - what about the "broken packages"? (re @lubuntu_bot: (irc) <kc2bez[m]> It looks like a grub problem http://paste.ubuntu.com/p/k3jRYtzv4F/)
[10:33] <kc2bez[m]> What I think happened is, grub updated and the signed Linux kernel has a hard dependency on a specific version of grub. I don't think the signed kernel has made it through yet. It looks like it is being worked on. 
 TKS (re @lubuntu_bot: (irc) <kc2bez[m]> What I think happened is, grub updated and the signed Linux kernel has a hard dependency on a specific version of grub. I don't think the signed kernel has made it through yet. It looks like it is being worked on.)
[11:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/365/
[11:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/817/
[11:04] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/116/
[11:14] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_qtermwidget/818/
[11:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/366/
[11:14] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/117/
[11:14] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_qtermwidget/818/
[11:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/366/
[11:15] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget just failed after being unstable: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/117/
[11:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/818/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/818/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/366/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/117/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_qtermwidget/819/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just became unstable after failing: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/367/
[11:40] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget just became unstable after failing: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/118/
 anyone know anything about this : https://phab.lubuntu.me/p/hudsonwyndham/
[14:17] <kc2bez[m]> Looks like spam. I disabled them from phab.
 and THIS is why i said we should disable registrations without admin approvals.
 which... is enabled so how does that user registration actually exist o.O
 Someone approved them.
 *sends this to a different realm*
 @kc2bez unless the user was otherwise named on registration, in which case is how they got approved by looking 'legit' and then spammer went in and tweaked it
 which... isn't unusual to see with 'smart' spammers
 see it on Ask Ubuntu regularly
 though there's no user 'approval' things there
[16:15] <Eickmeyer[m]> wxl: ack, just means we've got a bad iso build.
[16:16] <Eickmeyer[m]> Usually the Studio isos build around 11AM PST, so there's time for the new Cala to land.
 @kc2bez @wxl23 fyi - ISO build 20210301.1 EFI fails as previous build - https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292
 that... shouldn't have happened o.O
[17:50] <wxl> @leokolb not exactly. you'll notice the errors are totally different. looks like efibootmgr may be stuck in proposed
[17:51] <kc2bez[m]> I actually think it is grub it is complaining about. Some of the error is obscured.
[17:51] <kc2bez[m]> I ran one in debug mode.
 wxl: efibootmgr hasn't changed since Focal (17-1)
 if it's a Grub complaint then we need the grub info :P
 I think this is same error as I reported after earlier ISO this morning my time (re @lubuntu_bot: (irc) <wxl> @leokolb not exactly. you'll notice the errors are totally different. looks like efibootmgr may be stuck in proposed)
[17:51] <kc2bez[m]> Grub updated already and the kernel needs to follow I think
[17:51] <wxl> agreed @leokolb
[17:52] <wxl> well it is saying "Recommends: efibootmgr but it is not going to be installed"
[17:52] <wxl> so you tell me, @teward001
 wxl: that'd require additional debugging - if you attempt to install it what errors does that generate.
[17:52] <kc2bez[m]> Here is the paste I had earlier http://paste.ubuntu.com/p/k3jRYtzv4F/
[17:52] <wxl> @teward001 https://launchpadlibrarian.net/525650204/screen.jpg
 if it's waiting for a *newer* version to be available it won't happen unless someone way above us does it
[17:53] <wxl> ah there it is
[17:53] <wxl> or is it?
 yeah that's a grub version mismatch problem
 hmm
[17:54] <wxl> we got a new src:grub2 on the 25th
[17:54] <kc2bez[m]> We fixed the partition problem \o/
[17:54] <kc2bez[m]> XD
[17:54] <wxl> :/
 then something's up with your grub-efi-amd64-bin deps.  Possibly a cala problem or outdated ISO info because...
 grub-common | 2.04-1ubuntu40          | hirsute          | amd64, arm64, armhf, ppc64el, riscv64, s390x
 ^ it's -1ubuntu40 per rmadison so
 And that is once again same error rec latest build (re @lubuntu_bot: (irc) <wxl> @teward001 https://launchpadlibrarian.net/525650204/screen.jpg)
[17:55] <wxl> i mean we shouldn't have special deps of any kind :)
 no but it sounds like grub-efi-amd64-bin doesn't like this.
 wxl: can you get apt-cache policy grub-efi-amd64-bin output in the test env?
 I don't have the daily synced atm
 *is doing this now*
[17:57] <wxl> i'm really confused with how short the session.log is https://launchpadlibrarian.net/525660578/session.log
[17:57] <kc2bez[m]> Something changed there too, yes.
[17:57] <kc2bez[m]> I appended a `-d`
[17:58] <wxl> …to ultimately end up with something that included that paste?
[17:58] <kc2bez[m]> yes, I did it at home though
[17:58] <wxl> craaaaaaaaap
[17:58] <kc2bez[m]> I can run another here
[17:59] <wxl> maybe we should change the Exec in the desktop to -d
[18:00] <kc2bez[m]> I'm not sure, it does enable the debug button in the lower left which might confuse folks.
[18:00] <wxl> ehh true
[18:01] <kc2bez[m]> There may be a way to change the default log level, I am not sure though.
[18:02] <kgiii> In "QTerminal drop down", if I go to drag the window it closes. It doesn't behave that way on 20.04.
[18:02] <wxl> kgiii: for that one, go ahead and file a bug, please
[18:02] <kgiii> Will do.
[18:03] <wxl> @kc2bez[m]: what i don't understand is why there would be a sudden change. we've been keeping up on cala versions
[18:04] <kgiii> In regular QTerminal, setting the "start with preset" to anything, such as "2 terminals horizontally" makes no difference. 
[18:07] <wxl> kgiii: that might be worth a bug too
[18:07] <kgiii> Will do.
[18:12] <kc2bez[m]> https://paste.ubuntu.com/p/P8DScNCnkm/
[18:12] <kc2bez[m]> There is a debug log ^
[18:20] <wxl> ok so here is the one quirk of calamares. we get grub-efi-* (and shim-signed, but that's not relevant here) as a result of this https://phab.lubuntu.me/source/calamares-settings-ubuntu/browse/master/lubuntu/modules/before_bootloader_context.conf
[18:20] <kgiii> Are "QTerminal drop down" bugs reported as QTerminal bugs? I can't find a specific QTerminal drop down anything.
[18:21] <wxl> !info src:qterminal
[18:21] <wxl> yeah i'd say so
[18:22] <kgiii> Thanks. I got one reported, I'm now on that one.
[18:22] <wxl> anyways back to grub, we either get grub-efi-amd64-signed or we get grub-efi-ia32
[18:22] <kc2bez[m]> kgiii One thing you can do if you doubt which package to file against and it is a GUI application is `ubuntu-bug -w` then click on the offending application.
[18:23] <kgiii> I know, but that won't work in this case. It not only closes if you move it, it closes if you click anywhere else.
[18:23] <wxl> and we got a new grub2-signed on the 25th
[18:23] <wxl> soooooooooooooooooooooooooo
[18:23] <wxl> this is really irritating me
[18:23] <kc2bez[m]> That does seem to be the last thing changed.
[18:24] <kc2bez[m]> <kgiii "I know, but that won't work in t"> Gotcha.
[18:25] <wxl> here's an efi boot fail on mate/xubuntu https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916920
[18:26] <wxl> it is oem specific, but that may be circumstance
[18:26] <kgiii> Yeah, it turns out to be more involved than just moving it. It also closes if you click anywhere outside the text entry field.
[18:27] <wxl> the ubiquity log (which is shown in the screenshots) are really just warnings
[18:27] <wxl> i mean i guess the gtk-critical bug might be a thing but i'm guessing the following warning is a fall over
[18:27] <wxl> tl;dr widget height crap
[18:28] <wxl> the fact that it seems to continue on past the bug is interesitng
[18:29] <wxl> i guess it would be helpful to test the other flavors and see if they're having similar issues
[18:29] <wxl> @kgiii @leokolb @guiverc game for that? ^ all i need is one other flavor complaining similarly about grub/efibootmgr or something of the sort
 I have been testing Kubuntu and Ubuntu daily for past week or so and no problem with this other than Ubuntu Studio (re @lubuntu_bot: (irc) <wxl> i guess it would be helpful to test the other flavors and see if they're having similar issues)
[18:30] <kc2bez[m]> Studio would be good too
[18:30] <wxl> this may be relatively new
 Checked Studio yesterday can do it again
[18:30] <wxl> i'd rather test not-studio personally
 why not it is using calamares (re @lubuntu_bot: (irc) <wxl> i'd rather test not-studio personally)
 Both K and U do not have this will run quick check on Xubuntu
[18:32] <kc2bez[m]> <wxl "i'd rather test not-studio perso"> ok
[18:34] <kgiii> I'm filing bugs and keeping my notes updated. If leokolb has this that'd be pretty sweet. If not, let me finish up and I'll see how much more free time I have today.
 Testing X now (re @lubuntu_bot: (irc) <kgiii> I'm filing bugs and keeping my notes updated. If leokolb has this that'd be pretty sweet. If not, let me finish up and I'll see how much more free time I have today.)
[18:35] <kgiii> Thanks!
 I tested Studio this morning (latest iso) got the 1916356 EFI failure original bug
[18:40] <kc2bez[m]> Interesting https://paste.ubuntu.com/p/3zCSPpnGvx/
[18:40] <kc2bez[m]> From the live iso ^
 kc2bez: can you show the version that is installed (apt-cache policy grub-efi-amd64-bin) on the ISO?
 that may give some explanation for a mismatch.
 cause the 37 one sounds like a holdover
 unless there's really something wrong wtih GRUB
[18:49] <kc2bez[m]> standby
[18:52] <kc2bez[m]> Ha, looks like it is installing from the version on the live iso https://paste.ubuntu.com/p/yHZF5qwFRT/
[18:55] <wxl> so in total here's what's going on https://phab.lubuntu.me/source/calamares-settings-ubuntu/browse/master/lubuntu/modules/before_bootloader_context.conf
[18:56] <wxl> so that does add the live iso
[18:59] <wxl> and the second line effectively removes any repos from sources.list
[18:59] <wxl> making the only source the live iso
[18:59] <wxl> so that's weird
 Xubuntu - no errors— now testing K
[19:00] <kc2bez[m]> still why is the iso not up to date?
[19:00] <wxl> it appears we stole that from neon https://phab.lubuntu.me/rCALASETTINGS88e201e0c82eda4438f78ad949b25a43409556a2
[19:01] <wxl> that's a valid question, too, but i also have no freaking idea why we do this
[19:02] <wxl> whatever
[19:03] <wxl> see? we have 37!!!! https://cdimage.ubuntu.com/lubuntu/daily-live/current/hirsute-desktop-amd64.list
[19:04] <kc2bez[m]> wild
[19:05] <wxl> and indeed we seed all the right things
[19:06] <wxl> https://phab.lubuntu.me/source/seed/browse/hirsute/ship-live
[19:06] <wxl> not like they're specific versions or anything
 I can now confirm latest ISO's for K,X and Ubuntu all install no errors EFI mode
 One thing I found strange tho not related - none of them have visible file checking
[19:29] <wxl> OH
 kc2bez: wxl: so that sounds like a problem there.  in Ubuntu the system has the ability to install from the repos for newer things, but there's something in Cala that doesn't like it, installing from the ISOs directly and then not doing the updates.  You *may* need instead to force it to install with the versions on the ISO, and then post-install if you're on wifi update.
 just a thought
 not sure why you ain't doing that so 😔
[19:39] <wxl> i mean yes but the other problem is why is our seeding not current?
 also a good question, something to ask the release team?
 it DOES however explain the problems being observed :P
[20:08] -lugito:#lubuntu-devel- [rMANUAL1c3579325bfd: Add drop down autohide feature] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL1c3579325bfd
[20:11] <wxl> so want to make that -D6 change kc2bez[m] ?
[20:11] -lugito:#lubuntu-devel- [rMANUAL632d2f9ed922: Add lock button for not autohiding drop down] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL632d2f9ed922
[20:12] <kc2bez[m]> sure, cala settings I think.
[20:13] <wxl> yeah in the Exec call of the desktop
[20:13] <kc2bez[m]> probably need a bug for that.
[20:13] <wxl> k i'll make that happen
[20:18] -lugito:#lubuntu-devel- [rMANUAL57d48f5458fc: Add unlock] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL57d48f5458fc
[20:18] <wxl> https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1917360
[20:19] -lugito:#lubuntu-devel- [rMANUAL60e348c616ed: Add where lock button is] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL60e348c616ed
[20:19] <kc2bez[m]> Doing some updates on my VM here at work.
[20:27] <wxl> thanks for chiming in on that bug @lynorian …i did not know that
[20:32] <wxl> @teward001 well i've asked at #ubuntu-release but no response so i'm not sure what exactly to do. here's our bug though https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292
 wxl: I reasked in #ubuntu-release just now, no reply yet but I'll be persistent As Heck
[20:40] <wxl> maybe you should consider gin
[20:41] <kc2bez[m]> I would if we could get together in-person.
[20:42] <wxl> i was referring to #u-r's topic
[20:43] <kc2bez[m]> I know, I was serious though.
[20:43] <wxl> XD
[20:55] <kc2bez[m]> new cala settings building
[21:02] <kc2bez[m]> made a hirsute branch too
[21:32] <wxl> if i remove the step that basically kills sources.list (i still don't understand why) the install works
[21:33] <wxl> i pushed the commit but i don't understand why https://phab.lubuntu.me/rCALASETTINGS07a443fb588d4b45c8e978a967f6582a3caea4e7
[21:34] <wxl> even still, all i did was move it from its original location https://phab.lubuntu.me/rCALASETTINGS88e201e0c82eda4438f78ad949b25a43409556a2
[21:36] <wxl> uh
[21:36] <tsimonq2> We have to remove the cdrom entry from the new install somehow.
[21:37] <tsimonq2> Whatever way it's done, doesn't matter.
[21:37] <wxl> and then, why the heck are we using using `--no-upgrade`?//
[21:37] <wxl> this ADDS the cd rom and destroys sources.list
[21:37] <tsimonq2> ¯\_(ツ)_/¯ I wrote that code like two years ago
[21:37] <tsimonq2> No clue 
[21:37] <wxl> so none of that is relevant here
[21:37] <tsimonq2> Hack away, just be sure to test as thoroughly as you can
[21:38] <wxl> so given that the efi/grub bits are in ship-live i'm inclined to keep the addition of the cdrom
[21:38] <wxl> but destroying sources.list makes no sense, nor does using --no-upgrade
[21:38] <kc2bez[m]> What happens with no internet?
[21:39] <wxl> oh that's why destroying sources.list makes sense
[21:39] <wxl> it forces using the cdrom
[21:39] <wxl> janky way to do it
[21:39] <wxl> even still, it wouldn't have solved our issue, which all goes back to the seeding being all messed up
[21:40] <wxl> maybe if i refile our bug against the right high profile package maybe someone will care
[21:40] <wxl> maybe against germinate? 
[21:40] <wxl> too bad there isn't a package to file against for the infra misbehaving
[21:41] <tsimonq2> <wxl "janky way to do it"> Ohhh, that's why
[21:41]  * tsimonq2 snoozes after being up for 23 hours o/
[21:41] <wxl> night night
[21:45] <tsimonq2> tl;dr of my wonderful day: worked until 2 AM, had to get my car towed after my tire blew (drove on basically rim to a friend's house), AAA literally jerked my chain until 9:30 AM (original ETA 4 AM at the very latest), sent a completely incompetent tow truck driver who went to the wrong place and somehow lost a lug nut on the way, just an absolute mess. I've never been such a Karen on the phone before...
[21:45] <tsimonq2> Very much needed sleep. Extremely memorable day
[21:45] -lugito:#lubuntu-devel- [rCALASETTINGS8123671afb4f: Upload to Hirsute.] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rCALASETTINGS8123671afb4f
[21:45] -lugito:#lubuntu-devel- [rCALASETTINGSf52413a64755: Adjust log level for -D6.] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rCALASETTINGSf52413a64755
[21:45] <wxl> yeesh wow
[21:45] <tsimonq2> 24/7 roadside, suuure AAA
[21:48] -lugito:#lubuntu-devel- [T200: refactor cala bootloader script] wxl (Walter Lapchynski) just created this task: https://phab.lubuntu.me/T200
[22:06] <lynorian> this reminds me I might need to fill my spare tire
[22:06] <wxl> XD
[22:08] <wxl> the other day we were driving around and there was a car making a bunch of noise next to us and when we realized what the noise was we were shocked and got the hell away from them: their lug nuts were loose and the wheel was rattling around on the axle
 wxl I actually poked at it trying to reproduce and then went oh that is how this works. Then I added it to the manual as if it confuses someone in here it probably will confuse end users
[22:14] <wxl> @lynorian: nice! good job!
[22:58] <kgiii> Thanks @lynorian. That's the LEAST intuitive function so far but you figured it out. 
[23:14] -lugito:#lubuntu-devel- [T194: Fixup branches on cala-settings] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T194#4393