https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c2 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #2 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-11-21 06:58:02 UTC --- Ignacio, Thank you for the support that I am receiving from you. It seems to me that you are much better off with using the official Chrome package. At least there the packager is not "PLAYING" with all kind of flags in order to get a full working browser with all codecs supported. Please don't comment just you found something on a wiki side, without knowing why these flags have been set. If you install the corresponding chromium-ffmpeg package from Packman, then the Chromium is providing this full support. Those two flags are required to have full support for those codecs in Chromium. I can leave them out, yes, but that would mean that the Chromium package will never support H.264 nor mp4, etc. Whether you install the chromium-ffmpeg package from packman or not. At that moment you would be forced to switch to the official Chrome package. This has been the situation ever since Chromium was build for openSUSE. Also your last paragraph shows how much you understand the package as that those codecs are shipped through the ffmpeg package on Packman. The ffmpegsumo package that comes with openSUSE actually only support the opensource codecs. So the proper bug report would be that chromium without the anything from Packman pretends to be able to play certain proprietary codecs which it actually can't. But hey, if you have the feeling that you can provide a better Chromium package, that you are more than welcome to take over the maintainership. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.