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 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
So, system has acceleration profiles.
And Apps like Mplayer, VLS are working fine.
Only chromium is not working.
Hardware with driver:
Radeon 5500xt with latest AMDGPU driver.
Installed with flags:
amdgpu-install --usecase=workstation -y --vulkan=pro --opencl=rocr,legacy
--
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 : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
