[00:05] <arraybolt3> mmikowski: Somewhat bad news on the Chrome front - despite having Vulkan enabled, I have the bug back again. Will need to reboot Chrome and maybe the computer to check, but I thought I should mention that. Only noticed it on Nightcafe though, not on Reddit, so I think things have at least improved.
[02:03] <mmikowski> arraybolt3: Hmmm. It's a bit of a hack; I'll let you know when we know more.
[02:04] <mmikowski> vorlon: "We don't ship Chrome" <= Understood. Just thought you'd want to know since so many users download it. It may also affect Chromium, but I haven't checked (yet).
[04:22] <mmikowski> arraybolt3: Just ran this again today. Again enabling vulkan worked. However, I found that one does need to cold-restart chrome sometimes. Just clicking the full reload doesn't seem to work.
[04:24] <arraybolt3> Hmm, good to know. I'll fully "power-cycle" it rather than just using the "Restart" button it gives me.
[04:35] <vorlon> ginggs: hadn't noticed that 3.10.10-2 had been synced before I deleted.  Anyway, as doko notes we don't need any of these in lunar release
[05:03] <ginggs> vorlon: right, but you wanted to get 3.10.10-1 out of -proposed, and now it's stil there
[05:03] <vorlon> oh joy
[05:04] <vorlon> re-removing :/
[05:04] <vorlon> didn't notice the removal managed to delete -2 *before* it superseded -1 :/
[05:04] <ginggs> vorlon: thanks
=== sem2peie- is now known as sem2peie
[19:23] <adrien> morning, could someone trigger the retries at https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=livecd-rootfs&trigger=xz-utils%2F5.4.1-0.2 ; https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=lintian&trigger=xz-utils%2F5.4.1-0.2 ;
[19:23] <adrien> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=epson-inkjet-printer-escpr&trigger=xz-utils%2F5.4.1-0.2 ; https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=cmake&trigger=xz-utils%2F5.4.1-0.2 ; https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=cmake&trigger=xz-utils%2F5.4.1-0.2
[19:24] <adrien> I expect them to be transient errors
[20:53] <vpa1977> Hi, would it be possible to retry https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=gtk%2B3.0&trigger=harfbuzz%2F6.0.0%2Bdfsg-3build1, I have ran autopkgtest locally and it passes.
[22:20] <vorlon> vpa1977: done
[22:24] <vorlon> adrien: why do you expect them to be transient?  fwiw the livecd-rootfs failure required un-breaking debootstrap in lunar, which required lsb-release-minimal to migrate
[22:24] <vorlon> adrien: so given that this was not merely transient, I'd like more info about why you expect the tests to now succeed, before adding them to the amd64/arm64 queues which are still struggling
[22:25] <vpa1977> vorlon: Thank you !!!
[23:26] <tsimonq2> jawn-smith: Hi, friendly reminder to unsubscribe ~ubuntu-sponsors from a bug once it's sponsored, thank you for your work there :)
[23:30] <arraybolt3> Quick reminder about bug 1989163, a fix for it in all flavors other than Lubuntu has been sitting in Unapproved for a month.
[23:30] -ubottu:#ubuntu-devel- Bug 1989163 in xscreensaver (Ubuntu Kinetic) "Unable to run screensaver when selected from menu" [High, In Progress] https://launchpad.net/bugs/1989163
[23:30] <arraybolt3> Also, I'm realizing how this got missed - because of it's dual-fix nature (one fix for Lubuntu, one fix for everything else), the SRU team got unsubscribed incorrectly after only one of the two fixes got through.