Hi, Quoting Johannes Schauer Marin Rodrigues (2024-08-22 18:43:31) > Quoting Jeremy Bícha (2024-08-22 18:15:16) > > On Thu, Aug 22, 2024 at 11:59 AM Johannes Schauer Marin Rodrigues > > <[email protected]> wrote: > > > Quoting Jeremy Bícha (2024-08-22 17:49:40) > > > > On Thu, Aug 22, 2024 at 11:45 AM Johannes Schauer Marin Rodrigues > > > > <[email protected]> wrote: > > > > > Rebuilding src:gtk+3.0 with this patch fixes the issue: > > > > > > > > Thank you. I agree with bumping the severity. Do you have time to > > > > bisect and figure out which specific patch is broken? This would be > > > > very helpful upstream so that the problematic commit does not make it > > > > into the next stable gtk3 release. > > > > > > I do not have a lot of time. Maybe we can share the work? If you have a > > > hunch > > > which of the commits could be the likely culprit, I'll test out just > > > dropping > > > that one. Bisecting six commits needs 3 tries anyways. :) > > > > These 4 all do things with windows: > > > > wayland-Add-support-for-v2-of-xdg_foreign-protocol.patch > > Ensure-the-staging_cairo_surface-is-destroyed-before-re-a.patch > > a11y-Use-non-empty-message-dialog-title-as-a11y-name.patch > > immulticontext-Don-t-have-a-global_context_id.patch > > thank you, that helps!
I now built four libgtk-3-0t64 packages. Each of them identical to what is currently in unstable except, each of them has one of above four packages *not* applied. I tried this in a vanilla Debian unstable system booted from SD-card on my arm64 laptop and the only package where the bug did *not* surface was the package that I built without wayland-Add-support-for-v2-of-xdg_foreign-protocol.patch I hope that helps! cheers, josch
signature.asc
Description: signature
