[00:04] -queuebot:#ubuntu-release- New binary: haskell-language-c99-simple [riscv64] (kinetic-proposed/universe) [0.1.2-2] (no packageset)
[00:33] -queuebot:#ubuntu-release- New binary: renpy [riscv64] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[01:42] <RAOF> luis220413: I know you won't see this now, but when you get back: I've commented on the openconnect bug, asking some questions. If you want to talk about them over IRC and happen to overlap UTC+10, feel free to give me a ping when you're around.
[05:20] -queuebot:#ubuntu-release- New binary: librecast [amd64] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: librecast [ppc64el] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: librecast [arm64] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: librecast [armhf] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[05:34] -queuebot:#ubuntu-release- New binary: librecast [s390x] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[05:35] -queuebot:#ubuntu-release- New binary: librecast [riscv64] (kinetic-proposed/universe) [0.5.1-3] (no packageset)
[08:11] <sil2100> tsimonq2: hey!
[08:12] <sil2100> tsimonq2: ...oh no, ignore me, wrong tab-completion
[08:12] <sil2100> ...and we don't seem to have tseliot here
[08:18] <sil2100> eh, I HATE nvidia installer issues
[08:19] <slyon> sil2100: FYI: some of the download links in the ISO tracker are broken again (e.g. http://cdimage.ubuntu.com/ubuntu-base/daily/20220809/jammy-base-ppc64el.tar.gz -> http://cdimage.ubuntu.com/ubuntu-base/jammy/daily/20220809/jammy-base-ppc64el.tar.gz)
[08:19] <sil2100> Yeah, sorry about that, didn't get to fixing the base links
[09:09] <sil2100> eh, nvidia installs just depress me
[09:09] <sil2100> We always have to have an issue with those
[09:09] <sil2100> I'll dig out my nvidia test laptop and try it in a moment
[09:12] <schopin_> summing up our out-of-band discussion: when installing 22.04.1 Desktop on a laptop with nvidia GPU (proprietary enabled), *without* network, the system ends up without the nvidia drivers installed. Enabling network installs it just fine, and in the logs the installer does install the driver packages, including nvidia-driver-515, but on the booted install that package is nowhere to be found.
[09:13] <schopin_> The system logs on the system don't show anywhere that the package has been uninstalled
=== schopin_ is now known as schopin
[09:13] <sil2100> I checked the logs schopin_ provided and at least from the attached installer syslog, it looks like nvidia-driver-515 is installed correctly - comparing with the 'working' logs from 22.04 release images, the only difference I see is 510 being installed instead of 515
[09:14] <schopin> The only nvidia packages installed are nvidia-kernel-common-515, a bunch of kernel modules, and nvidia-prime.
[09:14] <sil2100> So I have no idea how the end system ends up without the 515 driver installed
[09:18] <sil2100> I am cursed, cursed to respin 22.04.1 into eternity
=== jibel_ is now known as jibel
[09:26] <schopin> sil2100: look at the end of the syslog, there's a plugininstall.py crash that doesn't occur in 22.04.0
[09:28] <sil2100> Shit
[09:30] <sil2100> THis might be the cause, maybe it's missing a package dependency in the pool and crashes because it cannot get it from neither the pool or via network
[09:30] <schopin> I'm still really confused as to how/when the driver were uninstalled :/
[09:42] <sil2100> xnox and juliank are also looking into this
[09:42] <sil2100> I'll try a no-network install on my laptop in the meantime
[10:01] <sil2100> Anyway, this warrants a respin in case we find the fix
=== cascardo__ is now known as cascardo
[12:06] -queuebot:#ubuntu-release- Unapproved: rejected apparmor [source] (bionic-proposed) [2.12-4ubuntu5.2]
[12:40] <sil2100> Okay, status update on the nvidia offline stupidness
[12:40] <sil2100> We were investigating some 'easy' solutions to this
[12:40] <sil2100> So besides respinning all the images and having to deal with the fact that we have new kernels in -updates already, we had considered two 'hacky' solutions:
[12:41] <sil2100> a) Adding libdpkg-perl to the package pool. This is doable, but needs re-creating the pool on the images by hand - which is doable, but I personally never did that without using debian-cd
[12:43] <sil2100> b) juliank noticed that the bug is triggered because the live system has /var/lib/apt/lists/*_Packages files present, letting the installer know that libdpkg-perl is available via the internet (even though no networking is available). So cleaning up those on the installer images is a solution as well
[12:43] <sil2100> I just tried hand-tinkering b) and I got a successful nvidia offline installation
[12:43] <sil2100> So I'm thinking of actually trying b)
[12:44] <sil2100> I assume we'd need to do this only for Ubuntu, Kubuntu, Ubuntu Mate, Ubuntu Kylin, Xubuntu?
[12:46] <sil2100> I'll wait for a final comment from juliank how safe this is to do as a solution, but I'll start doing that on cdimage, creating a new publish id for it
[13:35] <icey[m]> hey, could i beg acceptance into jammy-proposed for python-cheroot: https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=python-cheroot
=== plars_ is now known as plars
[13:56] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (bionic-proposed) [3.0.3-0ubuntu1~18.04.3]
[14:25] <Eickmeyer[m]> sil2100: I'm seeing the same plugininstall.py crash on OEM install in Kubuntu that you were. We rely on that with Kubuntu Focus pretty heavily.
[14:25] <sil2100> This should be fixed with my hackery ;)
[14:26] <sil2100> Oh man, this will be the most hackiest of point releases I've been leading for sure
[14:27] <Eickmeyer[m]> Hackery is fun. /s XD
[14:32]  * tsimonq2 can remember hackier ones... :P
[14:42] <sil2100> hahah, for sure, but not on my watch! ;p
[14:44] <sil2100> Okay, let's see if my hacked up image via cdimage is bootable, if yes I guess I'll send it for some testing to everyone. Need to see if it's not breaking anything before we move along to repacking all the other flavors
[14:57]  * mfo feels inspired by demonstration of candid (? :) expression and technical expertise/considerations/teamwork above. (if that counts/supports in some way the people handling it. :)
[15:06] <ricotz> doko_, hi, please check the dependencies in python3-stdlib-extensions against python3-defaults
[15:10] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[15:13] <sil2100> Ok everyone! I linked the new image ^ but I cannot guarantee it's all good and shiny yet, just did a boot test on VM. My USB drive is now ready for a test ride on my Nvidia hardware
[15:14] <sil2100> I'd be grateful if people could take the image and do some dogfooding on those. To make sure we didn't break anything by clearing out those Packages files
[15:14] <sil2100> If tests won't show anything worrysome, I'll continue with other flavors
[15:22] <bdmurray> sil2100: FYI the checksums look old
[15:23] <sil2100> aaaah, yessss
[15:23] <sil2100> THanks for noticing!
[15:23] <bdmurray> quality man
[15:23]  * bdmurray has an eye for details
[15:32] <sil2100> I need those quality eyes testing the new iso then!
[15:33] <bdmurray> Its downloading. ;-)
[15:35] <sil2100> ;) Thank you
[16:04] -queuebot:#ubuntu-release- Unapproved: epiphany-browser (jammy-proposed/universe) [42.1-1ubuntu1 => 42.4-0ubuntu1] (desktop-extra)
[16:08] -queuebot:#ubuntu-release- Unapproved: evolution-data-server (jammy-proposed/main) [3.44.2-0ubuntu1 => 3.44.4-0ubuntu1] (i386-whitelist, ubuntu-desktop)
[16:11] <bdmurray> During the boot process after installing I'm seeing some "mtd device must be supplied" messages. Has anyone else seen this?
[16:12] <sil2100> I  think I've seen that before. Is this the first time you're seeing this?
[16:12] <sil2100> Oh, crap, I now think I forgot something in those images
[16:12] <arraybolt3[m]> I've seen it quite often but it doesn't seem to affect the system's usability.
[16:12] <arraybolt3[m]> It's not just in the 22.04.1 images I don't think, I've seen it on my usual 22.04 system that just kept being upgraded IIRC.
[16:13] <bdmurray> Yes, I agree its not important for the point release and I also saw it on my desktop this morning. A better question might have been has anyone reported a bug and if so what is the number?
[16:13] <sil2100> Please continue testing in the meantime since it's just minor, but I forgot to update md5sums.txt on the iso (will fix and re-pack)
[16:17] <bdmurray> Oh it was in my firefox history bug 1981622
[16:17] <ubottu> Bug 1981622 in systemd (Ubuntu Jammy) "mtd device must be supplied (device name is empty)" [Medium, Confirmed] https://launchpad.net/bugs/1981622
[16:18] <sil2100> So far I tested an nvidia normal install and a PL locale minimal install (also with nvidia) on my Dell laptop
[16:18] <sil2100> Both seemed fine
[16:18] <sil2100> Not sure what other test cases we can do to make sure nothing's broken. Can maybe someone try OEM install as well?
[16:18] <bdmurray> I thought I tested an install bug /var/log/installer/media-info has 20220809 not 20220809.1
[16:18] <sil2100> The more general dogfooding done the better. Maybe some network enabled installs?
[16:19] <sil2100> bdmurray: ah, another thing needing tweaking then
[16:20] -queuebot:#ubuntu-release- Unapproved: evolution (jammy-proposed/universe) [3.44.1-0ubuntu1 => 3.44.4-0ubuntu1] (ubuntu-mate, ubuntukylin)
[16:22] <sil2100> Okay, included in the new repack
[16:22] <bdmurray> Okay I did test the iso file with a sha256sum of 8b2070d3f9f4d417c37afdd9c0b790624bf730b45d8b75b06a680c7ec197be44 and the install went fine.
[16:22] <bdmurray> By the way there are now 2 checksums for the same iso in https://cdimage.ubuntu.com/jammy/daily-live/20220809.1/SHA256SUMS
[16:22]  * bdmurray goes for food
[16:23] <arraybolt3[m]> Is there anything particular in the testing that still need done? I did an Ubuntu MATE OEM install and a bunch of Ubuntu Studio stuff, is there other high-priority testcases or should I just tackle anything not yet done on the QA tracker?
[16:24] <sil2100> arraybolt3[m]: so I'd like someone to take a look at desktop and do some install tests - I'll also be repacking MATE, Kubuntu, kylin, budgie and Xubuntu soon
[16:25] <sil2100> bdmurray: I re-packed 20220809.1, mirrors are syncing - can you re-try in a moment?
[16:25] <Eickmeyer[m]> sil2100: is this special focus on OEM or just general end-user installation?
[16:26] <sil2100> Eickmeyer[m]: I'd say both. The main thing broken was the Nvidia driver installation, but we want to know if by hot-fixing this we didn't break anything else
[16:26] <arraybolt3[m]> I've got a desktop with an nVidia card so I should be able to test that.
[16:26] <sil2100> I suppose Budgie, MATE, Xubuntu and kylin offer installing nvidia drivers like regular Ubuntu, right? Just making sure
[16:27] <sil2100> Please also test non-nvidia cases, since I don't want to break others by accident
[16:27] <arraybolt3[m]> I guess we'll find out - I know Studio and Lubuntu do not.
[16:27] <Eickmeyer[m]> sil2100: Ok. That sounds right. And yes, the only two that don't install the Nvidia drivers are Lubuntu and Studio because calamares doesn't have a facility to use ubuntu-drivers.
[16:28] <Eickmeyer[m]> I mean, it could probably be written by sir-hacks-a-lot Simon Quigley but I digress...
[16:29] <tsimonq2> That's DOCTOR hacks-a-lot to you lmaoooo
[16:29] <tsimonq2> "Doctor in Chaos from the School of the Chaos Monkey"
[16:33] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.0-3~ubuntu22.04.2 => 1.72.2-0ubuntu1] (desktop-core, desktop-extra, i386-whitelist, mozilla)
[16:33] <sil2100> This is essentially all so terrible eh
[16:34] <sil2100> Suddenly my upload to ancientminister became terrible
[16:34] <arraybolt3[m]> sil2100: I don't know for sure if you talked about this a bit ago, but http://cdimage.ubuntu.com/ubuntu-budgie/jammy/daily-live/20220809/MD5SUMS.gpg does not exist and is listed as the checksum GPG signature for Ubuntu Budgie.
[16:34] <sil2100> We'll have to tweak it on the tracker at some point, yes
[16:35] <sil2100> Since it probably didn't get updated after we switched off to just-SHA256
[16:35] <Eickmeyer[m]> That happened quite some time ago.
[16:36] <Eickmeyer[m]> Yeah, arraybolt3 , we don't use the md5sums anymore, go with sha256.
[16:36] <arraybolt3[m]> Eickmeyer: I know that. It's just in the tracker and messes up my super-fancy handcrafted downloader script.
[16:36] <arraybolt3[m]> (Which I guess is my problem since I wrote the script, but...)
[16:38] <Eickmeyer[m]> Oh, I just use zsync and download from current.
[16:39] <Eickmeyer[m]> While, of course, making sure that current matches what's in the tracker.
[16:40] <arraybolt3[m]> Eickmeyer: Mine does a lot but I probably shouldn't dump the details in this channel (I do use zsync, though).
[16:52] -queuebot:#ubuntu-release- Unapproved: gnome-desktop (jammy-proposed/main) [42.2-0ubuntu1 => 42.4-0ubuntu1] (ubuntu-desktop)
[16:57] <bdmurray> sil2100: so which isos have been repacked?
[16:57] <sil2100> bdmurray: for now only Ubuntu, Kubuntu is uploading, and rest I'll probably be able to do faster with help of IS
[17:00] <arraybolt3[m]> wait so I just synced everything too early?
[17:13] <bdmurray> arraybolt3[m]: yes
[17:14]  * arraybolt3[m] facepalms, but hey that will hopefully make the next zsync faster!
[17:14] <sil2100> Sorry!
[17:14] <sil2100> I'll be done soon I promise
[17:15] <arraybolt3[m]> Don't be sorry, it was my fault for not paying enough attenton!
[17:15] <sil2100> In the meantime, any obvious issues with the desktop ones?
[17:15] <arraybolt3[m]> s/attenton/attention/
[17:15] <arraybolt3[m]> No clue, because the one that actually was done is still syncing...
[17:15] <arraybolt3[m]> (My Internet speed is currently around 2 to 3 megabytes per second at the moment.)
[17:16] <bdmurray> I'm doing an Ubuntu Desktop install again now
[17:24] <Eickmeyer[m]> I'm going to be spending my workday today testing Kubuntu as soon as it's available.
[17:37] <bdmurray> sil2100: my Ubuntu desktop install worked well
[17:37] <sil2100> Okay, Kubuntu repacked, syncing mirrors
[17:37] <sil2100> Once 09.1 appears for Kubuntu, could someone try it out and see if I didn't totally break something by accident?
[17:37] <sil2100> I'll continue with mate
[17:38] <sil2100> bdmurray: phew
[17:38] <sil2100> Eickmeyer[m]: ^
[17:38] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[17:38] <Eickmeyer[m]> sil2100: On it, will be watching.
[17:38] <Eickmeyer[m]> Oh, there it is.
[17:54] <arraybolt3[m]> sil2100: Are the nVidia problems with Secure Boot or just in general? (I ask because I need to know if I need to enable Secure Boot on my desktop before starting the install or not.)
[17:54] -queuebot:#ubuntu-release- Unapproved: openldap (jammy-proposed/main) [2.5.12+dfsg-0ubuntu0.22.04.1 => 2.5.13+dfsg-0ubuntu0.22.04.1] (i386-whitelist, ubuntu-server)
[17:55] <bdmurray> sil2100: my notes say in general
[17:55] <bdmurray> oops arraybolt3[m] ^^
[17:55] <arraybolt3[m]> 👍️ Thank you!
[17:58] <sil2100> Okay, did now ubuntu-mate, maybe I'll do a quick test of that on vm if it at least launches
[18:03] <arraybolt3[m]> Well I hit quite an interesting Nouveau bug so far (let's just say my screen is supposed to be a screen not a strobe light). Not sure if it's my fault or Nouveau's but it certainly wasn't right, that's for sure.
[18:05] <arraybolt3[m]> Thankfully I have a different screen that isn't going berzerk.
[18:05] <Eickmeyer[m]> arraybolt3: We've noticed on Kubuntu Focus hardware that we have to disable nouveau and get it to default to the integrated intel graphics to get it to work properly for installation.
[18:07] <arraybolt3[m]> Hmm. My particular desktop makes that a tricky proposition, but oh well. I think it might be my monitor cable's fault (DVI-to-HDMI cable, not sure which end is input and which end it output but it seems to work with DVI graphics card to HDMI monitor).
[18:08] <arraybolt3[m]> Oh dear. I just hit a possibly serious bug.
[18:08] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[18:08] <arraybolt3[m]> Start the installatoin, choose Erase Disk and install Ubuntu, click Install Now, then go back.
[18:08] <arraybolt3[m]> The installer won't allow you to go forward again.
[18:09] <Eickmeyer[m]> That sounds like a known Ubiquity bug I've seen reported before.
[18:09] <arraybolt3[m]> Oh wait, shook it into working. I had to go back one more time and then go forward.
[18:10] <bdmurray> Yes, that's a duplicate.
[18:10] <arraybolt3[m]> OK. And it had a workaround, so nevermind, we're good!
[18:18] <sil2100> If we find another release blocker now I'll go crazy
[18:20] <arraybolt3[m]> sil2100: Well I told it to install proprietary drivers at install time, but it's still on Nouveau.
[18:21] <sil2100> arraybolt3[m]: what image is that?
[18:21] <arraybolt3[m]> I'm gonna re-zsync, reflash if necessary, and reinstall just to confirm, but I think that's bad.
[18:21] <arraybolt3[m]> I think it's the latest one.
[18:21] <sil2100> And did you have the nvidia drivers installed with 22.04 the release images?
[18:21] <arraybolt3[m]> No clue, I'll test that too.
[18:22] <sil2100> We need to make sure it's the 20220809.1 image, and if it's  the same symptoms that basically kernel drivers are installed but not the nvidia packages
[18:22] <arraybolt3[m]> We'll know momentarily - zsync will tell me.
[18:23] <sil2100> What flavor was that?
[18:23] <arraybolt3[m]> (I know which ISO I flashed, I just am going to make sure it's the same one as the one you mentioned.)
[18:23] <arraybolt3[m]> Ubuntu Desktop.
[18:24] <sil2100> Did anyone here also try the 20220809.1 image with nvidia hardware besides me?
[18:24] <arraybolt3[m]> Crud, target 100% complete, fetched 0. This is indeed the 20220809.1 image
[18:24] <arraybolt3[m]> Reflash just in case it's my flash drive's fault.
[18:25] <sil2100> schopin: you still around?
[18:26] <sil2100> Is there anyone with Nvidia hardware who can test this too?
[18:26] <sil2100> Since I'll be pissed if I tested the wrong thing or something
[18:26] <arraybolt3[m]> I'll see if I can enlist some help from alternate locations.
[18:26] <sil2100> bdmurray: do you have some nvidia hardware?
[18:26] <sil2100> jawn-smith: maybe you?
[18:26] <Eickmeyer[m]> sil2100: I just got Kubuntu finished zsyncing, getting ready to test shortly.
[18:27] <Eickmeyer[m]> Nvidia hardware.
[18:27] <sil2100> I desperately need all-hands-on-deck here, since if this is still broken then "we're screwed"
[18:27]  * jawn-smith reads scrollback
[18:27] <bdmurray> sil2100: I'm looking
[18:28] <jawn-smith> My only nvidia hardware is my main development machine. If bdmurray doesn't have any I'll give it a shot installing to some other disk
[18:29] <arraybolt3[m]> We might also sound an alarm in -devel to see if anyone's there.
[18:29] <bdmurray> arraybolt3[m]: Could you confirm the sha256sum of the image you used?
[18:30] <arraybolt3[m]> My downloading tool auto-downloads and verifies the sha256sum, and it was OK.
[18:30] <arraybolt3[m]> I can paste the sum here if it's helpful though.
[18:30] <bdmurray> please
[18:30] <arraybolt3[m]> c396e956a9f52c418397867d1ea5c0cf1a99a49dcf648b086d2fb762330cc88d
[18:30] <sil2100> I'll also re-test the image in a moment, but I don't want to stop the repacking work
[18:31] <sil2100> arraybolt3[m]: do you have access to the install logs?
[18:31] <arraybolt3[m]> What all images are done? Kubuntu, MATE, is that all?
[18:31] <sil2100> arraybolt3[m]: can you share the syslog of the installer?
[18:31] <arraybolt3[m]> sil2100: Yes, actually!
[18:31] <arraybolt3[m]> One moment, powering test rig back on...
[18:32] <sil2100> I'm in the middle of doing Xubuntu, but I'm a bit stressed out that I'm doing this work for nothing as it's still broken
[18:33] <arraybolt3[m]> You want the whole /var/log/installer folder as a tar.gz, or just the syslog?
[18:33] <arraybolt3[m]> The syslog is here: https://termbin.com/wf3a
[18:35] <arraybolt3[m]> Also my system is still intact so if you want to gut it throw commands at me and I'll tell you what they do.
[18:37] <sil2100> It's like a different bug hm, no crash on the end, and I see nvidia-driver-515 installed
[18:37] <sil2100> Can you run `dpkg -l | grep nvidia` on the installed system?
[18:37] <bdmurray> jawn-smith: the laptop I thought might have nvidia does not
[18:38] <sil2100> jawn-smith: no need for you to break your running system, I'll quickly dd the image and give it a re-try
[18:39] <arraybolt3[m]> It gives no output.
[18:39] <arraybolt3[m]> (re: Can you run `dpkg -l | grep nvidia` on the installed system?)
[18:40] <arraybolt3[m]> sil2100: ^
[18:40] <sil2100> Then I have no idea what's going on, clearly those packages have been installed and not removed
[18:40] <jawn-smith> sil2100: I do have a spare hard drive I could install to
[18:43] <arraybolt3[m]> I'll do another reinstall and see if it works, it might just be a transient error.
[18:43] <Eickmeyer[m]> Kubuntu OEM test running now
[18:44] <sil2100> arraybolt3[m]: was that with network disabled?
[18:45] <arraybolt3[m]> Well... ish? I started the installer with network disabled, then realized I wanted the network and plugged in an Ethernet cable on the screen where it gave me the option to install updates. Then the box became available and I checked it to install the updates.
[18:45] <arraybolt3[m]> This time it's going to be network enabled the whole way through.
[18:45] <arraybolt3[m]> So installer started without network and then installed with network.
[18:46] <arraybolt3[m]> Also I hit "Try Ubuntu" first rather than "Install Ubuntu" since my screen was acting up at first and I was trying to fix it.
[18:46] <arraybolt3[m]> sil2100: ^
[18:47] <sil2100> It's still a valid test case. I was testing with no-network, since that's where the bug was appearing initially
[18:47] <arraybolt3[m]> And I had one time where I went back and then forward again. All in all, I'm realizing it was a really messy test.
[18:47] <sil2100> I'm worried I tested the wrong thing actually, dding the image now
[18:55] <Eickmeyer[m]> sil2100: Happy to report: Kubuntu OEM install worked, no crashes, Nvidia install worked, performed on network setup. Would you like me to try without network?
[18:57] <sil2100> Eickmeyer[m]: oh yes please! No network was where the bug was present, but a network one is also reassuring
[18:58] <sil2100> (since we know we didn't break anything at least)
[18:58] <arraybolt3[m]> Just finished my second installation.
[18:59] <jawn-smith> sil2100: what can I do to help?
[19:00] <jawn-smith> Is it worth swapping out my hard drives?
[19:00] <arraybolt3[m]> Alright, second test successful, proprietary driver in use immediately after installation. This time I did everything in an orderly fashion (boot, Install Ubuntu, proceed through as normal making sure to check the proprietary driver box, network available the whole time).
[19:00] <arraybolt3[m]> 515 driver is marked as in use in Software & Updates.
[19:01] <arraybolt3[m]> So now that raises a bunch of questions as to why my first installation borked.
[19:01] <arraybolt3[m]> I'm going to try a no-network install now.
[19:02] <arraybolt3[m]> Unless you want anything out of the system.
[19:02] <arraybolt3[m]> sil2100: ^
[19:09] <sil2100> Retested on my machine and it works
[19:10] <arraybolt3[m]> No-network install in progress on my machine.
[19:10] <sil2100> THank you! Yeah, it's still interesting re: what actually happened, but it's reassuring that a 'clean' install went fine
[19:10] <sil2100> phew
[19:10] <sil2100> Ok, continuuing with the repacking then
[19:11] <bdmurray> sil2100: see this log from Carlos https://launchpadlibrarian.net/617564276/syslog
[19:11] <bdmurray> and the "Failed to fetch cdrom://" line
[19:11] <Eickmeyer[m]> sil2100: No-network OEM without network on Nvidia: complete success.
[19:11] <Eickmeyer[m]> (Kubuntu)
[19:12] <arraybolt3[m]> bdmurray: Hash sum mismatch, sounds like an ISO or USB error to me.
[19:12] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[19:12] <arraybolt3[m]> https://pastebin.com/fkb4z4qV
[19:12] <sil2100> jawn-smith: I think we dodged a bullet with the issues so far
[19:12] <arraybolt3[m]> That's the part where I'm seeing the corrupted file in that log.
[19:12] <sil2100> Eickmeyer[m]: oh man, music to my ears
[19:12] <jawn-smith> sil2100: great news but I'll stand by
[19:14] <bdmurray> Aug 10 17:50:12 ubuntu casper-md5check[1887]: Check finished: errors found in 1 files! You might encounter errors.
[19:15] <arraybolt3[m]> Yep. Guessing we found that one file.
[19:15] <sil2100> uh oh, is that a download error or did I not update some checksum?
[19:16] <arraybolt3[m]> Since it's part of the 515 driver I'm guessing it's a download error since my system took the 515 driver no problems.
[19:16] <arraybolt3[m]> (speaking of which my system just finished up the install so we're about to see how it works)
[19:19] <arraybolt3[m]> My casper-md5check in my installer logs says "Check finished: no errors found."
[19:19] <bdmurray> What a bad coincidence - Aug 10 17:47:02 ubuntu casper-md5check[1887]: Checking ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.65.01-0ubuntu0.
[19:19] <bdmurray> 22.04.1_amd64.deb........./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.65.01-0ubuntu0.22.04.1_amd64.deb: mismatch
[19:20] <arraybolt3[m]> And the 515 driver installed properly.
[19:20] <arraybolt3[m]> So that's a successful no-network installation.
[19:20] <arraybolt3[m]> (one moment, my laptop is nagging me to reboot, brb)
[19:21] <Eickmeyer[m]> I'm doing a no-network Kubuntu end-user (regular) Nvidia install for good measure.
[19:22] <arraybolt3[m]> back online.
[19:23] <arraybolt3[m]> Network-enabled OEM installation in progress.
[19:25] <Eickmeyer[m]> sil2100: No-network regular (end-user) Kubuntu with Nvidia install success. Looks like Kubuntu 22.04.1 is a go, but I'll leave that up to RikMills since he's the RM.
[19:26] <RikMills[m]> Eickmeyer: can't test that at the moment for reasons yoiu know :(
[19:27] <RikMills[m]> I will take your word for it
[19:27] <Eickmeyer[m]> Rik Mills: Ok, want me to mark as ready (assuming I have the power)?
[19:27] <RikMills[m]> If you can, the yeah
[19:28] <sil2100> \o/
[19:28] <RikMills[m]> s/the/then/
[19:32] <sil2100> Ok, budgie done, only one left is kylin
[19:32] <Eickmeyer[m]> Bah, wouldn't let me mark Kubuntu as ready.
[19:32] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[19:34] <Eickmeyer[m]> Now this I can do...
[19:34] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy 22.04.1] has been marked as ready
[19:35] <Eickmeyer[m]> Rik Mills: I'm unable.
[19:35] <sil2100> I don't know what we'd be able to do without all the help, thank you flavors!
[19:35] <arraybolt3[m]> Syncing MATE now, I've got this and one more Ubuntu Desktop install and then I'm willing to say it's AOK on my hardware.
[19:36] <arraybolt3[m]> sil2100: We're all Ubuntu. This is the ultimate definition of "I am because we all are", don't you think? :)
[19:36] <Eickmeyer[m]> ^ This guy gets it.
[19:36] <sil2100> So true!
[19:37] <bdmurray> ;-)
[19:39]  * arraybolt3[m] has to go afk real quick
[19:47] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy 22.04.1] has been updated (20220809.1)
[19:47] <sil2100> Okay, I think that's all of them
[19:48] <sil2100> I'll now start doing the other releasey stuff, I'll pre-publish images regardless
[19:48] <sil2100> And update the tracking post
[19:48] <arraybolt3[m]> Should I focus on MATE or Kylin next?
[19:53] <arraybolt3[m]> (Or any other flavor really, I just want to make sure I make the best use of the time I have.)
[19:53] <bdmurray> I think MATE as Kylin people may show up to test.
[19:57] <fossfreedom> sil2100: yesterdays UB iso was 2.7G ... the latest is now 2.4G ... any ideas why?
[20:01] <sil2100> fossfreedom: ...it might be the removed _Packages files
[20:01] <arraybolt3[m]> Alright, back in action!
[20:01] <sil2100> fossfreedom: at least I noticed that the filesystem.squashfs after removing the files *and* repacking with mksquashfs weirdly was like 500MB-ish smaller
[20:01] <sil2100> Checked the diffs and the only differences were the removed _Packages files
[20:02] <sil2100> So I don't know if it's that or some better compression, dunno
[20:02] <fossfreedom> Ah. So expected I guess.  Sounds like a really good idea for the future.
[20:03] <sil2100> Expected, but I did not expect such big differences. That being said, I saw no other differences + the images seem to work as expected
[20:03] <sil2100> ...fameous last words
[20:03] <arraybolt3[m]> I'm guessing that's also why the zsync is taking so long to determine the delta between the old ISO and the new?
[20:04] <arraybolt3[m]> (Proprietary driver working on a network-enabled OEM install, Firefox launches out of the box)
[20:05] <sil2100> Again, music to my ears
[20:06] <fossfreedom> 'fraid just don't have any nvidia stuff myself to test but I will try a no network bcmwl based install
[20:07] <sil2100> fossfreedom: \o/
[20:07] <sil2100> The more varying tests the better!
[20:08] <arraybolt3[m]> fossfreedom: You're the Budgie guy, right? If so I can throw some Budgie testing into the mix.
[20:08] <sil2100> I might give kylin a spin later, but I first want to do some of the pre-publishing + other .1 prep suff
[20:08] <sil2100> 'The Budgie Guy', hahah, love it ;)
[20:09] <arraybolt3[m]> I figure Simon's the Lubuntu guy, Erich's the Studio guy, Rik's the Kubuntu guy, etc. I guess Mark Shuttleworth is the Ubuntu guy then?
[20:10] -queuebot:#ubuntu-release- New binary: openfst [amd64] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[20:11]  * cjwatson tries to remember when Mark last did image testing ;-)
[20:11] <cjwatson> Quite A While Ago I suspect
[20:11] <arraybolt3[m]> LOL
[20:11] <arraybolt3[m]> No-network OEM installation in progress.
[20:12] <arraybolt3[m]> (I guess I *should* say "flavor lead", but the term escaped me at the moment.)
[20:13] <RikMills[m]> <Eickmeyer[m]> "Rik Mills: I'm unable." <- doing now
[20:13] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.1] has been marked as ready
[20:13] <Eickmeyer[m]> Rik Mills: Awesome!
[20:13] <RikMills> ^^ :D
[20:13] <Eickmeyer[m]> sil2100: \o/
[20:14] <sil2100> Delicious!
[20:14] <arraybolt3[m]> ✔️ One down, only six to go!
[20:15] <RikMills[m]> Eickmeyer[m]: If studio is going to continue to use the KDE desktop, I think we need to work out some task and permissions sharing for out teams
[20:15] <RikMills[m]> possibly...........
[20:15] <Eickmeyer[m]> Rik Mills: Probably not a bad idea.
[20:15] <Eickmeyer[m]> Rik Mills: We've got a similar thing going on with Lubuntu due to Calamares.
[20:15] -queuebot:#ubuntu-release- New binary: openfst [s390x] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[20:18] <fossfreedom> arraybolt3[m]: Well that's the first time I have been called "the budgie guy" ... but yeah. Project lead. Much appreciated for your kind testing offer.
[20:19] <arraybolt3[m]> fossfreedom: Sorry, forgot the official title. OK, I'll sync Budgie too and throw it in the mix ahead of MATE to make sure it gets a good NVIDIA workout.
[20:20] <RikMills[m]> fossfreedom: I read that as the 'bungie guy'. Whoops. An image of someone going' boing boing' on elastic was in my head :P
[20:21] <fossfreedom> Lol
[20:22] <tumbleweed> 3/41
[20:22] <tumbleweed> grr
[20:24] -queuebot:#ubuntu-release- New binary: openfst [ppc64el] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[20:25] <sil2100> tumbleweed: what's up?
[20:27] <tumbleweed> typo switching windows :)
[20:27] <sil2100> tumbleweed: ;)
[20:27] <arraybolt3[m]> Alright, no-network OEM install also worked and has the NVIDIA driver running.
[20:34] <sil2100> \o/
[20:44] -queuebot:#ubuntu-release- New binary: openfst [armhf] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[20:49] <arraybolt3[m]> It dawns on me there's one more test I should do on Ubuntu itself (Try Ubuntu then install), since that didn't quite work the first time. Will report back soon.
[20:53] <sil2100> Thanks. I think I did that test on my original Ubuntu hacked-up-test-image and it worked, but who know
[20:53] <sil2100> *knows
[20:54] <arraybolt3[m]> I'm also doing my weird "start with no internet and then add internet later" thingy since it may apply to users with WiFi (where you *always* start without Internet and connect later).
[21:08] <arraybolt3[m]> Success! OK, so I guess my initial fail was just a random glitch or I did way more fiddling than normal.
[21:11] <sil2100> Awesome! The installer isn't very ekhm, resilient
[21:42] -queuebot:#ubuntu-release- New binary: openfst [arm64] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[21:46] <sil2100> arraybolt3[m]: hey! hm hm
[21:46] <bdmurray> Does somebody still have an OEM install?
[21:46] <arraybolt3[m]> Yeah?
[21:46] <arraybolt3[m]> bdmurray: Erm, I wiped mine, like, two installs ago...
[21:46] <sil2100> arraybolt3[m]: when you tested the OEM install feature today, did you try launching firefox via the icon or from the terminal?
[21:46] <arraybolt3[m]> sil2100: I'm here.
[21:47] <arraybolt3[m]> sil2100: I used the icon.
[21:47] <sil2100> bdmurray: ^
[21:47]  * bdmurray reboots
[21:47] <sil2100> Since Brian was seeing some weirdness when trying to launch firefox via the icon
[21:48] <sil2100> arraybolt3[m]: thanks for the info o/
[21:48] <arraybolt3[m]> I'm doing Ubuntu Budgie tests so I can do an OEM one next and report back whatever is necessary.
[21:48] <arraybolt3[m]> 👍️
[21:48] <fossfreedom> Firefox launch via oem install is OK on UB
[21:50] <sil2100> fossfreedom: \o/
[21:50] <sil2100> I think Brian just wants to find reasons for me to feel miserable and stressed
[21:50] <fossfreedom> Just happen to have done that. Oddly bcmwl network driver was not installer in oem mode. Was working yesterday.  Going to repeat to see if I forgot to check the proprietary driver option.
[21:51] <sil2100> He's probably like: "ah, sil2100 started feeling relaxed again, let's try finding something"
[21:51] <bdmurray> I'm feeling vilified
[21:51] <arraybolt3[m]> sil2100: Hey, what was that trick that reduced the image size by 500MB? ItzSwirlz is trying to shrink the Ubuntu Cinnamon image.
[21:52] <sil2100> bdmurray: nooo~
[21:52] <arraybolt3[m]> bdmurray: It's always sad to be the one who has to say something about some critical bug. I still feel a bit bad about bringing up the Secure Boot mess the other day...
[21:54] <sil2100> fossfreedom: that would be worrying if it wasn't installed... please give me a sign after you do another round of testing
[21:55] <sil2100> And I'm sure bdmurray knows that I'm just joking
[21:55] <fossfreedom> sure sure. It will be a while. It on an old macbook pro 2012
[21:55] <arraybolt3[m]> fossfreedom: My laptop has a bcmwl WiFi card. It may take me a while to get to the point of testing since that laptop also happens to be my primary rig, but I can still test it eventually.
[21:56] <arraybolt3[m]> (My USB stick even happens to have Budgie on it ATM, so this is good timing.)
[21:57] <bdmurray> I'm testing the OEM install again
[22:00] <arraybolt3[m]> Alright, Budgie + NVIDIA = 515 Driver successfully installed. Also, I'm shocked at how fast Firefox is starting now, it's like back to the good old apt days.
[22:06] <arraybolt3[m]> OK, /me may vanish for a bit while I rig my laptop for bcmwl testing on Budgie, brb.
[22:11] <sil2100> arraybolt3[m]: thank you for all your testing today o/
[22:12] <arraybolt3[m]> sil2100: No problem, glad to still be helping!
=== NotEickmeyer is now known as Eickmeyer
[22:20] <fossfreedom> sil2100: no oem + bcmwl issues found this time. So happy to tick that box.
[22:20] <sil2100> fossfreedom: you can't even imagine how relieved I am to hear this
[22:21] <sil2100> Now the only thing left is the potential issue bdmurray saw with the firefox snap after OEM install
[22:21] <sil2100> But seeing that it worked for a few other people, I'm a bit less worried - we can always document flakyness
[22:21] <fossfreedom> Since I am right there at the moment ... firefox launches just fine (again)
[22:22] <bdmurray> It was fine this time but I launched it once before clicking "Prepare for shipping to end user"
[22:26] <arraybolt3[m]> OK, got Budgie booting for my own test of OEM+bcmwl.
[22:26] <sil2100> \o/
[22:28] <sil2100> Okay everyone, I think this is it for me, I think I need to get some rest after this all-day-ride
[22:29] -queuebot:#ubuntu-release- New binary: openfst [riscv64] (kinetic-proposed/universe) [1.7.9-4ubuntu1] (no packageset)
[22:29] <sil2100> bdmurray: you're in charge! Also, please leave me a message later about your decision of go/no-go as the QA representative
[22:29] <sil2100> I asked Kent from Cert QA to do testing on the certified devices once again, hopefully I'll get some test results in the morning
[22:30] <sil2100> Also, we might need to poke some people to do smoke-testing for flavors that don't have test results today
[22:30] <sil2100> Would be grateful for that
[22:30] <sil2100> bdmurray: keep me in the loop please o/
[22:34] <sil2100> Goodnight
[22:51] <arraybolt3[m]> OEM+bcmwl+Budgie = success!
[23:07] <arraybolt3[m]> Alright, that's all the intensive testing I had in me for right now, I'll do some VM testing in the mean time and maybe some more intensive testing later tonight.
[23:13] -queuebot:#ubuntu-release- New binary: libtickit-app-plugin-escapeprefix-perl [amd64] (kinetic-proposed/none) [0.02-1] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: libtickit-widget-entry-plugin-completion-perl [amd64] (kinetic-proposed/none) [0.01-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: interception-tools [amd64] (kinetic-proposed/none) [0.6.8-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: libcommuni [amd64] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: interception-tools [ppc64el] (kinetic-proposed/none) [0.6.8-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: libcommuni [s390x] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: interception-tools [s390x] (kinetic-proposed/none) [0.6.8-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: libcommuni [ppc64el] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: interception-tools [riscv64] (kinetic-proposed/none) [0.6.8-1] (no packageset)
[23:50] -queuebot:#ubuntu-release- New binary: libcommuni [arm64] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:51] -queuebot:#ubuntu-release- New binary: libcommuni [riscv64] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:52] -queuebot:#ubuntu-release- New binary: libcommuni [armhf] (kinetic-proposed/universe) [3.7.0-2] (no packageset)
[23:55] -queuebot:#ubuntu-release- New binary: interception-tools [arm64] (kinetic-proposed/universe) [0.6.8-1] (no packageset)
[23:55] -queuebot:#ubuntu-release- New binary: interception-tools [armhf] (kinetic-proposed/universe) [0.6.8-1] (no packageset)