@osomon: did you build for arm64? should I try again?
--
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 i
No worries, let me see if @jon-nettleton can have a look.
--
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
Stat
@osomon: I see linux-libc-dev is installed in the snap build process but
not libc6-dev. I know that normally libc6-dev is included in build-
essentials when building .deb files, but is it possible that it isn't in
the default set of things for a snap build environment?
--
You received this bug no
Oddly enough, you do include it in the snap definition as of May 13...
```
build-packages:
- gcc
- libc6-dev
- libdrm-dev
- libgl1-mesa-dev
- libwayland-dev
- libx11-dev
- libxext-dev
- libxfixes-dev
- pkg-config
```
--
You received this
As was pointed out by @jon-nettleton, the intel parts are not required
to build, and only are used for intel onboard graphics, which
necessarily won't be present on ARM64. Is it possible to make it
conditional to build those parts depending upon architecture?
https://launchpad.net/~lizthegrey/+sna
`stage-packages libdrm-intel1` still fails despite skipping the build
steps. Needs a selector to skip it on !amd64/i386.
--
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
Now we're getting somewhere!
chrome://gpu shows:
```
Vulkan: Disabled
...
Video Acceleration Information
Vulkan Information
Device Performance Information
Log Messages
[4784:4784:0719/142605.755018:ERROR:vaapi_wrapper.cc(511)] : vaInitialize
failed: unknown libva error
[4784:4784:0719/142605.96757
Can we try pulling in https://packages.ubuntu.com/bionic-updates/mesa-
va-drivers instead of the base bionic package pulled right now by the
https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-
enable-vaapi build config (which doesn't use Bionic-Updates)?
--
You received this bug
The problem also might be that I'm running Chromium inside XWayland
rather than natively on X11. I'll try popping over to X11 to see whether
it works...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://b
>From X11 without Wayland:
Vulkan still shows as disabled but the init error doesn't turn up.
Log Messages
[18061:18061:0719/145212.290039:ERROR:sandbox_linux.cc(374)] :
InitializeSandbox() called with multiple threads in process gpu-process.
[18061:18061:0719/145432.791528:ERROR:shared_image_man
from x11 without wayland:
```
LIBVA_MESSAGING_LEVEL=2 snap run chromium
Gtk-Message: 12:36:55.257: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:36:55.262: Failed to load module "canberra-gtk-module"
/usr/share/libdrm/amdgpu.ids: No such file or directory
libva info: VA-API version 1
Aha, it's a detection issue on wayland. passing
`LIBVA_DRIVER_NAME=radeonsi` does a trick.
```
LIBVA_DRIVER_NAME=radeonsi LIBVA_MESSAGING_LEVEL=2 snap run
chromiumGtk-Message: 12:41:29.046: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:41:29.049: Failed to load module "canberra-gtk-
```
Gtk-Message: 12:30:13.823: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:30:13.826: Failed to load module "canberra-gtk-module"
/usr/share/libdrm/amdgpu.ids: No such file or directory
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva
although Vulkan is showing as off in chrome://gpu, I _am_ seeing better
performance now when switching tabs, watching youtube, and using webgl
:)
or maybe that's the placebo effect at work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
VP9 decodes in software with VpxVideoDecoder
```
00:00:00.294error
"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
name\":\"DecryptingVideoDeco
Correct. I'ts a Polaris chip = UVD6.3
(https://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_6). no vp9 or
av1.
--
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:
Started seeing this recently with 5.8.0-33 after a few minutes logged
into either Wayland or X11 session, regardless of other activity on
system, but does not repro once I downgrade kernel to 5.8.0-31.
Gnome shell version 3.36.4-1ubuntu1~20.04.2 has been the same
throughout. Mutter likewise on 3.3
Never mind, I think mutter 3.36.6-1ubuntu0.20.04.2+lizf1 is busted,
please disregard :)
on the plus side I have a reliable trigger.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/18
Reverted mutter to focal-updates stock, rebooted into 5.8.0-33, repro'd
again :( so we're back to the hypothesis that there's something wrong in
5.8.0-33. Sorry for the noise, I'm trying to debug this as best as I
can.
--
You received this bug notification because you are a member of Desktop
Pack
bug was hardware - bad usb port! hardware is hilarious.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1886059
Title:
gnome-shell crashed with assertion failure
"!xcb_xlib_threa
can I beg the favor of having `rtc_use_pipewire` turned on for your
branch? otherwise I'm happy to fork, just let me know :)
--
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/18164
I'm unable to find the channel/branch on arm64. Can you also publish an
arm64 snap in that branch?
```
$ sudo snap switch --channel=latest/candidate/vaapi chromium
"chromium" switched to the "latest/candidate/vaapi" channel
$ sudo snap refresh chromium
error: requested a non-existing branch on lat
Some of us would like to have use_vaapi on Linux arm64 though :)
--
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 decodin
23 matches
Mail list logo
