Hi, vivaldi package maintainer here. We built the package for core24 yesterday as an effort to side-step the chromium-ffmpeg needing a new glibc not available in core22 and had to roll back the changes and rebuild with core22, as the core24 build manifested a problem with lacking plug connections for gpu-2404 and gnome-46-2404. Local builds do not manifest this, they autoconnect, so my limited testing via local build didn’t reveal a problem would happen when building via the provided services. (Don’t know for sure now as it was an intense time yesterday but I think it was build revision 325 of vivaldi that was core24)
Is there a way to fix this on the ubuntu snapcraft side or is there something we have to hotfix? We compared the snap declaration with chromium, which has no explicit plug declarations for those and yet works.
While I can’t help directly with the gpu-2404 auto-connection issue (which indeed sounds like a Store assertion that needs updating for the core24 base transition), I wanted to share some findings from a recent migration I did for a video processing app on core24.
Once you get the plugs connected, if Vivaldi relies on the system’s VA-API stack (Intel iHD driver) provided by the gnome extension/core24, you might hit a runtime crash.
The Context: We found that core24 currently ships a very recent Intel iHD driver that requires symbols (vaMapBuffer2) not present in the system’s older libva (v2.20). This causes immediate crashes or fallback to software rendering on Intel gen12+ hardware.
The Workaround: If you encounter this, we successfully stabilized the stack by manually bundling libva 2.22 (from Debian Sid) via override-build and pointing LD_LIBRARY_PATH to it, essentially bypassing the core24 system library while keeping the newer drivers.
It’s a bit of a “Frankenstein” approach, but it results in a fully functional HW accelerated stack (NVENC + VA-API) on core24.
Just a heads-up in case you solve the plug issue but suddenly face media playback regressions! Good luck with the migration.
