ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
steven has joined #zink
<fdobridge> <O​wo> @ermine1716 do you remember what GPU you were using here? it was an Intel one, right, on ANV?
<fdobridge> <e​rmine1716> Yes
eukara has quit []
<fdobridge> <O​wo> @gfxstrand so, reproducible across sway, gnome, KDE, and anv, radv, and nvk
<fdobridge> <O​wo> :hammy:
<fdobridge> <S​id> :Pain:
<fdobridge> <g​fxstrand> Thanks! That's not surprising and I think that pretty well narrows it down to a Zink+EGL issue which is what I kinda figured it was based on the bug report. I'll look at it on Monday and see if I can figure out where things are going sideways.
<fdobridge> <O​wo> :ferrisCowboyRTX:
<fdobridge> <g​fxstrand> It's a little annoying that the reproducer is Firefox but I guess that's no worse than the last sync issue I fixed where the #1 reproducer was Chrome. 🤷🏻‍♀️
<fdobridge> <O​wo> Zink is bound to hit more than a few bugs in browsers
<fdobridge> <O​wo> the good part is, you don't need any specific hardware to reproduce it
<fdobridge> <O​wo> the bad part is, you don't need any specific hardware to reproduce it
<fdobridge> <g​fxstrand> Hehe
odrling has quit [Remote host closed the connection]
odrling has joined #zink