hi, Quoting Jeremy Bícha (2024-08-22 18:15:16) > On Thu, Aug 22, 2024 at 11:59 AM Johannes Schauer Marin Rodrigues > <jo...@debian.org> wrote: > > Quoting Jeremy Bícha (2024-08-22 17:49:40) > > > On Thu, Aug 22, 2024 at 11:45 AM Johannes Schauer Marin Rodrigues > > > <jo...@debian.org> 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! > If you use sbuild, you can add --profiles=noudeb,nocheck to speed up the > build for this case. Thankhs, I'll add those. The build is not the problem but testing it is. I do run Debian bookworm, so to test this, I'm using an SD-Card with Debian unstable on it that I flash every time... XD
signature.asc
Description: signature
