Adam Williamson

Huh, Fedora's SDL2 and libdecor both buildrequire pkgconfig(wayland-protocols), so I'm not sure why we wind up in GTK3 nevertheless. Will poke into it a bit.

guvcview with SDL backend uses GTK in two separate threads which is not valid, causes crashes on Wayland

Thanks Jonas! Sorry, I misunderstood the PR as meaning "the app will crash intentionally" or something equally bad, not "it'll fall back smoothly to some other decorations". I guess I'll check if Fedora's SDL can be built with wayland-protocols, too...

The problem started appearing on Fedora when the whole stack was native Wayland, I think. But according to the GTK devs, running GTK in two threads within the app is just fundamentally wrong and not supportable even if it happened to work in some configurations, they're not going to do anything to fix the crash. edit: and yeah, I guess SDL build could affect it. For instance, is arch's SDL actually built against libdecor? This bug will only happen with libdecor, as that's what causes SDL to use ...

The problem started appearing on Fedora when the whole stack was native Wayland, I think. But according to the GTK devs, running GTK in two threads within the app is just fundamentally wrong and not supportable even if it happened to work in some configurations, they're not going to do anything to fix the crash.

ah, forgot about this ticket. this eventually came back around on 'guvcview is doing something wrong', specifically using GTK in two threads - https://sourceforge.net/p/guvcview/tickets/77/ .

guvcview with SDL backend uses GTK in two separate threads which is not valid, causes crashes on Wayland

Frequent crashes in GTK CSS code when run as regular user