Ok, this was introduced upstream somewhere between 2.36.0 (jammy release) and 2.44.0 (jammy-updates). webkit2gtk now detects whether gbm_bo_create_with_modifiers2 exists at build time; if so, it uses them.
This is not a problem for the main archive, as the libgbm that mesa provides includes those symbols, but some proprietary drivers include their own libgbm (notably, here, the ARM MALI drivers) and this change has accidentally and silently broken the effective driver ABI for Ubuntu 22.04. In this case here it seems like it will be easy enough to patch the code to dynamically resolve gbm_bo_create_with_modifiers2 - the upstream code already has an implementation for where this is not available at build time. That's not an archive-wide solution, though. It's not *entirely* obvious to me whether this should be considered an SRU regression - I'm inclined to think so, but I don't hold that opinion strongly. I'll take the temperature of the SRU team on this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
