https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c1 Ignacio Areta changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |areta@outlook.com.br --- Comment #1 from Ignacio Areta 2013-11-21 05:41:41 UTC --- I can conffirm this bug. Just a 13.1 fresh install, without any package from Packman repository or Fluendo and Flash. When I go to a YouTube video like these https://www.youtube.com/watch?v=y1Q5YXe88sY https://www.youtube.com/watch?v=jjRAKuis7T8 And click on "Statics for nerds", the video type appears as mp4, using HTML5 (no Flash installed) If I go to Firefox, these videos doesn't appeas as MP4. Also, if I downloaded one of these videos with youtube-dl, I can reproduce it with Chromium, but Firefox and Totem refused to play it. This occurs because of these 2 lines in the chromium.spec package: Line 347 -Dproprietary_codecs=1 Line 349 -Dffmpeg_branding=Chrome According to the Chromium's wiki, when you use the -Dproprietary_codecs=1, you tell to the sites that H.264 and MP3 are supported. And when you use -Dffmpeg_branding=Chrome, this activates the support in fact. http://www.chromium.org/audio-video In my opinion, it would be much better if the packager stops to play with these non-default cflags. Problems in Chromium because of these type of games are frequently, and also, increases the complexity of builds (sorry for the critical). Also, I think this bug should be marked as critical, because openSUSE can't ship anything with support to proprietary codecs like H.264. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c3 --- Comment #3 from Ignacio Areta 2013-11-22 00:54:22 UTC --- (In reply to comment #2)

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.

From my point of view, to avoid chromium-ffmpegsumo from opeSUSE reproducing

I know why these flags are present. But... Re-read the bug report, re-read my comment. The bug report tells that chromium-ffmpegsumo from openSUSE is reproducing MP3 audio and MP4 video. And this occurs because these flags are present. If you have a scipt/patch/whatever to avoid the openSUSE's chromium-ffmpegsumo reproducing these formats, that script/patch/whatever isn't working. You marked this as wontfix. But did you try to reproduce this? No? So, install chromium-ffmpegsumo from openSUSE, enable HTML5 on YouTube and try to go to the links in comment 1, click with the right button on the video > Statics for nerds and see what's happening. Also, try this link too. I reproduced with suceess the MP3 file. http://hpr.dogphilosophy.net/test/ Get the fact: chromium-ffmpegsumo from openSUSE is reproducing MP3 and MP4 files, and not only showing them as supported. 2 users reproduced this bug with sucess. And chromium-ffmpegsumo from openSUSE is reproducing these files because of these two flags. So, closing this bug as wontfix can be risky to the future of Chromium in openSUSE. these formats, the solution is to not use these flags. Do you have another idea?

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.

I was doing some research about this some months ago because at that time there wasn't a stable version of Chromium at openSUSE. But as you started to package the stable version, I abbandoned the idea. But I can consider this again. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c5 --- Comment #5 from Ignacio Areta 2013-11-22 21:38:37 UTC --- (In reply to comment #4)

So what you are asking for is that Chromium will NEVER support H.264/MP4 or at least the package that one gets from openSUSE shouldn't support that. If users want to have that support they should go to get the official google-chrome package, which causes other issues as that they don't build against openSUSE.

According to the description of that package http://software.opensuse.org/package/chromium-ffmpegsumo?search_term=chromiu... These formats are not supported and if the user wants support to these formats, s/he must use chromium-ffmpeg from Packman. In theory, no poblem. But the issue is with openSUSE's chromium-ffmpegsumo. This is what the reporter of this bug and I are asking. We're using chromium-ffmpegsumo from openSUSE and we still are able to reproduce MP3 and MP4 in Chromium. Can you explain why it's happening?

You are aware that those are not runtime flags, but build flags ?[/quote]

Yes, I am.

If you feel that I should remove them, then I would kindly ask you to raise this discussion on the openSUSE-Factory mailinglist so that other people can comment on this too.

Everything has been reviewed by the legal team of openSUSE and found everything ok. This included even that the full ffmpeg source is intree, but only build against openSOURCE libraries. But maybe you know better than them, what can and cannot be done.

In that email you can also indicate that you are willing to take over the maintainership of chromium as that you can provide the right package without EVER supporting a number of codecs.

OK, I'll write to Factory ML. This really needs a new review from the legal team. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c7 Raymond Wooninck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|WONTFIX | AssignedTo|tittiatcoke@gmail.com |cfarrell@suse.com --- Comment #7 from Raymond Wooninck 2013-11-23 22:38:26 UTC --- Reassigning to Legal for review -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c9 --- Comment #9 from Raymond Wooninck 2013-11-27 09:31:30 UTC --- Ciaran, Nothing really changed regarding the enable flags for these codecs. They were always there, but I guess the became really available after the change that we had to build the ffmpeg lib for Chromium to build/work. I am not sure if that was before or after the release of 12.3. I will disable those flags. Side-effect is only that those codecs will not even be supported by the ffmpeg package on Packman. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c11 Cristian Morales Vega changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.morales.vega@gmai | |l.com --- Comment #11 from Cristian Morales Vega 2013-11-27 12:17:42 UTC --- I don't use Chromium, and it's the first time I listen about "ffmpegsumo". But since this reached the mailing list and I would like it to stop, and had a quick look into it. So, correct me if I am wrong: a) libffmpegsumo is just libavutil + libavcodec + libavformat build into a single library b) If libffmpegsumo is not available, the libavutil + libavcodec + libavformat from the system will be used. This is specified in media/base/media_posix.cc: --------------------------------------------------------------------------- bool InitializeMediaLibraryInternal(const base::FilePath& module_dir) { StubPathMap paths; // First try to initialize with Chrome's sumo library. DCHECK_EQ(kNumStubModules, 1); paths[kModuleFfmpegsumo].push_back(module_dir.Append(kSumoLib).value()); // If that fails, see if any system libraries are available. paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avutil", AVUTIL_VERSION))).value()); paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avcodec", AVCODEC_VERSION))).value()); paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avformat", AVFORMAT_VERSION))).value()); return InitializeStubs(paths); } --------------------------------------------------------------------------- c) libffmpegsumo has never depended on ffmpeg libraries. To have full multimedia support you need libffmpegsumo from Packman, not just ffmpeg. If so, IMHO there is no problem here. Just build the Chromium/libffmpegsumo version in openSUSE without the extra codecs (ffmpeg_branding != Chrome). And leave "proprietary_codecs" enabled (since it only affects what Chromium *claims* to support). Optionally, build in Packman libffmpegsumo with all the codecs supported. Result: - Chromium and libffmpegsumo from openSUSE Only "open" codecs are supported - Chromium and no libffmegsumo/ffmpeg libraries installed No codecs support at all - Chromium and libffmegsumo from Packman Full codecs support - Chromium and ffmpeg libraries from Packman (supposing they are compatible), with no libffmpegsumo at all Full codecs support The only question is how Chromium will behave when it claims to support a codec that it can't support. But I guess it will not be any user visible change. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c13 --- Comment #13 from Raymond Wooninck 2013-11-27 13:07:25 UTC --- Christian, Thanks for checking, but did you really expected that I wouldn't have checked that myself ? I never said that Chromium needs the ffmpeg library from Packman. Chromium itself contains the ffmpeg sources and builds in into the libffmpegsumo library. Depending on the build dependencies, you would get either a libffmpegsumo that just supports opensource codecs (like build on OBS) or one with full support (like I am building on Packman) Doing it your way, doesn't help as that the actual support for these codecs is not in the ffmpegsumo library. Also leave 1 flag out doesn't help the situation as that the build system, checks either one or the other, e.g. from media/media.gyp: ['proprietary_codecs==1 or branding=="Chrome"', { 'sources': [ 'mp2t/es_parser.h', 'mp2t/es_parser_adts.cc', 'mp2t/es_parser_adts.h', 'mp2t/es_parser_h264.cc', 'mp2t/es_parser_h264.h', 'mp2t/mp2t_common.h', 'mp2t/mp2t_stream_parser.cc', 'mp2t/mp2t_stream_parser.h', 'mp2t/ts_packet.cc', 'mp2t/ts_packet.h', 'mp2t/ts_section.h', 'mp2t/ts_section_pat.cc', 'mp2t/ts_section_pat.h', 'mp2t/ts_section_pes.cc', 'mp2t/ts_section_pes.h', 'mp2t/ts_section_pmt.cc', 'mp2t/ts_section_pmt.h', 'mp2t/ts_section_psi.cc', 'mp2t/ts_section_psi.h', 'mp4/aac.cc', 'mp4/aac.h', 'mp4/avc.cc', 'mp4/avc.h', 'mp4/box_definitions.cc', 'mp4/box_definitions.h', 'mp4/box_reader.cc', 'mp4/box_reader.h', 'mp4/cenc.cc', 'mp4/cenc.h', 'mp4/es_descriptor.cc', 'mp4/es_descriptor.h', 'mp4/mp4_stream_parser.cc', And these indicated sources, are the one that is building the support for the MP4 and H.264 stuff. With regards to the changes between 12.3 and 12.3:Update, I can indicate the following: The 12.3 package contains as well the flag "-Dproprietary_codecs=1", however the source back then pushed all the support into the ffmpegsumo library and things worked as we wanted it to work. The Packman package was required to get the proprietary codec support and the OBS package didn't even offer the libffmpegsumo. However since then Google changed it where codecs were moved around and the libffmpegsumo library is hardcoded required for Chromium to even start. Based on that I already moved the package to Packman, but with the help of Ludwig Nussel we were able to move it back as that OBS is allowed to have the ffmpeg sources as long as the full package is not build. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c15 --- Comment #15 from Raymond Wooninck 2013-11-27 13:26:52 UTC --- No I meant the codec support that was raised in the bug report. Those codecs will never be part of the ffmpegsumo library (wherever it is being build). I had my days with patching Chromium, which became a nightmare so I don't want to go into that same direction again. If Chromium without the proprietary codec support is becoming a browser that is unusable, then I will delete it from OBS and start building it on Packman. This would save a lot of headache. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c17 --- Comment #17 from Raymond Wooninck 2013-11-27 14:04:32 UTC --- I don't see any issue to build it without the ffmpeg_branding flag. When I looked at the code, I noticed that quite some stuff was build from the media directory. As that I am not a specialist in this area, I could only draw the conclusion that these codecs were incorporated from there. I have now adjusted all chromium packages to have just the proprietary_codecs=1 flag. For the Packman build I also use the ffmpeg_branding=Chrome flag, so lets see what is going to happen here. Thanks for the assistance -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c19 Alexander Bergmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abergmann@suse.com --- Comment #19 from Alexander Bergmann 2013-12-04 11:03:37 UTC --- Does that mean that openSUSE users who are not subscribed to the Packman repos will lose the capability to access video content on youtube and similar sites with the ongoing chromium update? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:2347:moderate -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|obs:running:2346:moderate |obs:running:2345:moderate -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|obs:running:2345:moderate |obs:running:2345:moderate |obs:running:2347:moderate |obs:running:2346:moderate -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c21 --- Comment #21 from Swamp Workflow Management 2013-12-23 14:04:25 UTC --- openSUSE-SU-2013:1927-1: An update that fixes 7 vulnerabilities is now available. Category: security (moderate) Bug References: 847971,854472,854473 CVE References: CVE-2013-6634,CVE-2013-6635,CVE-2013-6636,CVE-2013-6637,CVE-2013-6638,CVE-2013-6639,CVE-2013-6640 Sources used: openSUSE 12.3 (src): chromium-31.0.1650.63-1.21.1 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c23 --- Comment #23 from Swamp Workflow Management 2014-01-15 10:04:23 UTC --- openSUSE-SU-2014:0065-1: An update that fixes 43 vulnerabilities is now available. Category: security (moderate) Bug References: 847971,854472,854473 CVE References: CVE-2013-2906,CVE-2013-2907,CVE-2013-2908,CVE-2013-2909,CVE-2013-2910,CVE-2013-2911,CVE-2013-2912,CVE-2013-2913,CVE-2013-2914,CVE-2013-2915,CVE-2013-2916,CVE-2013-2917,CVE-2013-2918,CVE-2013-2919,CVE-2013-2920,CVE-2013-2921,CVE-2013-2922,CVE-2013-2923,CVE-2013-2924,CVE-2013-2925,CVE-2013-2926,CVE-2013-2927,CVE-2013-2928,CVE-2013-2931,CVE-2013-6621,CVE-2013-6622,CVE-2013-6623,CVE-2013-6624,CVE-2013-6625,CVE-2013-6626,CVE-2013-6627,CVE-2013-6628,CVE-2013-6629,CVE-2013-6630,CVE-2013-6631,CVE-2013-6632,CVE-2013-6634,CVE-2013-6635,CVE-2013-6636,CVE-2013-6637,CVE-2013-6638,CVE-2013-6639,CVE-2013-6640 Sources used: openSUSE 13.1 (src): chromium-31.0.1650.63-13.7 -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=847971 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:2346:moderate |obs:running:2346:moderate |obs:running:2347:moderate | -- You are receiving this mail because: You are on the CC list for the bug.