[16:59] -queuebot:#edubuntu- Unapproved: cloud-init (bionic-proposed/main) [22.4.2-0ubuntu0~18.04.1 => 23.1.1-0ubuntu0~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[16:59] -queuebot:#edubuntu- Unapproved: cloud-init (focal-proposed/main) [22.4.2-0ubuntu0~20.04.2 => 23.1.1-0ubuntu0~20.04.1] (core, edubuntu, ubuntu-cloud)
[22:30] <arraybolt3> Eickmeyer: Is there anything in particular that would cause the Broadcom drivers to not be available/not get installed on Edubuntu? I have Secure Boot disabled on my Broadcom laptop but the driver isn't activated when I check the box to install proprietary drivers, and the driver doesn't appear to be installed in the installed system.
[22:31] <Eickmeyer> arraybolt3: Probably not in the ship-live seed. Easy fix for tomorrow's run.
[22:31] <arraybolt3> I'll be filing a bug for it but I thought it might be useful to have a "mini bug report" now.
[22:31] <Eickmeyer> Nah, no need for a bug report.
[22:31] <arraybolt3> Nice.
[22:31] <arraybolt3> (Was just about to ask that.)
[22:33] <arraybolt3> I'm also having a bit of trouble with launching Geary (the email app on the Dash or whatever it's called) - trying to launch it with the button appears to fail silently or with an error message that vanishes too quickly to read, trying to launch it from the terminal gives "Error creating controller: No such secret collection at path: /org/freedesktop/secrets/collection/login".
[22:33] <arraybolt3> Last time, I was able to reboot the system and then it launched normally.
[22:34] <Eickmeyer> I'd love to investigate that but Launchpad just went 500 on me.
[22:35] <Eickmeyer> Ope, nvm.
[22:35] <Eickmeyer> arraybolt3: New geary in proposed, needed a rebuild against icu.
[22:35] <arraybolt3> Wow that was fast.
[22:35] <arraybolt3> Guess I'll test that on tomorrow's ISO too :D
[22:35] <Eickmeyer> Probably not, it's been sitting there since Feb 6.
[22:36] <arraybolt3> Oh.
[22:37] <Eickmeyer> It's blocked by webkit2gtk right now.
[22:37] <arraybolt3> Which has an autopkgtest failure and a bunch of riscv64 nonsense attached to it :-/
[22:37] <Eickmeyer> Yep.
[22:38] <arraybolt3> Sigh. I kinda wish we had *not* started supporting RISCV until we had actual build hardware to support it with :P
[22:38] <arraybolt3> But whatever, we live with it.
[22:38] <Eickmeyer> Yeah, I don't imagine geary is going to stay broken for long.