[06:54] <|N3on21|> Hello How can I keep the same password on my remote ubuntu client after reboot... It changes after every reboot.  
[07:36] <tjaalton> who's the maintainer of chromium snap?
[07:37] <nteodosio> tjaalton, nteodosio
[07:37] <tjaalton> nteodosio: hi :)
[07:37] <nteodosio> hey :) I just saw the mesa bug
[07:37] <tjaalton> ah good, was just about to let you know
[07:38] <tjaalton> so this is an upstream issue afaik
[07:52] <nteodosio> tjaalton, while the issue isn't fixed upstream would it make sense as a stopgap measure to simply remove GPUCache at every launch?
[07:56] <nteodosio> It seems that all reporters are on Chrome itself though, so we couldn't do that there.
[07:59] <tjaalton> yeah clearing the cache would be fine I think
[08:50] <lissyx> jbicha, I still dont see a libmutter-12 on lunar-proposed
[08:50] <lissyx> https://packages.ubuntu.com/search?keywords=libmutter-12-0
[08:50] <lissyx> only lunar-updates
[09:44] <duflu> Is packages.ubuntu.com meant to show proposed? It's visible on https://launchpad.net/ubuntu/+source/mutter
[09:47] <ogra> you can probably ask the community person that runs it to include proposed
[09:47] <ogra> IIRC there is a bug report button at the bottom 
[09:47] <ogra> (beyond that it is "Rhoda", active in #ubuntu-motu if you want a more direct conversation)
[09:47] <duflu> That was really an answer. Not a question
[09:48] <ogra> oh, heh ... sorry, missed the backlog
[12:15] <KGB-0> gnome-software signed tags 81b053b Jeremy Bicha upstream/44.2 * Upstream version 44.2 * https://deb.li/H26y
[12:15] <KGB-2> gnome-software pristine-tar 262fb70 Amin Bandali gnome-software_44.2.orig.tar.xz.delta gnome-software_44.2.orig.tar.xz.id * pristine-tar data for gnome-software_44.2.orig.tar.xz * https://deb.li/3onW2
[13:13] <KGB-0> gtk4 ubuntu/master e08b880 Till Kamppeter debian/ control control.in rules * Switch from the CUPS print backend to CPDB * https://deb.li/3kbqd
[13:13] <KGB-0> gtk4 ubuntu/master f4fdadb Jeremy Bicha debian/ control control.in * Depend on cpdb-backend-cups * https://deb.li/iWnwV
[13:33] <lissyx> well I have lunar-proposed enabled, I see the package in "apt-cache policy libmutter-12-0" but it's not updating to it so I guess a dep is missing?
[14:04] <jbicha> lissyx: Starting with 22.10, proposed updates aren't installed by default even when enabled
[14:04] <lissyx> ok
[14:04] <lissyx> that's weird but why not
[14:05] <lissyx> any setting  to change back the behavior?
[14:05] <lissyx> I dont really like having to "apt install -t lunar-proposed
[14:05] <jbicha> generally, people just want to test a specific fix they are interested in and not everything that needs verification
[14:08] <lissyx> that's some way of seeing it, I was more looking at "early beta tester" but no problem
[14:08] <lissyx> so no setting to change back?
[14:10] <jbicha> What I do is steps 1-3 from https://jeremy.bicha.net/2022/03/29/how-to-install-a-bunch-of-debs/
[14:11] <jbicha> for step 2, it's pull-lp-debs mutter lunar-proposed (you'll also want gnome-shell & gtk4 for this update)
[14:12] <lissyx> that makes things really complicated :(
[14:14] <jbicha> it's a little more reliable that  -t lunar-proposed  because it ensures I get the other packages built from source instead of just the main package
[14:14] <jbicha> than
[14:14] <jbicha> Correction, from reading the ubuntu-devel list, it looks like this change was new for 23.04
[14:16] <jbicha> I don't know how to undo the behavior change on your computer
[14:16] <jbicha> https://wiki.ubuntu.com/Testing/EnableProposed explains one way to opt into that behavior but it hasn't been updated to show how to opt out after the default behavior changed
[15:07] <chiluk> Is anyone else getting really strange artifacting after recent updates?  I fear their may be a regression in mesa, but I'm not sure how to prove that.
[15:14] <jbicha> chiluk: what version of Ubuntu are you using?
[15:14] <chiluk>  jbicha... I'm on jammy.  
[15:15] <chiluk> yeah looks like all my mesa related libraries were updated to 22.2.5-0ubuntu0.1~22.04.2  this morning.
[15:15] <nteodosio> chiluk, where do you see the problem?
[15:15] <chiluk> the only other thing my system upgrade was the kernel, but I've already rolled the kernel back to 6.1.0-1012-oem
[15:15] <chiluk> nteodosio: mostly in chrome
[15:16] <nteodosio> We have bug 2020604
[15:16] -ubottu:#ubuntu-desktop- Bug 2020604 in chromium-browser (Ubuntu) "After mesa upgrades, Chrome won't show graphics" [Undecided, Fix Committed] https://launchpad.net/bugs/2020604
[15:16] <nteodosio> Yeah that's it
[15:16] <chiluk> yep that's probably it.
[15:16] <nteodosio> Well just try --disable-gpu for now.
[15:17] <chiluk> yuck... why aren't you folks just rolling back the mesa upgrade?
[15:17] <chiluk> it basically makes chrome pretty unusable.
[15:17] <chiluk> graphics not showing up at all.. 
[15:19] <nteodosio> I don't know the decision process for Mesa.
[15:20] <nteodosio> I rebuilt Chromium with a workaround (on --candidate), but of course Google Chrome is not under our control.
[15:22] <chiluk> I'd have to look at the changes, but shipping a library change that breaks applications is typically a big no-no.  @tjaalton what's the plan here?
[15:28] <chiluk> I'm catching up on the ticket, what's the right solution to this?  Do we need to get changes in chromium to better handle mesa updates?
[16:47] <tjaalton> chiluk: even a no-change rebuild of mesa would invalidate the cache because GL_RENDERER string changes
[16:52] <tjaalton> chiluk, jbicha: the mesa update wil be pulled out from updates for now
[16:53] <ahasenack> in lunar, chrome, chrome://gpu shows GL_RENDERER=ANGLE (Intel, Mesa Intel(R) Graphics (ADL GT2), OpenGL 4.6 (Core Profile) Mesa 23.0.2)
[16:54] <ahasenack> so a mesa version bump, even a patch-level one, would change that string?
[16:57] <tjaalton> apparently, this seems to affect all distros
[16:58] <tjaalton> hmm
[16:59] <tjaalton> there's probably something else then, that string doesn't change actually
[17:01] <tjaalton> but it would change after booting a new kernel, though it was tested that mesa revert fixed it
[18:31] <KGB-2> gtk4 signed tags f8662a8 Jeremy Bicha ubuntu/4.10.3+ds-1ubuntu3 * gtk4 Debian release 4.10.3+ds-1ubuntu3 * https://deb.li/3S3Cg
[19:41] <chiluk> tjaalton in case you weren't already aware the clearing cache workaround seems to have resolved at least my issue.  I just with there was some way we could automate this.