Ruarí Ødegaard

Ruarí Ødegaard's avatar
Ruarí Ødegaard
ruario_at_social.vivaldi.net@momostr.pink
npub1zc46...ywf4
I work in QA for #VivaldiBrowser and also handle much of the release process for desktop products. I generally favour very simple technologies that allow me to better understand and fix things. On the other hand Vivaldi is so powerful and permits so much flexibility, that I love it anyway. 😉 I am also a keen #unicyclist and a fan of other unusual simple cycles. #ActiveTransport for the win! 🚴 Pronouns: He/him/his searchable Cycling account: https://velocipederider.com/@ruari Oulipo account: https://oulipo.social/@ruario Vivaldi Version Tracker 🤖: https://social.vivaldi.net/@vivaldiversiontracker Vivaldi team member: https://vivaldi.com/team/
So I just discovered that proprietary media (H.264, AAC, etc.) was not working with the Snap version of @Vivaldi Browser on Linux—I mean .snap packages, not Snapshots. I found this out as I attempted to use the Snap version to play a video and it failed. I am on vacation at the moment and not really monitoring our forums or bug tracker right now. I addition I do not usually use the Snap at home personally, so this was just by chance. 😱 On investigating, it seems that on 2024-12-17T13:39:10.926512+00:00 (last Tuesday) the "chromium-ffmpeg" snap package that we use to provide support for proprietary media was updated by Canonical and version 115541 (which we were still using) was removed entirely. Since I can update things myself and most of my colleagues are likely asleep I have now switched the Vivaldi 7.0 Snap to use "chromium-ffmpeg-118887" (which Canonical offer now) and released this live as of 2024-12-23T00:03:01.156148+00:00. That seems to have resolved it for me. If anyone is using the Snap version of Vivaldi, could you also confirm (after a Snap refresh and a restart of the browser) that it works for you also. There is a test video (with sound) here for you to check against: #Snapcraft
For you Vivaldi users using Flathub who are wondering where the 7.0.3495.26 update is. I made the changes on a branch 3 hours back but I cannot make things live without a test build created by Flathub and there is quite a backlog on Flathub's buildbot instance right now. It looks like there was a massive rebuild of KDE packages. So again, the lack of update is not a reflection on how much I care about Flatpak, it is just delays inherent in the system used to roll out.