Comment 175 for bug 1816497

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
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSlice
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSlice
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileNone : VAEntrypointVideoProc`
>
> --
> 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
>
> Status in chromium-browser package in Ubuntu:
> In Progress
>
> Bug description:
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> 2. Start Chromium,
>
> 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, 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,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
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSlice
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSlice
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileNone : VAEntrypointVideoProc`
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>
>