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`.

** Description changed:

  To test the snap with VA-API changes,
  
  1. Install the Chromium snap,
  
     sudo snap install --channel candidate/hwacc chromium
  
- 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
+ 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
+ 
+    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
  
  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.
  
  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;
  - 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 a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
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. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),

     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

  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.

  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;
  - 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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to