[SOLVED]Chromium doesn't play IMDb video's on Debian Testing

Everything about X, Gnome, KDE, ... and everything running on it

[SOLVED]Chromium doesn't play IMDb video's on Debian Testing

Postby merloki » 2018-01-06 19:35

IMDb video's don't work for me in Chromium. I receive this message: Sorry, this video is unsupported on this browser.

The video's work in Chromium on any other website (e.g. YouTube and Steam)

I tried every possible solution that I could find on the web so I think it's a problem in Debian Testing or in Chromium Version 62.0.3202.89 (Developer Build)

I use Plasma 5.11, the proprietary GTX 1050 driver, an AMD Phenom X3 with the AMD microcode and here is additional info about my setup:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
CheckerImaging: Disabled
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Disabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated but at reduced performance
WebGL2: Unavailable

Problems Detected
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Checker-imaging has been disabled via finch trial or the command line.
Disabled Features: checker_imaging

Version Information
Data exported 1/6/2018, 9:07:54 PM
Chrome version Chrome/62.0.3202.89
Operating system Linux 4.14.0-2-amd64
Software rendering list version 0
Driver bug list version 10.30
ANGLE commit id unknown hash
2D graphics backend Skia/62 e74b41c6c84638d5a9ee6d254a715bcd9e17c603-
Command Line /usr/lib/chromium/chromium --show-component-extension-options --ignore-gpu-blacklist --no-default-browser-check --disable-pings --media-router=0 --enable-remote-extensions --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so --ppapi-flash-version=28.0.0.126 --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end

Driver Information
Initialization time 0
In-process GPU true
Passthrough Command Decoder false
Supports overlays false
Sandboxed false
GPU0 VENDOR = 0x10de, DEVICE= 0x1c81
Optimus false
Optimus false
AMD switchable false
Driver vendor Google Inc.
Driver version 3.3.0.2
Driver date 2017/04/07
Pixel shader version 3.0
Vertex shader version 3.0
Max. MSAA samples 4
Machine model name
Machine model version
GL_VENDOR Google Inc.
GL_RENDERER Google SwiftShader
GL_VERSION OpenGL ES 2.0 SwiftShader
GL_EXTENSIONS
Disabled Extensions
Window system binding vendor
Window system binding version
Window system binding extensions
Window manager KWin
XDG_CURRENT_DESKTOP KDE
Compositing manager Yes
Direct rendering Yes
Reset notification strategy 0x0000
GPU process crash count 0
System visual ID 0
RGBA visual ID 0

Compositor Information
Tile Update Mode One-copy
Partial Raster Enabled

GpuMemoryBuffers Status
ATC Software only
ATCIA Software only
DXT1 Software only
DXT5 Software only
ETC1 Software only
R_8 Software only
R_16 Software only
RG_88 Software only
BGR_565 Software only
RGBA_4444 Software only
RGBX_8888 Software only
RGBA_8888 Software only
BGRX_8888 Software only
BGRA_8888 Software only
RGBA_F16 Software only
YVU_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only

Log Messages
[1271:1271:0106/193631.178732:ERROR:gl_implementation.cc(241)] : Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: /usr/lib/chromium/swiftshader/libGLESv2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
GpuProcessHostUIShim: The GPU process exited with code 1024.
[1279:1279:0106/193631.372646:ERROR:gl_implementation.cc(241)] : Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: /usr/lib/chromium/swiftshader/libGLESv2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
GpuProcessHostUIShim: The GPU process exited with code 1024.
[1287:1287:0106/193631.556992:ERROR:gl_implementation.cc(241)] : Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: /usr/lib/chromium/swiftshader/libGLESv2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
GpuProcessHostUIShim: The GPU process exited with code 1024.
[1297:1297:0106/193631.741564:ERROR:gl_implementation.cc(241)] : Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: /usr/lib/chromium/swiftshader/libGLESv2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
GpuProcessHostUIShim:
GpuProcessHostUIShim: The GPU process exited with code 1024.


Is there a fix for this that I didn't find? Or should I file this as a bug report?
Last edited by merloki on 2018-01-11 18:14, edited 1 time in total.
merloki
 
Posts: 5
Joined: 2018-01-06 17:13

Re: Chromium doesn't play IMDb video's on Debian Testing

Postby debiman » 2018-01-08 07:28

i cannot make anything of this wall of "additional info", but:

does chromium rely on gstreamer plugins?

also i seem to remember something about chromium being no longer supported.
could be wrong though.
User avatar
debiman
 
Posts: 2900
Joined: 2013-03-12 07:18

Re: Chromium doesn't play IMDb video's on Debian Testing

Postby merloki » 2018-01-08 20:07

debiman wrote:i cannot make anything of this wall of "additional info", but:

does chromium rely on gstreamer plugins?

also i seem to remember something about chromium being no longer supported.
could be wrong though.


Thank you for the reply. Chromium displays this wall of additional info when I surf to chrome://gpu/

I also tried with hardware acceleration enabled but it doesn't make a difference.

I don't think that chromium needs a gstreamer plugin for IMDb, because using an external codec platform will probably be seen as a security risk by the chromium developers.

And I have pepperflashplugin-nonfree installed for the flash support.

Chromium is supported by Debian and it should also work with IMDb:

"The majority of videos on IMDb are in HTML5 and should play on any modern browser. We do have a small number of video still in Flash format, although these are being phased out so you should not need Flash for most video content. There might be a temporary network issue affecting video streaming with via your internet connection. The problem may simply resolve itself after a few hours."

I use uBlock Origin but the video's on IMDb also don't play when I disable uBlock for IMDb.

HTML5 video's shouldn't be a problem in Chromium so maybe the IMDb video's are encoded in AAC, H.264 or MP3? Chromium doesn't support these 3 formats but how can I check in which format that IMDb encodes it's video's?

If the IMDb video's aren't encoded in AAC, H.264 or MP3 then I think it's 99% certain that it's a bug.
merloki
 
Posts: 5
Joined: 2018-01-06 17:13

Re: Chromium doesn't play IMDb video's on Debian Testing

Postby Kryten » 2018-01-09 22:50

They use h264 .chromium only supports Opus, Theora, Vorbis, WebM (VP8, VP9), and WAV which are open source.
Firefox has an open source version of h264 built in.chromium doesnt,so cannot play them.

Youtube works because all the videos can be played using WebM which chromium does support.

I have both installed in testing and just switch to firefox for sites like IMDb.
Kryten
 
Posts: 25
Joined: 2015-11-05 01:32

Re: Chromium doesn't play IMDb video's on Debian Testing

Postby debiman » 2018-01-10 07:01

^ i'm guessing that nails it.

merloki wrote:how can I check in which format that IMDb encodes it's video's?

download the video instead of playing it, and check with a media player or mediainfo or something.
youtube-dl works for imdb videos.
User avatar
debiman
 
Posts: 2900
Joined: 2013-03-12 07:18

Re: Chromium doesn't play IMDb video's on Debian Testing

Postby merloki » 2018-01-11 16:58

Kryten wrote:They use h264 .chromium only supports Opus, Theora, Vorbis, WebM (VP8, VP9), and WAV which are open source.
Firefox has an open source version of h264 built in.chromium doesnt,so cannot play them.

Youtube works because all the videos can be played using WebM which chromium does support.

I have both installed in testing and just switch to firefox for sites like IMDb.


Ok I downloaded an IMDb video via:

Code: Select all
youtube-dl "http://www.imdb.com/video/imdb/vi2921576729?playlistId=tt5109784&ref_=tt_ov_vi"


The mediainfo from this downloaded file gives this info:

    Video format: AVC
    Writing library: x264 core 148
    Audio format: AAC

AAC and x264 are not supported by Chromium.

I also have Firefox so I can switch to it when I need to watch the IMDb video's. Or I can use youtube-dl, thank you for the tip.

If Debian Testing would have Firefox Quantum as a standard package I would probably use it as my default brower.

But version 52 is significantly slower than Chromium. I even notice it on my V-NAND SSD 850 EVO.

Maybe I'll install Firefox Quantum from the Sid repo and remove Chromium.

I just don't know if it affects stability when you have both Firefox versions.
merloki
 
Posts: 5
Joined: 2018-01-06 17:13

Re: [SOLVED]Chromium doesn't play IMDb video's on Debian Tes

Postby pendrachken » 2018-01-13 04:44

You have several options other than bunging up your system with SID stuff:

1: Compile chromium with a version of FFMPEG that doesn't have h.264 stripped out of it.
2: Use google chrome, which is available for Linux. You don't have to sign in with a google account to use it.
3: Download firefox from the mozilla site and extract it to a folder in your users home directory and create a launcher for it.

Option 1 means you will have to re-compile the browser every time there is a security update. You will also have to recompile FFMPEG if there is a version bump that chromium relies on. You can do this on your own machine, or look into Steve's guide on how to set up a Debian compile environment through SuSe's build farm ( free )

Option 2 is the easiest, as Chrome will be updated by APT whenever a new build is rolled out. It will be the same update process that the rest of the system uses when you update software.

Option 3 PROBABLY will let firefox update itself when a new version rolls out, but will have some things like fonts / fontconfig [1] options ETC compiled in so won't respect your systemwide font smoothing or hinting working potentially leading to ugly font syndrome.


[1] At least this used to be the case, I haven't used FF in a long, long time. I don't think there was a way to avoid this though. If it was fixed let us know, if this is the path you so choose.
fortune -o
Your love life will be... interesting.
:twisted: How did it know?

The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches :-P
pendrachken
 
Posts: 1325
Joined: 2007-03-04 21:10
Location: U.S.A. - WI.


Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 10 guests

fashionable