Control: tags -1 moreinfo Control: notforwarded -1 > This sure does look an awful like the upstream Mesa issue 13426 I've > referenced. I've rebuilt the Debian Trixie packages with https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37150 applied and the problem still occurs, so that's probably not it. I have noticed Mesa upstream adding workarounds for GTK 4 applications recently; maybe the issue is on their end. Many issues and commits use the same buzzwords that pertain to this bug, but since I don't know what they mean, I think I've exhausted my ability to do more detective work for now.
> the Mesa version in trixie-backports should still be affected and I ought to > confirm that I also upgraded all binaries of src:mesa to the Trixie backports version and didn't see any relief. > if that doesn't help, then I can fast-forward to whatever is in upstream > Git—and maybe use some LD_PRELOAD or LD_LIBRARY_PATH voodoo so I don't have > to deal with Debian packaging changes—and see if I can reproduce then. This might not be as easy as I thought. I don't know too much about Mesa; does one usually need to reboot (or at least restart the graphical session) for upgrades to take effect such that they might address this issue? Also Mesa uses modules of some kind in directories like /usr/lib/x86_64-linux-gnu/dri/, but I don't know what I need to do about that. I think I've hit a dead end, but largely due to lack of knowledge in this space and the high upfront cost to learning this subject. If anyone is daring enough to dig in, I can make arrangements for remote access to this machine such as by SSH.
signature.asc
Description: This is a digitally signed message part
