Unable to view HTML5 after installing codecs.

English Multimedia
#1

Hi,

I’ve just recently installed 13.1 after staying on Ubuntu 14.04 for so long, but I missed my KDE so I made the switch.

Anyways, after adding the One-click install codecs (with the packman repo), HTML5 videos still fail to play in Chromium. They seem to be able to play in Firefox using HTML5 but not Chromium.

Here is the HTML5 page in Chromium: http://i.imgur.com/u4O99Lf.png

Here is the HTML5 page in Firefox: http://i.imgur.com/excJe5G.png

In order to have videos play in general, I’ve defaulted to using Chromium-pepper-flash to play videos, but would prefer to use the HTML5 player. I also installed the Chromium-ffmpeg codec from the repositories as well and that did not seem to have any effect. I have tried uninstalling chromium and reinstalling the codecs first then Chromium but to no avail. If any further info is needed I will happy to oblige. Thank you.

#2

Well, KDE is available on Ubuntu, too… :wink:

In order to have videos play in general, I’ve defaulted to using Chromium-pepper-flash to play videos, but would prefer to use the HTML5 player. I also installed the Chromium-ffmpeg codec from the repositories as well and that did not seem to have any effect. I have tried uninstalling chromium and reinstalling the codecs first then Chromium but to no avail. If any further info is needed I will happy to oblige. Thank you.

Installing “chromium-ffmpeg” should suffice.
Please post the list of chromium packages you have installed, maybe there’s a mismatch:

rpm -qa | grep chromium

Also, please post your repo list:

zypper lr -d

Having both the Packman and VLC repo may/will break your multimedia support.

Anyway, a “full repository vendor change update” to the Packman repo will probably fix your problem.
See here for how to do that: https://en.opensuse.org/SDB:Vendor_change_update#Full_repository_Vendor_change

#3

Hey thanks for the reply! Here are my answers!

Results of Chromium grep:

peter@linux:~> rpm -qa | grep chromiumchromium-36.0.1985.125-41.1.x86_64
chromium-pepper-flash-15.0.0.152-1.1.x86_64
chromium-desktop-kde-36.0.1985.125-41.1.x86_64
chromium-pdf-plugin-15.0.0.152-1.1.x86_64
chromium-ffmpeg-37.0.2062.120-671.1.x86_64
chromium-suid-helper-36.0.1985.125-41.1.x86_64

Repo list:

sudo zypper lr -d
root's password:
#  | Alias                     | Name                               | Enabled | Refresh | Priority | Type   | URI                                                                               | Service
---+---------------------------+------------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------------------------+--------
 1 | Google-Chrome             | Google-Chrome                      | Yes     | No      |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                               |        
 2 | KDE:Frameworks5           | KDE:Frameworks5                    | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.1/         |        
 3 | KDE:Qt5                   | KDE:Qt5                            | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.1/                 |        
 4 | Packman Repository        | Packman Repository                 | Yes     | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.1/                          |        
 5 | X11:Cinnamon:Factory      | X11:Cinnamon:Factory               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/X11:/Cinnamon:/Factory/openSUSE_13.1/   |        
 6 | dvd                       | dvd                                | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/13.1/                                              |        
 7 | google-chrome             | google-chrome                      | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                               |        
 8 | home:XRevan86             | home:XRevan86                      | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/XRevan86/openSUSE_13.1/           |        
 9 | home:XRevan86:non-free    | home:XRevan86:non-free             | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/XRevan86:/non-free/openSUSE_13.1/ |        
10 | home:andykimpe            | home:andykimpe                     | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/andykimpe/openSUSE_13.1/          |        
11 | libdvdcss repository      | libdvdcss repository               | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/13.1/                                              |        
12 | multimedia:libs           | multimedia:libs                    | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_13.1/         |        
13 | openSUSE:13.1             | openSUSE:13.1                      | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/13.1/standard/                |        
14 | repo-debug                | openSUSE-13.1-Debug                | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/13.1/repo/oss/                    |        
15 | repo-debug-update         | openSUSE-13.1-Update-Debug         | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/13.1/                                   |        
16 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/13.1-non-oss/                           |        
17 | repo-non-oss              | openSUSE-13.1-Non-Oss              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.1/repo/non-oss/                      |        
18 | repo-oss                  | openSUSE-13.1-Oss                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.1/repo/oss/                          |        
19 | repo-source               | openSUSE-13.1-Source               | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/13.1/repo/oss/                   |        
20 | repo-update               | openSUSE-13.1-Update               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1/                                         |        
21 | repo-update-non-oss       | openSUSE-13.1-Update-Non-Oss       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1-non-oss/                                 |

I installed VLC-codecs because VLC seemed unable to play anything even while the Packman codecs were installed.

What should my next move be?

EDIT: Just some additional info that might (help?) be of use:

peter@linux:~> sudo zypper install libxine2-codecs k3b-codecs ffmpeg lame gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-ugly gstreamer-0_10-plugins-ugly-orig-addon gstreamer-0_10-plugins-ffmpeg libdvdcss2root's password:
Loading repository data...
Reading installed packages...
'ffmpeg' is already installed.
No update candidate for 'ffmpeg-2.2.4-4.3.x86_64'. The highest available version is already installed.
'gstreamer-0_10-plugins-bad' is already installed.
There is an update candidate for 'gstreamer-0_10-plugins-bad', but it is from a different vendor. Use 'zypper install gstreamer-0_10-plugins-bad-0.10.23-164.5.x86_64' to install this candidate.
'lame' is already installed.
No update candidate for 'lame-3.99.5-1013.9.x86_64'. The highest available version is already installed.
'gstreamer-0_10-plugins-ugly' is already installed.
There is an update candidate for 'gstreamer-0_10-plugins-ugly', but it is from a different vendor. Use 'zypper install gstreamer-0_10-plugins-ugly-0.10.19-47.1.x86_64' to install this candidate.
'gstreamer-0_10-plugins-ffmpeg' is already installed.
No update candidate for 'gstreamer-0_10-plugins-ffmpeg-0.10.13-2000.4.x86_64'. The highest available version is already installed.
'libxine2-codecs' is already installed.
No update candidate for 'libxine2-codecs-1.2.5-90.6.x86_64'. The highest available version is already installed.
'gstreamer-0_10-plugins-ugly-orig-addon' is already installed.
No update candidate for 'gstreamer-0_10-plugins-ugly-orig-addon-0.10.19-12.5.x86_64'. The highest available version is already installed.
'k3b-codecs' is already installed.
No update candidate for 'k3b-codecs-2.0.80+git20140916.1337-1.1.x86_64'. The highest available version is already installed.
'libdvdcss2' is already installed.
No update candidate for 'libdvdcss2-1.2.13-5.2.x86_64'. The highest available version is already installed.
Resolving package dependencies...


Nothing to do.

Using

zypper install gstreamer-0_10-plugins-ugly-0.10.19-47.1.x86_64

just wants to change vendors from Packman to multimedia:libs.

EDIT 2: I did install Chromium before I installed the codecs. Could deleting my Chromium profile do anything?

#4

Well, do you see the difference?
Not sure if that is normal or would work, but I would think not.

The latest chromium is in fact 37, and this is unfortunately not part of the update repo yet.
This might be worth a bug report, but I guess it will be released soon (tomorrow maybe?), it is at least in the queue.
Maybe the update process should be a bit more streamlined though, or the packages should have stricter dependencies…

But I don’t know, as I don’t use chromium myself.

Repo list:

Ok, you could clean up there a bit.
No need to have the Google-Chrome repo twice, or even once at all, if you want to use chromium anyway.
And #13 is superfluous as well, as you have the standard oss repo anyway as #18.
But those should not cause your problem.

I installed VLC-codecs because VLC seemed unable to play anything even while the Packman codecs were installed.

Yes, you need to additionally install vlc-codecs for vlc being able to play all files.
But that’s unrelated to chromium.

What should my next move be?

EDIT: Just some additional info that might (help?) be of use:

peter@linux:~> sudo zypper install libxine2-codecs k3b-codecs ffmpeg lame gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-ugly gstreamer-0_10-plugins-ugly-orig-addon gstreamer-0_10-plugins-ffmpeg libdvdcss2root's password:
Loading repository data...
Reading installed packages...
'ffmpeg' is already installed.
...
Nothing to do.

That’s ok.
There are higher versions in your multimedia:libs repo, but you should not install those, as they don’t have the full codec support that Packman provides.
Do you have any particular reason to use multimedia:libs at all?
Maybe you should just remove it.

And as I already wrote, your next step should probably be a “full vendor change upgrade” to Packman.
In your case:

zypper dup --from "Packman Repository"

But at the moment, it probably won’t help much.
Just wait until chromium 37 is released as official update, I’d say.

Using

zypper install gstreamer-0_10-plugins-ugly-0.10.19-47.1.x86_64

just wants to change vendors from Packman to multimedia:libs.

It should not want to do this.
Have you enabled “vendor change”?

EDIT 2: I did install Chromium before I installed the codecs. Could deleting my Chromium profile do anything?

No, this should not matter.

#5

The latest chromium is in fact 37, and this is unfortunately not part of the update repo yet.
This might be worth a bug report, but I guess it will be released soon (tomorrow maybe?), it is at least in the queue.
Maybe the update process should be a bit more streamlined though, or the packages should have stricter dependencies…

But I don’t know, as I don’t use chromium myself.

If that was the case, wouldn’t there be more people being affected by this? And wouldn’t it make more sense to update chromium-ffmpeg after Chromium itself? Weird that they could be different versions at all…

Ok, you could clean up there a bit.
…
And #13 is superfluous as well, as you have the standard oss repo anyway as #18.
But those should not cause your problem.

Okay, cleaned up my repo list. Here is the new one:


peter@linux:~> zypper lr -d
#  | Alias                  | Name                         | Enabled | Refresh | Priority | Type   | URI                                                                               | Service                                                                                                                                                                        
---+------------------------+------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------------------------+--------                                                                                                                                                                        
 1 | KDE:Frameworks5        | KDE:Frameworks5              | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.1/         |                                                                                                                                                                                
 2 | KDE:Qt5                | KDE:Qt5                      | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.1/                 |                                                                                                                                                                                
 3 | Packman Repository     | Packman Repository           | Yes     | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.1/                          |                                                                                                                                                                                
 4 | X11:Cinnamon:Factory   | X11:Cinnamon:Factory         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/X11:/Cinnamon:/Factory/openSUSE_13.1/   |        
 5 | google-chrome          | google-chrome                | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                               |        
 6 | home:XRevan86          | home:XRevan86                | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/XRevan86/openSUSE_13.1/           |        
 7 | home:XRevan86:non-free | home:XRevan86:non-free       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/XRevan86:/non-free/openSUSE_13.1/ |        
 8 | home:andykimpe         | home:andykimpe               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/andykimpe/openSUSE_13.1/          |        
 9 | libdvdcss repository   | libdvdcss repository         | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/13.1/                                              |        
10 | openSUSE:13.1          | openSUSE:13.1                | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/13.1/standard/                |        
11 | repo-non-oss           | openSUSE-13.1-Non-Oss        | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.1/repo/non-oss/                      |        
12 | repo-oss               | openSUSE-13.1-Oss            | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.1/repo/oss/                          |        
13 | repo-update            | openSUSE-13.1-Update         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1/                                         |        
14 | repo-update-non-oss    | openSUSE-13.1-Update-Non-Oss | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1-non-oss/

I removed the redundant repo’s and multimedia:libs (not sure why I had it in the first place)
Everything look alright in this section?

No need to have the Google-Chrome repo twice, or even once at all, if you want to use chromium anyway.

I use Google Chrome for syncing my Google stuff and Chromium for everything else. Weird but that’s what I do.

And as I already wrote, your next step should probably be a “full vendor change upgrade” to Packman.
In your case:

zypper dup --from "Packman Repository"

But at the moment, it probably won’t help much.
Just wait until chromium 37 is released as official update, I’d say.

I ran

zypper dup --from "Packman Repository"

and it seemed to switch some packages over to Packman, but overall didn’t work for Chromium. Surprised it wasn’t already changed to Packman already.

So in summary: I might have been hit with a bug until Chromium is updated to v.37. I could try to file a bugreport if I want to, but should probably wait until the update to see if that solves it. And when v37, in theory, should work with the v.37 ffmpeg plugin correct? Not reinstalling of either packages needed right? Thanks for all of the help you’ve given me.

#6

Probably.
But I don’t know myself, as I don’t have chromium installed and don’t use it.

Maybe someone else could comment on this?

And wouldn’t it make more sense to update chromium-ffmpeg after Chromium itself? Weird that they could be different versions at all…

Well, that’s a problem with synchronizing, I suppose.
Packman is a completely different repo, on completely different servers.
But they link to OBS.
Normally this should work, but sometimes there can be problems maybe.

I removed the redundant repo’s and multimedia:libs (not sure why I had it in the first place)
Everything look alright in this section?

Yes.

I use Google Chrome for syncing my Google stuff and Chromium for everything else. Weird but that’s what I do.

Well, this was just a side-question.
The main point was that you have it twice, which is unnecessary of course. :wink:

Still, I don’t really understand why you don’t just use Chrome then for everything?
It is the same browser after all, but comes with everything included AFAIK.

So in summary: I might have been hit with a bug until Chromium is updated to v.37. I could try to file a bugreport if I want to, but should probably wait until the update to see if that solves it. And when v37, in theory, should work with the v.37 ffmpeg plugin correct? Not reinstalling of either packages needed right?

Yes, that’s how I see it. But I’m not at all sure that the version mismatch is really a problem (I do think it is though).
The update to chromium V37 is in the queue as mentioned, so there’s no need to file a bug report about that.

But maybe somehow such a problem should/could be prevented in the future.
I’m not sure at the moment though if there would be a way.

Thanks for all of the help you’ve given me.

Well, I tried at least, but I’m not sure whether I really helped you much… :wink:

#7

Well, this was just a side-question.
The main point was that you have it twice, which is unnecessary of course. :wink:

Still, I don’t really understand why you don’t just use Chrome then for everything?
It is the same browser after all, but comes with everything included AFAIK.

I don’t really like having my searches tied to my account, just a weird personal preference I guess. Plus I tend to get a lot of screen-tearing with Chrome that I don’t see with Chromium. Drivers I suppose.

Yes, that’s how I see it. But I’m not at all sure that the version mismatch is really a problem (I do think it is though).
The update to chromium V37 is in the queue as mentioned, so there’s no need to file a bug report about that.

But maybe somehow such a problem should/could be prevented in the future.
I’m not sure at the moment though if there would be a way.

Well, I tried at least, but I’m not sure whether I really helped you much… :wink:

Yeah, makes enough sense for me! I’ll update this thread once Chromium v.37 is released and whether or not it solved the issue and work my way from there. Thanks again.

Fingers crossed.

#8

switching from chromium-ffmpeg to chromium-ffmpegsumo (which is same version # as chromium) will give you html5 but the trade-off is that you will lose support for h264/265 content.
Recently updates to chromium in openSUSE have been a little slow. There was mention of this in another thread a few months back but I forget what the reason was.

#9

FYI
I just ran the Youtube HTML5 test on my openSUSE web browsers…
On this machine, <no media codecs packages are installed>, these are the default configurations of the web browsers. Even if media codec packages were installed, I’d question whether those are automatically used by the web browser… Maybe, maybe not.

Chromium
Version 35.0.1916.114 (270117)
All boxes are checked, all codecs and extensions supported
Could you expect anything different from a web browser designed to support Google technology?

Firefox ESR
13.1.0
Checked boxes - HTMLVideoElement, WebM VP8

So, interpreting the above findings…

  • The Chromium browser if fully functional, supporting the HTML5 player, and all codecs used on the YouTube site.
  • The FF browser supports the HTML5 player, but only the WebM codec.

The YouTube videos I’ve downloaded using JDownloader have almost all been encoded in all available codecs but if any were not encoded with WebM, then you wouldn’t be able to watch in FF. If you haven’t heard of WebM, it’s the multimedia codec Google was able to obtain awhile back but only within the past half year or so clear up all the licenses necessary to make this codec usable as FOSS, in fact it’s probably the only codec that is completely free to use. Ogg Vorbis is next closest but some aren’t completely happy with performance so hasn’t been able to challenge .264.

I don’t normally use this machine to watch video, so don’t have the Packman codec packages installed which are required for VLC and other locally running video viewers.

TSU

#10

EDIT: Switched to Chromium–ffmpegsumo and although the HTML5 says all codecs are supported, Chromium still fails to play HTML5 videos and switches to using Flash immediately.

#11

Yes, that’s because chromium-ffmpegsumo is the stripped down version that lacks support for most codecs.
But it can be shipped with openSUSE legally therefore.

#12

On 2014-09-19 17:16, tsu2 wrote:
>
> FYI
> I just ran the Youtube HTML5 test on my openSUSE web browsers…

Where is that test?

I tried https://www.youtube.com/html5, and it says several
things supported or not supported by my browser, but I do not see any
video playing testing. It apparently only checks that the codec is
present and reported to work.

> Firefox ESR
> 13.1.0
> Checked boxes - HTMLVideoElement, WebM VP8
…
> - The FF browser supports the HTML5 player, but only the WebM codec.

I think that the VLC plugin supports H.264, so FF should be able to play
it.

> The YouTube videos I’ve downloaded using JDownloader have almost all
> been encoded in all available codecs but if any were not encoded with
> WebM, then you wouldn’t be able to watch in FF. If you haven’t heard of
> WebM, it’s the multimedia codec Google was able to obtain awhile back
> but only within the past half year or so clear up all the licenses
> necessary to make this codec usable as FOSS, in fact it’s probably the
> only codec that is completely free to use.

I was not aware of the “open” part of it. When I use jdownloader I avoid
it, because webm can autoadjust the resolution to the actual download
speed - which is a good thing when watching real time in FF, but not
when waiting to view it later. So I specify a fixed resolution on
jdownloader.

Nuances of having a too slow internet pipe…

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#13

On 2014-09-20 14:35, Carlos E. R. wrote:

> I was not aware of the “open” part of it. When I use jdownloader I avoid
> it, because webm can autoadjust the resolution to the actual download
> speed - which is a good thing when watching real time in FF, but not
> when waiting to view it later. So I specify a fixed resolution on
> jdownloader.
>
> Nuances of having a too slow internet pipe…

In fact, html5 is horrible here. I’m trying a video, and it says «webm;
codecs="vp8.0, vorbis», and «dash: no». “Dash” is the variable,
adjusting speed thing (not webm), and it is not running. Video is
horribly chopped even at the lowest speed available.

At the end of the video, it automatically starts with a new one, so that
if I go back in the broweser to replay the one I do want and have
already “seen”, it downloads it again, choppy. It does not cache it.

I don’t see where to tell youtube not to start a new video at the end,
but STOP there. Oh, ok, saw it. Right hand side panel. “Autoplay”. Now I
can go back and replay without “chops”.

I still prefer jdownloader… or CLI, rather.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#14

AFAIK Firefox (current versions at least, FF 13.1.0 is ancient :wink: ) uses gstreamer (0.10 in openSUSE 13.1) to play back HTML5 content.
So you have to have the necessary gstreamer(-0_10) codecs/plugins installed.

Old versions of Firefox did not support gstreamer yet and indeed only could play WebM content, IIRC.

#15

PS, @LostLogin, sorry for not mentioning this earlier (I somehow forgot to…):
If you don’t want to wait longer for the chromium update to be released, you can install it from here now already:
http://download.opensuse.org/update/13.1-test/

This is the Test-Update repo, official updates are tested there first before they get released via the standard Update repo.
If you install chromium 37 from there, the Packman chromium-ffmpeg package should work again.

I would not really recommend to add that repo to your system though. Although most of the time there should not be problems.

#16

yes, if it is youtube you are trying to view then ffmpegsumo will be of no help as most content is h264 encoded.

#17

I believe I could also just find the RPM online and upgrade it that way (without adding the repo) as well correct?

I’m thinking of just sticking out with pepper-flash and hoping the official update will clear all of this up.It just doesn’t make sense though: technically, shouldn’t every OpenSUSE user using Chromium also have this problem? I’m having a hard time wrapping my head around this.

#18

Yes, but you don’t have to “find the RPM online”… :wink:
Just click on that link, browse to the corresponding sub-folder (i586 for a 32bit system, x86_64 for a 64bit one), download the “chromium” RPM and install it.

This was just a suggestion though if you don’t want to/can wait any longer.
The update should be released in the next few days anyway.

I’m thinking of just sticking out with pepper-flash and hoping the official update will clear all of this up.It just doesn’t make sense though: technically, shouldn’t every OpenSUSE user using Chromium also have this problem? I’m having a hard time wrapping my head around this.

Yes, if that’s the problem (and I think it is), then every openSUSE user using Chromium should indeed have the same problem.

So either not many openSUSE users use chromium, or those that do do not use HTML5 sites.
I belong to the first group, as mentioned… :wink:

#19

Yes, if that’s the problem (and I think it is), then every openSUSE user using Chromium should indeed have the same problem.

So either not many openSUSE users use chromium, or those that do do not use HTML5 sites.
I belong to the first group, as mentioned… :wink:

That’s really weird to me, I always thought Chromium was a popular browser. But after checking Chromium-ffmpeg, it was updated to version 37 only 8 days before my post so I guess it would make sense that I’m the first to post about it. Maybe the rest of the Chromium users have pepper-flash installed and didn’t notice the Youtube wasn’t in HTML5. Whatever the case. I hope this is fixed in Chromium’s update.

#20

No idea, and I don’t have any statistics.
But don’t forget that quite a few people probably use Chrome.

But after checking Chromium-ffmpeg, it was updated to version 37 only 8 days before my post

Of course.
Packman has version 37 since version 37 was submitted to the update process. They do not create a chromium package themselves.

Maybe the rest of the Chromium users have pepper-flash installed and didn’t notice the Youtube wasn’t in HTML5.

Yes, maybe.

Whatever the case. I hope this is fixed in Chromium’s update.

If the reason is the version mismatch, it will definitely be fixed by the update, obviously.