[03:30] <nishit_> Hi team, let me know if it is ok for me to push mariadb-10.6 updates to jammy, bug ref: https://launchpad.net/bugs/2006882
[03:30] -ubottu:#ubuntu-release- Launchpad bug 2006882 in mariadb-10.6 (Ubuntu) "MDEV-29988 affects MariaDB in Ubuntu" [Undecided, Fix Released]
[05:47] <rs2009> bdmurray: could you take a look at https://code.launchpad.net/~rs2009/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/437647? (it adds Ubuntu Unity to DistUpgrade.cfg)?
[05:49] <rs2009> vorlon: I saw your comment in your merge proposal in the Ubuntu Unity seed repo; ~ubuntu-core-dev has been invited to the Unity7 Maintainers team
[05:50] <rs2009> also, could we sync the ubuntu-unity-desktop package with the seed?
[06:32] <khfeng> rbasak: can you please review and sponsor the debdiff in  https://bugs.launchpad.net/bugs/2007331? Thanks!
[06:32] -ubottu:#ubuntu-release- Launchpad bug 2007331 in pulseaudio (Ubuntu Lunar) "Fix HFP mSBC support on Realtek Bluetooth USB controller" [Medium, Confirmed]
[08:29] <sil2100> paride: morning! How are the 22.04.2 subiquity images looking so far?
[08:31] <rbasak> khfeng: sorry, I'm off for the next few weeks
[08:49] <paride> sil2100, hi! looking good, I submitted results to the iso tracker yesterday
[08:49] <sil2100> paride: excellent, thanks!
[08:49] <sil2100> paride: btw. can you help me poke the desktop team for some desktop testing? Since I poked them yesterday but I still only see 2 test results so far...
[08:50] <sil2100> Maybe I'm poking them too early in the morning
[08:52] <paride> sil2100, I also have a couple of desktop results to submit, and I'll try to poke someone from desktop
[09:12] <khfeng> rbasak: still thanks!
[09:13] <khfeng> sil2100: so, can you please review and sponsor the debdiff in  https://bugs.launchpad.net/bugs/2007331? Thanks!
[09:13] -ubottu:#ubuntu-release- Launchpad bug 2007331 in pulseaudio (Ubuntu Lunar) "Fix HFP mSBC support on Realtek Bluetooth USB controller" [Medium, Confirmed]
[10:02] <sil2100> khfeng: hello! eeek! Might be a bit problematic this week for me, I'm swamped with 22.04.2 work + others!
[11:10] <utkarsh2102> sil2100: heey, one more thing around "task", sorry :P
[11:11] <utkarsh2102> sil2100: when we mention add_task install cloud-image (cf: https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/config?h=2.799#n941)
[11:12] <utkarsh2102> what happens really?
[11:12] <utkarsh2102> the cloud-image seed's definition is used?
[11:12] <utkarsh2102> that is https://people.canonical.com/~ubuntu-archive/seeds/ubuntu.jammy/cloud-image
[11:12] <utkarsh2102> so the three things gets installed: ubuntu-server, cloud-init, and openssh-server?
[11:12] <utkarsh2102> or the task install cloud-image means the germinated output of the whole seed?
[11:15] <sil2100> utkarsh2102: hey! It installs something closer to the latter. Basically it installs all packages that are in the 'cloud-image' task, which basically comes from germinating the cloud-image seed
[11:16] <utkarsh2102> then what's the difference between adding something as a task and germinating the whole seed?
[11:16] <utkarsh2102> so is cloud-image germinated behind the scenes?
[11:27] <khfeng> sil2100: oops. still thanks!
[11:27] <khfeng> tjaalton: your turn... can you please review and sponsor the debdiff in  https://bugs.launchpad.net/bugs/2007331? Thanks!
[11:27] -ubottu:#ubuntu-release- Launchpad bug 2007331 in pulseaudio (Ubuntu Lunar) "Fix HFP mSBC support on Realtek Bluetooth USB controller" [Medium, Confirmed]
[11:39] <tjaalton> khfeng: okay
[12:10] <khfeng> tjaalton: thanks a lot
[13:24] <sil2100> Ouch, we seem to have a possible .2 blocker!
[13:24] <sil2100> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2008082
[13:24] -ubottu:#ubuntu-release- Launchpad bug 2008082 in ubiquity (Ubuntu) "Install crash with broadcom wifi" [Undecided, New]
[13:41] <sil2100> Oh hoo, hmmm, could it be locale related?
[14:18] <fheimes> Hi @ubuntu-archive, the s390-tools (/ s390-tools-signed) package for lunar is stuck.
[14:18] <fheimes> The LP build: https://launchpad.net/ubuntu/+source/s390-tools/2.26.0-0ubuntu1/+build/25599529
[14:18] <fheimes> says that the "Binary packages awaiting approval in UNAPPROVED queue".
[14:18] <fheimes> Would you be so kind to approve?
[15:09] <coreycb> hello sru team, we have a small SRU for neutron in the focal unapproved queue if someone can take a look please.
[15:30] <sil2100> Ok, re: the possible-blocker-bug above - this might not be a regression since .1
[15:31] <sil2100> I think it's just a limitation of ubiquity + missing locale packages on the images for budgie
[15:54] <sil2100> paride: heeey
[15:54] <sil2100> paride: do the automated testing for subiquity test both the GA and the HWE kernel installs?
[15:54] <sil2100> paride: did you by any chance test the HWE kernel installation scenario?
[16:07] <paride> sil2100, only the GA kernel is tested in automation. I did try an hwe install in a VM, without hitting issues, but of course there's no special hardware there
[16:07] <paride> sil2100, there are some hwe reports on arm64: https://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271835/testcases/1697/results
[16:07] <sil2100> paride: phew, thanks. Since I did an install but didn't check if it was actually using the right kernel at the end
[16:08] <sil2100> Since one regression in comparison to 20.04 we *might* have is the fact that even when you select the HWE kernel, the target might have two kernels installed...
[16:08] <sil2100> I don't think that's per design?
[16:08] <sil2100> Actually I don't know if that's what's happening
[16:14] -queuebot:#ubuntu-release- New binary: tzdata [amd64] (lunar-proposed/main) [2022g-7ubuntu1] (core)
[16:22] <seb128> hum, the iso tracker states that the Ubuntu Desktop Lunar daily is rebuilding but there is no build listed in https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/lunar/ubuntu
[16:22] <seb128> I tried to trigger a new build but no sign of it having an effect
[16:23] <seb128> could someone trigger a build on https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/lunar/ubuntu directly?
[16:23] -queuebot:#ubuntu-release- New binary: webkit2gtk [i386] (lunar-proposed/main) [2.39.90-1ubuntu1] (desktop-core, i386-whitelist)
[16:52] <sil2100> seb128: this needs to be cleared on ancientiminister
[16:52] <sil2100> I'll do that in a free  timeslot
[17:07] <seb128> sil2100, ack, thanks
[18:04] <sil2100> xnox, klebers, smb: I got a report that there is issue with secureboot and dkms on .2, with the broadcom driver at least
[18:06] <sil2100> With kernels/shims landing so late and not having testing resources, how could this been properly checked..?
[18:08] <sil2100> bdmurray: it seems similar to the kinetic issue, but I thought we fixed this with https://launchpad.net/ubuntu/+source/dkms/2.8.7-2ubuntu2.1
[18:08] <bdmurray> It doesn't seem fixed in Jammy
[18:08] <sil2100> Also, I  thought it was broken by the kinetic version of dkms
[18:10] <sil2100> aka, I think it was a breakage we got when we pulled in a new dkms from Debian. But in jammy we didn't get anything besides the fix upload from Dimitri
[18:10] <sil2100> arraybolt3 is filling in a bug now
[18:10] <arraybolt3> Trying anyway, this laptop is slow so bear with me :-/
[18:11] <arraybolt3> what? ubuntu-bug dkms is telling me that the package doesn't appear to be an official Ubuntu package >_<
[18:12] <bdmurray> That always happens if you haven't run 'apt-get update'
[18:12] <bdmurray> Also filing it about ubiquity would be best so we get install log files.
[18:12] <arraybolt3> Ah, OK thank you.
[18:23] <arraybolt3> sil2100: bug 2008120
[18:23] -ubottu:#ubuntu-release- Bug 2008120 in ubiquity (Ubuntu) "Third-party drivers are silently left unsigned when installing Ubuntu Desktop on a system with Secure Boot, Broadcom WiFi, and LVM+encryption" [Undecided, New] https://launchpad.net/bugs/2008120
[18:24] <arraybolt3> bdmurray, xnox, klebers, smb: ^
[18:24] <jbicha> arraybolt3: do you have time to check if that issue also happens with 22.04.1 ?
[18:25] <arraybolt3> Yes.
[18:25]  * arraybolt3 digs up a faster USB drive
[18:26] <sil2100> ...that would be a good test indeed
[18:26] <sil2100> Since I think we only started testing secureboot with DKMS actually only with kinetic
[18:36] <arraybolt3> Lovely. I can't boot the 22.04.1 ISO.
[18:36] <arraybolt3> Verification failed: (0x1A) Security Violation
[18:36] <arraybolt3> Somehow I've managed to scramble Secure Boot on this laptop.
[18:38] <arraybolt3> I think I must be booting the wrong shim somehow?
[18:39] <arraybolt3> Sigh. Anyone know how to clear the old shim keys? The shim on the 22.04.1 ISO is booting but it's not willing to boot GRUB probably because of the key rotation in shim we did recently.
[18:59] <bdmurray> I tried recreating bug 1991725 but with virtualbox and the while I received no MOK enrollment in the boot process there are vbox drivers loaded e.g. vboxdrv vboxnetadp vboxnetflt.
[18:59] -ubottu:#ubuntu-release- Bug 1991725 in dkms (Ubuntu) "fails to sign kernel modules" [High, Fix Released] https://launchpad.net/bugs/1991725
[19:00]  * arraybolt3 meanwhile still can't get 22.04.1 to boot :(
[19:01] <sil2100> juliank: ^ do you have any idea on how to proceed here?
[19:02] <arraybolt3> (I tried resetting all existing MOK keys, which had no effect.)
[19:03] <juliank> Boot the 22.04.2 preview iso or disable secure boot and then do reset of the sbat level with mokutil
[19:03] <arraybolt3> Not sure what the "rest of the sbat level" means. I have to boot the 22.04.1 iso for regression testing, with Secure Boot enabled.
[19:04] <arraybolt3> Oh, "reset", not "rest". Nvm.
[19:04] <arraybolt3> Will attempt, thank you!
[19:05] <sil2100> I knew juliank is the right person to ping regarding hacking shim!
[19:05] <sil2100> juliank: thanks!
[19:05] <sil2100> arraybolt3: and thank you for the help debugging this o/
[19:05] <sil2100> I need to rest a moment AFK
[19:19] <arraybolt3> juliank: What would be the command to reset SBAT? mokutil no longer appears to support --set-sbat-policy.
[19:31]  * arraybolt3 has to go afk
[19:36] -queuebot:#ubuntu-release- New binary: rustc [arm64] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[19:37] -queuebot:#ubuntu-release- New binary: rustc [amd64] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[19:38] -queuebot:#ubuntu-release- New binary: rustc [s390x] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[19:53] <arraybolt3> Actually, it looks like the mokutil version in 22.04.1 is too *old.
[19:54] <arraybolt3> OK I can work around that probably.
[20:08] <arraybolt3> WOOT got it! OK, finally testing 22.04.1.
[20:20] <sil2100> \o/
[20:20] <sil2100> arraybolt3: waiting with anticipation!
[20:20] <arraybolt3> I had to install the mokutil from Kinetic to get it working >_<
[20:23] <arraybolt3> sil2100: Good news, it's not a regression!
[20:23] <arraybolt3> Same exact problem on 22.04.1
[20:24] <sil2100> I'd like to say 'yay', but then again, bugs like this are never good
[20:24] <arraybolt3> I personally would *prefer* that this be fixed for 22.04.2 but if we have no choice, we have no choice. And no one has brought it up in support venues while I was around.
[20:24] <sil2100> Can you leave a comment on the bug for that?
[20:24] <arraybolt3> If I can manage to get to the tab, yes.
[20:26] <sil2100> Big thanks for all the testing. It's really unfortunate as we basically recommended people that encountered issues with Broadcom in kinetic installs to use 22.04.1
[20:26] <sil2100> oh well
[20:35] -queuebot:#ubuntu-release- New binary: rustc [armhf] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[20:56] <pmatulis> rbasak, hi, verification to have this enter -updates is done. it's a high priority for enterprise cloud users: https://launchpad.net/ubuntu/+source/ovn/20.03.2-0ubuntu0.20.04.4
[20:57] <sil2100> Ok, and I'm still investigating the locale-based offline-mode crash, and I think I'm getting close
[21:02] <rbasak> pmatulis: sorry, I'm off for a few weeks.
[21:11] <sil2100> Oh no... this seems to point to a regression in language-selector
[21:30] <sil2100> Oh no, I'm getting flashbacks
[21:33] <sil2100> This starts feeling as if another issue with the apt cache on the live filesystem being invalid
[21:34] <bdmurray> I've been able to recreate bug 2008120 w/ qemu and a broadcom wireless device I found lying around my office
[21:34] -ubottu:#ubuntu-release- Bug 2008120 in ubiquity (Ubuntu) "Third-party drivers are silently left unsigned when installing Ubuntu Desktop on a system with Secure Boot, Broadcom WiFi, and LVM+encryption" [Undecided, New] https://launchpad.net/bugs/2008120
[21:36] <sil2100> Yeah, not a regression, but we need to release note it
[21:38] <bdmurray> How was it determined not to be a regression?
[21:38] <arraybolt3> Uses 22.04.1, reproduced the bug.
[21:38] <arraybolt3> *Used
[21:38] <bdmurray> Ah, I'd missed that.
[21:38] <arraybolt3> (Thus my small tantrum over Secure Boot earlier, since installing 22.04.2 makes it impossible to boot a 22.04.1 ISO :P)
[21:39] <arraybolt3> (Without using mokutil to fix SBAT.)
[21:39] <sil2100> GRRR
[21:39] <sil2100> SHIT, this IS the same issue as we had previously
[21:40] <sil2100> Something's wrong with out build scripts
[21:40] <sil2100> *our
[21:40] <sil2100> The locale-dependent offline-install issue is the same as we had with the kernels (I think) previously, the one where I had to manually repack all the candidate isos
[21:41] <arraybolt3> That sounds bad.
[21:41] <arraybolt3> OK, well where's the build scripts? And maybe a link to the bug report?
[21:41] <sil2100> Basically doing a `rm -rf *Packages` in /var/lib/apt/lists fixes it
[21:42] <sil2100> Let me write down my findings
[21:42] <arraybolt3> So I guess the question then is how hard it is to deploy new build scripts and then use them, test the results, and push them.
[21:42] <arraybolt3> Release day isn't 'till tomorrow, I think a concerted effort could probably pull it off.
[21:42] <sil2100> I think it would be hard to pin-point where the bug is happening
[21:43] <arraybolt3> Right but you have a command that fixes it, why not run it immediately before the step where the filesystem gets squashfs'ed?
[21:43] <sil2100> I think we need to identify what's breaking this, but for now I think I'd resort again to re-packing the desktop isos
[21:43] <sil2100> hmmm
[21:43] <arraybolt3> I mean that's what you're about to do by hand anyway.
[21:44] <sil2100> That's also an option, but I think it would still be easier to just repack
[21:44] <sil2100> Since livecd-rootfs is a bit of a risky beast
[21:44] <sil2100> But yeah, certainly an option
[21:45] <arraybolt3> Perhaps it's better to leave it unmodified so we can fix the real bug.
[21:45] <arraybolt3> (livecd-rootfs is a bash script, right? Might be a fun project for me to hack on at some point.)
[21:46] <arraybolt3> Nope, Python. Still, I know that and can fiddle with it.
[21:47] <arraybolt3> er, mixture of both.
[21:47]  * arraybolt3 has a head explosion and then goes back to what I was doing
[21:51] <sil2100> https://bugs.launchpad.net/ubuntu-cdimage/+bug/2008082
[21:51] -ubottu:#ubuntu-release- Launchpad bug 2008082 in Ubuntu CD Images "Install crash with broadcom wifi" [Critical, Triaged]
[21:52] <sil2100> bdmurray, vorlon, paride: FYI ^
[21:52] <sil2100> fossfreedom: ^
[21:52] <sil2100> arraybolt3: ahahah, yeah, it's actually a very terrible set of bash scripts, some Python
[21:53] <mwhudson> a distressing amount of livecd-rootfs is actually run by sh not even bash
[21:53] <arraybolt3> The joys of legacy code.
[21:54] <arraybolt3> Speaking of manual repacks, I have to repack lxqt-runner so I'm gonna go do that, yell at me when you need extra testing help.
[22:43] <liushuyu> Hi there, I would like to request the removal of https://launchpad.net/ubuntu/+source/rustc/1.67.1+dfsg0ubuntu1-0ubuntu1/ from LL-proposed due to a critical issue described in https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/2007642/comments/7
[22:43] -ubottu:#ubuntu-release- Launchpad bug 2007642 in rustc (Ubuntu) "Upgrade Rust to 1.67.1" [Undecided, In Progress]
[22:48] <bdmurray> Is there an AA who can help liushuyu ?
[23:14] -queuebot:#ubuntu-release- New binary: dm-writeboost [amd64] (lunar-proposed/none) [2.2.16-0.1] (kernel-dkms)
[23:36] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (jammy-proposed/main) [2.765.17 => 2.765.18] (desktop-core, i386-whitelist)
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (jammy-proposed) [2.765.18]