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.

-- 
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 beta/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`).

  Currently it seems to work for all reporters on Xorg, but not for all
  reporters on Wayland.

  Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
  the main snap via [2]. Comments before #176 refer to [3] and _should_
  be roughly equivalent to [1], but I wouldn't be surprised if it turned
  out not to be.

  [1]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
  [2]: 
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
  [3]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168

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