[00:00] <jbicha> the webkit2gtk amd64 build might work when we aren't building and autopkgtesting so much stuff, but I'll probably update https://salsa.debian.org/webkit-team/webkit/-/merge_requests/9 for amd64 too tomorrow
[00:00] <ubottu> Merge 9 in webkit-team/webkit "Reduce the number of parallel build jobs on Ubuntu's arm64" [Closed]
[00:01] <Eickmeyer[m]> jbicha: Oh, ok. I have reason to believe it's all related.
[00:07] <jbicha> Eickmeyer[m]: not sure what you mean. But anyway, there are multiple issues with the new mesa. If you're using Intel, this may help: https://launchpad.net/ubuntu/+source/intel-media-driver/22.2.1+dfsg1-1build1
[00:08] <jbicha> it didn't fix my issue but it helps other people :)
[00:08] <Eickmeyer[m]> jbicha: Actually, I'm on both Intel and Nvidia (hybrid laptop).
[00:10] <jbicha> I don't know how to troubleshoot that, but please add details about your graphics cards to that bug
[00:11] <jbicha> if you want to see if your issue was triggered by the new mesa, see my Planet Ubuntu post
[00:13] <Eickmeyer[m]> jbicha: Well, I did attempt to install intel-media-va-driver from proposed, and there was no change in behavior, so I'm not sure it's that.
[00:15] <jbicha> log out and log back in if you didn't. But the rebuilt intel-media-va-driver didn't help me either
[00:16] <Eickmeyer[m]> Yeah, no dice on the relog.
[00:17] <Eickmeyer[m]> ALTHOUGH, this time Evolution showed a crash.
[00:32] <Eickmeyer> jbicha: It's wayland-related.
[08:53] <tjaalton> systemd-timesyncd is installed by default on jammy and up?
[09:01] <seb128> tjaalton, it was already in the focal manifest for desktop
[09:01] <seb128> so not new
[09:02] <tjaalton> oh
[09:03] <tjaalton> I don't have it installed
[09:03] <seb128> tjaalton, sudo apt install ubuntu-desktop^ :)
[09:03] <tjaalton> though I probably used 19.10 to install
[09:04] <Unit193> Huh, thought chrony was, OK.
[09:16] <cpaelzer> Unit193: chrony is the default if you need a time-server or the more sophisticated behavior of chrony
=== st13g is now known as crisdel
[12:02] <ahasenack> morning
[16:04] <bdmurray> seb128: Will the desktop team be looking at bug 1966317?
[16:04] <ubottu> Bug 1966317 in gvfs (Ubuntu) "gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()" [Undecided, New] https://launchpad.net/bugs/1966317
[19:38] <mwhudson> for go snap users btw https://twitter.com/mwhudson/status/1508964109274218501
[19:41] <rbasak> ubuntu-devel-announce@ moderation please
[20:04] <bdmurray> rbasak: I'll do the moderation
[20:07] <mwhudson> dbungert, mclemenceau, bdmurray: apparently i can't access any canonical system currently, i think my ISP has messed up their routing or something
[20:08] <mwhudson> oh nm
[20:28] <rbasak> Thanks!
[20:40] <rbasak> !dmb-ping is ddstreet, rbasak, sil2100, teward, bdmurray, kanashiro, seb128: DMB ping
[20:40] <ubottu> But 'dmb-ping' already means something else!
[20:40] <rbasak> ?
[20:41] <rbasak> Unit193: ^ help please?
[20:44] <teward> !no dmb ping is ddstreet, rbasak, sil2100, teward, bdmurray, kanashiro, seb128: DMB ping
[20:44] <ubottu> I know nothing about 'dmb ping' yet, teward
[20:44] <teward> oops
[20:44] <teward> !no dmb-ping is ddstreet, rbasak, sil2100, teward, bdmurray, kanashiro, seb128: DMB ping
[20:45] <teward> rbasak: ops just has to approve it
[20:46] <rbasak> Thanks!
[21:13] <tomreyn> rbasak, teward: that's updated
[21:13] <teward> tomreyn: thank you!
[21:13] <tomreyn> you're welcome :)