[snap] vaapi chromium no video hardware decoding

VAAPI in Chromium snap 71 worked really well,
after update to 72 It does not work anymore.

I have also reinstalled snap with sudo snap install --channel=candidate/vaapi chromium
yet does not work.

CPU 6700HQ:

libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 2.1.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Simple : VAEntrypointEncSlice
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointStats
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointEncSliceLP
      VAProfileH264Main : VAEntrypointFEI
      VAProfileH264Main : VAEntrypointStats
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointEncSliceLP
      VAProfileH264High : VAEntrypointFEI
      VAProfileH264High : VAEntrypointStats
      VAProfileH264MultiviewHigh : VAEntrypointVLD
      VAProfileH264MultiviewHigh : VAEntrypointEncSlice
      VAProfileH264StereoHigh : VAEntrypointVLD
      VAProfileH264StereoHigh : VAEntrypointEncSlice
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileNone : VAEntrypointVideoProc
      VAProfileJPEGBaseline : VAEntrypointVLD
      VAProfileJPEGBaseline : VAEntrypointEncPicture
      VAProfileVP8Version0_3 : VAEntrypointVLD
      VAProfileVP8Version0_3 : VAEntrypointEncSlice
      VAProfileHEVCMain : VAEntrypointVLD
      VAProfileHEVCMain : VAEntrypointEncSlice

Status changed to 'Confirmed' because the bug affects multiple users.

It appears that the candidate/vaapi channel has either been broken or abandoned, since the last build was on February 15th: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-enable-vaapi

Is it possible to get the channel added to the 'Built automatically' build schedule since is currently set to the 'Built on request' build schedule?

I have resurrected the candidate/vaapi channel with an up-to-date build, however it's currently pending a manual review in the store.

Some updates:

- I can confirm that 'sudo snap install --channel=candidate/vaapi chromium' installs correctly, as of today, with the same version indicated in the build log.
- HW accelerated decode is not available when I apply the '--ignore-gpu-blacklist' flag
- HW accelerated encode is available whether or not I apply '--ignore-gpu-blacklist' flag
- I've attached the following three files, in a tar.bz2 archive, to show my system config:
     1) vainfo output
     2) chrome://gpu default value
     3) chrome://gpu value after applying '--ignore-gpu-blacklist' flag

As far as i know, Chromium uses a new video decoding backend. If chrome://media-internals is showing MojoVideoDecoder as VideoDecoder it's using VA-API. Otherwise it falls back to FFMpegVideoDecoder or VPXVideoDecoder.

With the latest snap from candidate/vaapi (73.0.3683.86 REV-686) media-internals show that it's using MojoVideoDecoder. CPU-Usage around 10$ - 15% on an i3 Broadwell and HD5500-Graphics. Video Decode under chrome://gpu is also showing "Hardware accelerated"

Interesting. Since I'm only getting VpxVideoDecoder decode, I guess I have an installation issue of some kind.

I wonder if my problem may be related to this error in the chrome://gpu log:

- [20257:20257:0414/133034.932196:ERROR:gl_implementation.cc(280)] : Failed to load /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: cannot open shared object file: No such file or directory

Oddly I get this bug in both the main chromium snap and the vaapi candidate snap. No problems in Chromium when installed via apt. Since I'm not able to update the snap file, I can't correct this issue unfortunately.

@Matt have you tried h264ify extension from the chrome store? It ensures that only h264 videos are loaded. On my Broadwell hardware decoding of VP9 is not supported.

I have a slightly newer chipset (Kabylake) so VP9 is supported in my case. Thanks for the suggestion though.

Hi,

with Version 74.0.3729.131 the decoder has become FFmpegVideoDecoder
 once again and does not turn gpu decoder.

The landing page for the build has disappeared: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-enable-vaapi so it's possible that your installation has reverted to the main branch again.

For what it's worth, there is another working option available that we can try: https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta

I'd honestly prefer to use an official Ubuntu build but the one above has served me consistently well on previous system so I'll probably stick with that until we see a main branch build with vaapi support.

Can confirm it is still not working. I don't like the idea of using a ppa in software as sensitive as a browser. But also, vaapi acceleration makes a really important deference, specially in a laptop. The snap was a great solution, it is a shame it is not longer working.

I can also confirm this. Is VAAPI Chromium snap abandoned? It really makes a huge difference.

It does appear to be abandoned, unfortunately. I had hoped that the official addition of VAAPI support to Firefox would be an alternative but it is dependent on Wayland, which is not currently default supported by Ubuntu.

If anyone doesn't mind, Brave has vaapi support out the box.
1. install gstreamer-vaapi
2. go to brave://flags and enable Override software rendering list, restart browser.
3. go to brave://gpu/ and look at Video Acceleration Information:

Thank you for the recommendation.

Brave is now my default browser. First impression is quite good.

I have updated the enable-vaapi branch and test snaps are currently building for amd64 and i386 at https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-source-enable-vaapi.

Hi Olivier,

Many thanks for starting that back up! I have install Chromium from the candidate/vaapi channel and the HW acceleration is working for me.

Thanks for the testing and feedback Matt, much appreciated!

Here is my few tests from yesterday :

Platform : pentium Kabylake mobile

- YouTube VP90 1080p : MojoVideoDecoder - 15% CPU - 8-10W battery

- Netflix H264 720p ? ( https://bit.ly/3apopqR) : DecryptingVideoDecoder - 20% CPU - 12-15W battery

I'm then looking for info about DecryptingVideoDecoder when Widevine is used , how is video decoded.

Bacause when looking to compare LinuxLaptops with MacBooks on "Netflix battery time"

Test on 20.04 on Pentium N5000 :

- Chromium show "unknown libva error" from the start.
- VAAPI is not used

I have tried the 81.0.4044.113 vaap candidate, but it is showing this warning at startup:
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)

For reference, this is the output of vainfo:
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
vainfo: Supported profile and entrypoints
      VAProfileNone : VAEntrypointVideoProc
      VAProfileNone : VAEntrypointStats
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Simple : VAEntrypointEncSlice
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointFEI
      VAProfileH264Main : VAEntrypointEncSliceLP
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointFEI
      VAProfileH264High : VAEntrypointEncSliceLP
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileJPEGBaseline : VAEntrypointVLD
      VAProfileJPEGBaseline : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3 : VAEntrypointVLD
      VAProfileVP8Version0_3 : VAEntrypointEncSlice
      VAProfileHEVCMain : VAEntrypointVLD
      VAProfileHEVCMain : VAEntrypointEncSlice
      VAProfileHEVCMain : VAEntrypointFEI
      VAProfileHEVCMain10 : VAEntrypointVLD
      VAProfileHEVCMain10 : VAEntrypointEncSlice
      VAProfileVP9Profile0 : VAEntrypointVLD
      VAProfileVP9Profile2 : VAEntrypointVLD

@Michel: sorry for the late feedback. On that Pentium N5000 system, could you please include the full output of running "chromium --enable-logging=stderr", and the corresponding journalctl entries, filtered on "chromium"?

@Miguel: which OS/version are you running the chromium snap on? Can you please include the output of "snap info --abs-time chromium" ?

For reference, I tested on my HD Graphics 4000 (Ivy bridge, Core i7) and I'm seeing similar numbers as Michel in comment #21.

I am using Ubuntu 20.04. Here is the output of snap info:

name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
  An open-source browser project that aims to build a safer, faster, and more stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/vaapi
refresh-date: 2020-05-09T15:52:01+02:00
channels:
  latest/stable: 81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB -
  latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB -
  latest/beta: 83.0.4103.44 2020-05-08T01:02:43Z (1144) 163MB -
  latest/edge: 84.0.4128.3 2020-04-29T05:50:21Z (1136) 164MB -
installed: 81.0.4044.113 (1117) 165MB -

Same "libva error" issue here, with an Intel Core i5-7200U CPU (Intel HD 620). I attached the output of running "chromium --enable-logging=stderr", the chromium's journalctl entries (from installation to first and second launch) and vainfo.

The iHD VAAPI driver wasn't available until Ubuntu 19.04. If the Chromium snap is build with Ubuntu 18.04 libraries, wouldn't that explain the error?

@Alain: thanks for the info. That might explain it, indeed.

intel-media-va-driver{,non-free} depends on libva-driver-abi-1.7, but libva in bionic only provides up to libva-driver-abi-1.1.

I'll look into building the snap with a newer version of libva.

Still working on this. I had to patch chromium's vaapi code to enable it to build against a custom libva: https://chromium-review.googlesource.com/c/chromium/src/+/2204178.

@osomon If bionic provides only libva-driver-abi-1.1, maybe its time to move chromium snap to core20?

HW acceleration doesn't work for me in the latest build. I noted that Olivier was going to build with a newer version of libva so I went ahead an installed the latest version, as per this guide: https://github.com/intel/media-driver/wiki/How-to-build-and-use-media-driver%3F. Unfortunately that did not change the behavior, so I still see kVideoDecoderName="VpxVideoDecoder"

snap info --abs-time chromium & vainfo dumps below:

name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical*
store-url: https://snapcraft.io/chromium
contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
  An open-source browser project that aims to build a safer, faster, and more stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/vaapi
refresh-date: 2020-05-17T17:46:48-07:00
channels:
  latest/stable: 81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB -
  latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB -
  latest/beta: 83.0.4103.56 2020-05-15T02:46:16Z (1155) 163MB -
  latest/edge: 84.0.4143.2 2020-05-13T04:57:20Z (1154) 164MB -
installed: 81.0.4044.138 (1162) 162MB -

libva info: VA-API version 1.8.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.8 (libva 2.1.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.2.pre (f403839f)
vainfo: Supported profile and entrypoints
      VAProfileNone : VAEntrypointVideoProc
      VAProfileNone : VAEntrypointStats
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Simple : VAEntrypointEncSlice
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointFEI
      VAProfileH264Main : VAEntrypointEncSliceLP
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointFEI
      VAProfileH264High : VAEntrypointEncSliceLP
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileJPEGBaseline : VAEntrypointVLD
      VAProfileJPEGBaseline : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3 : VAEntrypointVLD
      VAProfileVP8Version0_3 : VAEntrypointEncSl...

@Matt and others: I'm still working on this. I got chromium to build with the latest libva release, and there's an ongoing build with the latest releases of the corresponding drivers, which in my local tests is working fine. If everything goes well this should be available to test in the candidate/vaapi channel within less than 24 hours.

A note of interest: when testing the snap, use this command line to output more libva debug information:

    LIBVA_MESSAGING_LEVEL=2 snap run chromium

Thanks Olivier. I'll keep my eye out for that, so I can test

Everyone: a new snap is ready for testing in the candidate/vaapi channel (revision 1163):

    snap refresh chromium --channel=candidate/vaapi

Please test and report CPU usage while playing back HD video in the browser (you might want to use the h264ify extension for youtube and the like). Run the browser like this, and attach the output here:

    LIBVA_MESSAGING_LEVEL=2 snap run chromium

Thanks!

It's working here with an Intel Core i5-7200U CPU (Intel HD 620); "intel-gpu-top" confirms it is. Both VP9 and h264 are accelerated. CPU usage is around 20 to 35% while playing a 1080p video on Youtube (VP9), and a bit higher on Twitch (h264). Though it's way better than with software decoding.

$ LIBVA_MESSAGING_LEVEL=2 snap run chromium
Gtk-Message: 12:18:38.213: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:18:38.215: Failed to load module "canberra-gtk-module"
libva info: VA-API version 1.7.0
libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
[14314:14314:0520/121838.333051:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
libva info: VA-API version 1.7.0
libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
[14175:14175:0520/121838.439652:ERROR:browser_switcher_service.cc(238)] XXX Init()

It doesn't work here.
Intel i5-7200u running Ubuntu 20.04 on wayland. Maybe wayland is the issue?

$ LIBVA_MESSAGING_LEVEL=2 snap run chromium
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Gtk-Message: 10:15:51.783: Failed to load module "appmenu-gtk-module"
Gtk-Message: 10:15:51.986: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:15:52.002: Failed to load module "canberra-gtk-module"
[12405:12405:0520/101552.253222:ERROR:edid_parser.cc(102)] Too short EDID
data: manufacturer id
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[12641:12641:0520/101553.290076:ERROR:vaapi_wrapper.cc(482)] vaInitialize
failed: unknown libva error

El mié., 20 de may. de 2020 a la(s) 09:41, Alain Rouet (
<email address hidden>) escribió:

> It's working here with an Intel Core i5-7200U CPU (Intel HD 620);
> "intel-gpu-top" confirms it is. Both VP9 and h264 are accelerated. CPU
> usage is around 20 to 35% while playing a 1080p video on Youtube (VP9),
> and a bit higher on Twitch (h264). Though it's way better than with
> software decoding.
>
> $ LIBVA_MESSAGING_LEVEL=2 snap run chromium
> Gtk-Message: 12:18:38.213: Failed to load module "canberra-gtk-module"
> Gtk-Message: 12:18:38.215: Failed to load module "canberra-gtk-module"
> libva info: VA-API version 1.7.0
> libva info: Trying to open
> /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_7
> libva info: va_openDriver() returns 0
> [14314:14314:0520/121838.333051:ERROR:sandbox_linux.cc(374)]
> InitializeSandbox() called with multiple threads in process gpu-process.
> libva info: VA-API version 1.7.0
> libva info: Trying to open
> /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_7
> libva info: va_openDriver() returns 0
> [14175:14175:0520/121838.439652:ERROR:browser_switcher_service.cc(238)]
> XXX Init()
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>

--

Nicolás Abel Carbone

Doctor en Física - Becario Posdoctoral

CIFICEN-CONICET-UNCPBA

https://www.researchgate.net/profile/Nicolas_Carbone

*Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo
indique el mail, por favor no se sienta obligado a responder este mensaje
fuera de su horario de trabajo habitual.*

*My working hours may not be your working hours. Unless otherwise specified
in the mail, please do not feel obligated to reply outside of your normal
work schedule.*

Yes, I suspect chromium (or at least the vaapi patches we apply) isn't sufficiently wayland-aware. Nicolás, could you test in an X11 session just to let us know whether accelerated HW video decoding works there? That would be a useful data point.

I just tried in X11. It seems to be working :)
Sadly, most videos in YouTube seem to be av1 so it took me a while to get a vp9 video, but that's another issue altogether.

Thanks!

LIBVA_MESSAGING_LEVEL=2 snap run chromium
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Gtk-Message: 10:43:53.358: Failed to load module "appmenu-gtk-module"
Gtk-Message: 10:43:53.358: Failed to load module "appmenu-gtk-module"
Gtk-Message: 10:43:53.613: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:43:53.638: Failed to load module "canberra-gtk-module"
libva info: VA-API version 1.7.0
libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
[19302:19302:0520/104355.042209:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
libva info: VA-API version 1.7.0
libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
[19157:19157:0520/104355.269741:ERROR:browser_switcher_service.cc(238)] XXX Init()

Wao, perfecter build.

It is the first time my Nvidia/intel CPU, get a snap chromium support video decoder.

I need not manually maintain my native chromium environment.

Thanks for your hardwarking.

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454

 chrome://flags/#ozone-platform-hint , not work.

[30855:30855:0806/092525.830999:ERROR:wayland_connection.cc(210)] Failed to connect to Wayland display
[30855:30855:0806/092525.831041:ERROR:ozone_platform_wayland.cc(226)] Failed to initialize Wayland platform
[30855:30855:0806/092525.831051:ERROR:env.cc(226)] The platform failed to initialize. Exiting.

So it works in Xorg (great to hear!) but not in Wayland for you?

It seems that you need one additional flag in Wayland, --ozone-platform=wayland. I.e., can you please try

    chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland

sure, I already enable wayland.

chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
[14225:14225:0807/073546.382350:ERROR:wayland_connection.cc(210)] Failed to connect to Wayland display
[14225:14225:0807/073546.382387:ERROR:ozone_platform_wayland.cc(226)] Failed to initialize Wayland platform
[14225:14225:0807/073546.382398:ERROR:env.cc(226)] The platform failed to initialize. Exiting.

I remember in previouse snap it is working, but withtout vaapivideodecoder working. It is another problem, but the wayland is sure working.

does wayland mode conflict with vaapivdideodecoder feature ?

I know in the 22.04 version the default GUI mode is Wayland.

Wait,

> chrome://flags/#ozone-platform-hint , not work.

1. What does "not work" mean here? Does Chromium not even launch, or does it start but not hardware accelerated? If the former, does dropping the flags (--enable-features=VaapiVideoDecoder etc.) makes it launch?

> I remember in previouse snap it is working, but withtout vaapivideodecoder working. It is another problem, ...

2. So, in previous versions of the snap, Chromium would launch, but without hardware acceleration, correct me if I understand wrong.

> ... but the wayland is sure working.

3. You mean that snap is supposed to work under Wayland, not that Wayland itself works, right?

4. I'm also interested in your `snap run --shell chromium`, `vainfo` output under Wayland.

> does wayland mode conflict with vaapivdideodecoder feature ?

I, for one, could get hardware acceleration in Chromium under Wayland working with `chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland`.

I get the exact error you report on #161 if I try the Wayland command (chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland) under Xorg. Please double check you are not under Xorg when trying the Wayland command.

I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display.

I confirmed the native chromium-browser did work with --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland. The WAYLAND_DISPLAY will displayed chromium browser.

The only problem is using snap chromium. So I made a report this time.

> I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display.

Hmm, I'm not sure if this is clear: The variable WAYLAND_DISPLAY is set as a consequence of a Wayland session being started. One should not manually set WAYLAND_DISPLAY; that does not start Wayland.

> The WAYLAND_DISPLAY will displayed chromium browser.

I don't understand what this means.

Also it would be nice if you could address the points in #164, as your situation is still unclear to me.

Sorry I did not make clear describe the problem. (I thought the previous version is working, so the current is a small problem.)

I am using ubuntu-frame to make Wayland test: https://github.com/MirServer/ubuntu-frame

If the ubnutu-frame is started, the Wayland display is ready. So I just used native chromium and snap version chromium to confirm the display result.

It would be nice if you could run your test on normal Ubuntu Wayland, as it could be a bug in Ubuntu Frame.
Especially given https://github.com/MirServer/ubuntu-frame/issues/75, it would be reasonable to disregard your failure report.

The native chromium works. So I did not think it is a ubuntu-frame bug.

I test the previous snap chromium version before, and it also works.

This appears to be a duplicate of bug 1424201. Can we close this bug?

It is, but since that bug targets both Chromium and Firefox, I believe it would be significantly harder to keep track of context of each piece of feedback (unfortunately we don't have threading here), judging by the interactions we have had in this one, both for developers and users.

Also, I consider the bug description with the test case key for quickly identifying testing instructions.

A user reported VDAVideoDecoder in testing this under Wayland, but if he tries to play a Youtube video on fullscreen on 3 4K displays, it stops playing after ~10 s; Unmaximizing it resumes it.

The snap in the hwacc channel has been updated. Now it automatically detects Wayland or Xorg and sets flags accordingly.

My T460P (nvida + intel GPU): snap X11 works. video decoder with
hardware acceleration.

ubuntu frame with WayLand test: proper display.

Only problem is no video hardware decode. (I think it is not the snap
problem, the native version is also not support.)

It is nearly a perfect build.

Hope the wayland hardware acceleration will work in near future.

Lee

On Thu, Aug 18, 2022 at 1:44 AM Nathan Teodosio <email address hidden>
wrote:

> The snap in the hwacc channel has been updated. Now it automatically
> detects Wayland or Xorg and sets flags accordingly.
>
> ** Description changed:
>
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> - 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
> + 2. Start Chromium,
>
> - snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
> - --enable-features=VaapiVideoDecoder
> -
> - If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
> -
> - chromium --enable-features=VaapiVideoDecoder --disable-
> - features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
> + snap run chromium
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-media-
> samples
>
> - 4. Enter about:media-internals in the address bar and note what the page
> - says for kVideoDecoderName.
> + 4. Enter about:media-internals in the address bar, click the
> + corresponding box (if the video is playing, it will have the "(kPlay)"
> + identifier) and note what the page says for kVideoDecoderName.
>
> Please report
>
> - - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
> - - If failed, the video used for testing, including codec and
> resolution if possible;
> + - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is
> {FFMpeg,Vpx,Dav1d}VideoDecoder;
> - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
> - CPU generation (`lscpu`).
>
> About the last point, it may be that unfortunately only those with newer
> generations of Intel CPUs will have luck with this, but it's still an
> uncertainty. So reports are highly welcome.
>
> ----------Original Bug report ---------
>
> Libva is no longer working for snap installed chromium 72.0.3626.109
> (Official Build) snap (64-bit)
>
> I followed this instruction
> sudo snap install --channel=candidate/vaapi chromium
>
> My amdgpu can use libva
>
> `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
> 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
> vainfo: Supported profile and entrypoints
> VAProfileMPEG2Simple : VAEntrypointVLD
> VAProfileMPEG2Main : VAEntrypointVLD
> VAProfileVC1Simple : VAEntrypointVLD
> VAProfileVC1Main : VAEntrypointVLD
> VAProfileVC1Advanced : VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointVLD
> ...

Desktop: wayland
OS: Kinetic
CPU: i5-12600k
GPU: Intel Alderlake_s (Gen12)

I hit this error: vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode)

After which chromium seems to fall back to ffmpeg.

[135904:14:0913/135753.793304:INFO:decoder.cc(41)] DecryptingVideoDecoder
[135863:135986:0913/135753.794331:INFO:decoder.cc(65)] VDAVideoDecoder
[135904:14:0913/135753.795630:INFO:decoder.cc(65)] VDAVideoDecoder
[135904:14:0913/135753.795678:INFO:decoder.cc(65)] VDAVideoDecoder
[135863:135863:0913/135753.809617:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[135863:135863:0913/135753.809730:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap
[135863:135863:0913/135753.811544:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[135863:135863:0913/135753.811593:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap
[135904:14:0913/135753.811795:INFO:decoder.cc(32)] VpxVideoDecoder
[135904:14:0913/135753.811863:INFO:decoder.cc(44)] Dav1dVideoDecoder
[135904:14:0913/135753.812884:INFO:decoder.cc(29)] FFmpegVideoDecoder
[135904:14:0913/135753.812955:INFO:decoder.cc(29)] FFmpegVideoDecoder
[135744:135875:0913/135755.767907:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.

Launched with:

$ chromium --enable-logging=stderr --use-gl=egl --enable-features=VaapiVideoDecoder,VaapiVideoEncoder --disable-features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --ozone-platform=wayland Downloads/big-buck-bunny-1080p-60fps-30sec.mp4

Hi.
Can confirm this issue on Ubuntu 22.04 with Mate desktop env in X11 session.
No video acceleration is present.
When i try to start chromium in terminal i'm getting following output:
chromium-browser --use-gl=desktop --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder
Gtk-Message: 09:12:41.908: Failed to load module "appmenu-gtk-module"
[26251:26418:1016/091242.099224:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.ListActivatableNames: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.137" (uid=1000 pid=26251 comm="/snap/chromium/2105/usr/lib/chromium-browser/chrom" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus" member="ListActivatableNames" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:383)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:269)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:199)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)

Error: eglChooseConfig returned zero configs
    at Create (../../third_party/dawn/src/dawn/native/opengl/ContextEGL.cpp:53)

[26251:26522:1016/091244.462029:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.

Information from vainfo:
vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 22.1.0-devel for Radeon RX 5500 XT (navi14, LLVM 14.0.1, DRM 3.46, 5.15.0-50-generic)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileHEVCMain : VAEntrypointVLD
      VAProfileHEVCMain : VAEntrypointEncSlice
      VAProfileHEVCMain10 : VAEntrypointVLD
      VAProfileHEVCMain10 : VAEntrypointEncSlice
      VAProfileJPEGBaseline : VAEntrypointVLD
      VAProfileVP9Profile0 : VAEntrypointVLD
      VAProfileVP9Profile2 : VAEn...

Thanks for the report, especially valuable as it is the first about AMD.

I just submitted a change and pushed the new build. Can you please give
it a try?

   # snap refresh --channel beta/hwacc chromium
   $ snap run chromium

The previous version did not include the radeonsi_drv_video.so driver
(the one in your system is not visible from snap confinement).

If it still doesn't work, please attach the outputs of env and lscpu.

It's probably better to focus more on Intel until everything is working well enough to close the bug. VAAPI has historically only been reliable on Intel so we risk getting distracted in debugging non-Intel driver issues (which would also be off-topic given this is a Chromium bug).

Hi! From: https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038/comments/1137194

Is there any ETA for finishing the legal review of the inclusion of the non-free driver?

Thanks!

Unfortunately, no.

For these description items:

- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);

Do you mean?

- Distro version (`grep VERSION= /etc/os-release`);
- GPU (`lsgpu`);

Hardware decode on stable/hwacc worked out of the box for me, thanks!

- VDAVideoDecoder
- Xorg
- VERSION="21 (Vanessa)"
- Intel Kabylake (Gen9)
- Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

> For these description items:
>
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
>
> Do you mean?
>
> - Distro version (`grep VERSION= /etc/os-release`);
> - GPU (`lsgpu`);

Just found out about that one. :) Either is fine.

 > Hardware decode on stable/hwacc worked out of the box for me, thanks!

Great to hear that! But do note that stable/hwacc is at 105 and falling
behind, so unresolved CVEs will start accumulating and I don't recommend
using it on a regular basis. Unfortunately, so far it is the only one I
could get VDAVideoDecoder on.

Hi again @nteodosio and happy new year!

Any progress to report in the last 2 months?

Thanks!

Hey Marc, you can follow
https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/+ref/hwacc-dev,
-beta and -candidate.

- The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
FFmpegVideoDecoder

- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
xorg

- Distro version (`grep VERSION= /etc/os_release`);
22.10 Kinetic

- GPU (`lscpu`);
intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 -

lsgpu (that's a new one):
card0 Intel Kabylake (Gen9) drm:/dev/dri/card0
└─renderD128 drm:/dev/dri/renderD128

- CPU generation (`lscpu`).
Vendor ID: GenuineIntel
  Model name: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
    CPU family: 6
    Model: 142

Chromium snap:
chromium 112.0.5615.20-hwacc 2398 latest/beta/… canonical✓ -

Hardware decode on candidate/hwacc worked out of the box for me, thanks!

- VaapiVideoDecoder
- Xorg
- VERSION="21.1 (Vera)"
- Intel Kabylake (Gen9)
- Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

GPU . Intel® HD Graphics 5500 / Gen8 / Broadwell

Chromium : 113.0.5672.24 hwacc/candidate

Hardware decoding is not working !

Log:

[46128:46128:0511/183800.564351:WARNING:chrome_main_delegate.cc(589)] This is Chrome version 113.0.5672.24 (not a warning)
[46128:46128:0511/183800.609573:WARNING:chrome_browser_cloud_management_controller.cc(87)] Could not create policy manager as CBCM is not enabled.
[46128:46128:0511/183800.628662:WARNING:wayland_object.cc(157)] Binding to gtk_shell1 version 4 but version 5 is available.
[46128:46128:0511/183800.628726:WARNING:wayland_object.cc(157)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[46128:46128:0511/183800.628780:WARNING:wayland_object.cc(157)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available.
[46128:46128:0511/183800.889036:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
[46128:46128:0511/183800.904533:WARNING:account_consistency_mode_manager.cc(73)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[46128:46128:0511/183800.952551:WARNING:wayland_surface.cc(163)] Server doesn't support zcr_alpha_compositing_v1.
[46128:46128:0511/183800.952572:WARNING:wayland_surface.cc(178)] Server doesn't support overlay_prioritizer.
[46128:46128:0511/183800.952579:WARNING:wayland_surface.cc(192)] Server doesn't support surface_augmenter.
[46128:46128:0511/183800.952584:WARNING:wayland_surface.cc(207)] Server doesn't support wp_content_type_v1
[46128:46128:0511/183800.952589:WARNING:wayland_surface.cc(226)] Server doesn't support zcr_color_management_surface.
[46128:46128:0511/183800.952946:WARNING:cursor_loader.cc(122)] Failed to load a platform cursor of type kNull
libva info: VA-API version 1.17.0
libva info: Trying to open /snap/chromium/2444/va-driver-non-free/dri/iHD_drv_video.so
libva info: Trying to open /snap/chromium/2444/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
[minigbm:drv_helpers.c(364)] DRM_IOCTL_MODE_CREATE_DUMB failed (12, 13)
[46281:46281:0511/183800.988362:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= YUV_420_BIPLANAR and usage=GPU_READ_CPU_READ_WRITE
....

VAINFO
----
$ export LD_LIBRARY_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/
$ export LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri
$ vainfo

libva info: VA-API version 1.17.0
libva info: Trying to open /snap/chromium/current/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.6.6 (b51ffe5)
vainfo: Supported profile and entrypoints
      VAProfileNone : VAEntrypointVideoProc
      VAProfileNone : VAEntrypointStats
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Simple : VAEntrypointEncSlice
      VAProfileMPEG2Main : VAEntry...

Don't wanna be rude , but don't expect this to work solid one day.

I've been asking this to google and canonical for almost 10 years

We've worked hours of test and stuff , this is going nowhere.

Let's help firefox , time is precious

With the beta testing release, the hardware decoding is working for several recent Intel GPU architectures (Tigerlake, Aderlake, Raptorlake), so far, we only experienced a problem on Roadwell (Gen8) GPU, the oldest GPU generation we aim to support for this release, we will work to make it working very soon ... Let's keep the faith Michel !

CPU: 12th Gen Intel i5-12400 (12) @ 4.400GHz
GPU: Intel Alder Lake-S GT1 [UHD Graphics 730]

intel_gpu_top shows 0%

Kubuntu 23.04

Hi Peter, thanks, the bug description was not up to date, you need the snap from beta or edge. What is 'snap info chromium' for you?

If it doesn't work on those channels, please attach

  snap run chromium --enable-logging=stderr &> chr.log

Thank you, Nathan Teodosio.

I installed chromium as described here:
https://discourse.ubuntu.com/t/chromium-hardware-accelerated-build-for-intel-based-platforms-available-for-beta-testing/35625?u=d0od

That is, like this:
To install hardware accelerated Chromium:
snap install chromium --channel=latest/candidate/hwacc

I already found at https://snapcraft.io/chromium
Indeed, such a command is needed:
sudo snap install chromium --beta
I apologize for the inattention. I will check and send a message.
Thank you very much for your help.

Indeed, chromim-beta has hardware video acceleration.
All videos on youtube are accelerated.
But this is not observed in video conferences.
Verified in Google Meet.
Is this a bug?

No, it is not a bug, hardware decoding for video conferencing on google meet only works for very few specific use cases,

These are two different features as far as i know. For videoplayback with hardwaredecoding VAAPI videoencoding needs to be supported. For conference tools like google meet chromium needs to support videoencoding and videodecoding with Webrtc. On Windows both functions are implementet. The linuxversion never had support for it.