Hello and a Merry Christmas to you all!
It happened about a week ago:
we (all, I guess) received an update to Chromium - you just can’t dodge if you are a responsible guy, this as it is a security update and there are more than 25 security fixes, many dubbed important/critical;
I was happily using chromium-ffmpeg (I guess from the Packman repo? read bellow, I can’t find it anymore);
but as always, when a Chromium update comes out, this package lags behind and I have to switch to chromium-ffmpegsumo (vendor openSUSE);
problem is, when resolving the conflict I had very poor choices:
downgrade Chromium and use chromium-ffmpegsumo - neah, read above;
uninstall everything ffmpeg Chromium related and totally drop the fun part of the web.
weird thing is, I had to uninstall the chromium-ffmpeg; but it disappeared completely from the repos! Did something happened? I can only get chromium-ffmpegsumo, the partial implementation, but as I said, for an older version of Chromium.
Well, I figured “no one will leave me without A&V in the browser during holidays”, right ? But when searching the forums I saw very few posts, related to Chromium and ffmpeg, so maybe it’s just me.
So, there is a bit of info about “Obsolete ffmpeg and ffmpegsumo package in addition to conflict” in the Change Log tab, and further searches on the web suggest that Chromium should use the system ffmpeg now. Of course I have it installed from Packman:
**openSUSE:/home/fakemoth #** zypper search -id ffmpeg
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
i | ffmpeg | Library for working with various multimedia formats | package
i | libavcodec56 | FFmpeg codec library | package
i | libavcodec57 | FFmpeg codec library | package
i | libavdevice57 | FFmpeg device library | package
i | libavfilter6 | FFmpeg audio and video filtering library | package
i | libavformat56 | FFmpeg's stream format library | package
i | libavformat57 | FFmpeg's stream format library | package
i | libavresample3 | FFmpeg alternate audio resampling library | package
i | libavutil54 | FFmpeg's utility library | package
i | libavutil55 | FFmpeg's utility library | package
i | libpostproc53 | FFmpeg post-processing library | package
i | libpostproc54 | FFmpeg post-processing library | package
i | librtmp1 | RTMP Stream Dumper Library | package
i | libswresample1 | FFmpeg software resampling library | package
i | libswresample2 | FFmpeg software resampling library | package
i | libswscale4 | FFmpeg image scaling and colorspace/pixel conversion library | package
i | openSUSE-2016-1288 | Recommended update for chromium | patch
i | openSUSE-2016-1292 | Security update for Chromium | patch
i | openSUSE-2016-1365 | Security update for ffmpeg | patch
i | openSUSE-2016-1453 | Security update for Chromium | patch
i | vlc | Graphical media player | package
Whenever you post a list of your repositories always include the URLs. The URL is the deciding item to tell what the repository is. All other items like Name and Alias are pure local identifications. You can make them what you want and on other systems they may be different for the same repos.
the chromium-ffmpeg and chromium-ffmpegsumo packages have been depreciated now chromium uses the system ffmpeg by default no need for extra packages
also pepper-flash has been renamed to flash-player-ppapi you need to manually install it as an update might remove it
chromium 55 plays both html5 and flash video’s fine for me
I have no idea why you still have chromium-ffmpegsumo remove that package as it does not work with chromium 55 nor is it needed
do a full vendor change to packman and then force install of flash-player-ppapi
Yes, not too many posts on this. So I suppose most people worked it out.
I first saw it on Tumbleweed, which wanted to uninstall “chromium-ffmpeg”. So I skipped that part of the the update, and updated everything else. Then I decided to go back and retry, and do the chromium update.
The thing is that I had already heard (maybe on the factory mailing list), that chromium 55 would use “ffmpeg” directly without the need for “chromium-ffmpeg”. So I gave that a try. And I tested it, including the youtube html5 tests. And all worked well.
So when a similar update came out for Leap a few days later, I already knew how to handle it. And then came the flash changes. And, again, everything seemed to work.
So yes, a Christmas gift from the chromium developers.