I didn't know it ever worked on Nvidia. Since this bug is closed you
should open a new one and include output from 'vainfo'.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title
I have packages for Nvidia VAAPI and EGL in my system.
When I manually turned it on a few months ago, the acceleration in
Firefox was working. With new Nvidia drivers or whatever it broke.
I tried the 550, 560 and 565 drivers.
Still the same on Xorg or Wayland.
Tested with Snap and FLATPAK(ffmpe
I only tested a 13th gen U chip in the above comment. It looks like 13th
gen P chips should be supported so long as:
intel-media-driver >= 22.3.1+dfsg1-1ubuntu2 (per bug 2004237)
which it looks like snaps are shipping with now.
Newer Intel 14th gen and Ultra chips might not be supported yet, b
Verified working in firefox (Wayland) on both Intel 12th and 13th gen
systems. intel_gpu_top shows hardware video decoding is in use straight
out of the box when viewing YouTube. The firefox snap versions tested
were 122.0-2 and 122.0-2.1, both Noble systems.
Caveat: intel_gpu_top also shows very
** Description changed:
This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
browsers.
We will close this bug when most browsers will have Va-api decoding working
OOTB without user interaction like in WinOS and MacOS
January 2024:
- Quickest answer : Install firefo
Yeah that's the same question I had in "EDIT" of comment #151. Someone
just needs to test it on old and new hardware.
--
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/1424201
Tit
@Daniel, #146 mentions xwayland but we switched firefox to use wayland
by default since so it should work at least on waylands sessions? And #2
is about newer intel generation.
Said differently on a < 13th gen using wayland the videoacc should be
working out of the box no?
--
You received this b
** Description changed:
This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
browsers.
- We will close this bug when both browsers will have Va-api decoding working
OOTB without user interaction like in WinOS and MacOS
+ We will close this bug when most browsers will have Va-a
This bug is still open for Firefox. Also the issue mentioned in comment
#146 isn't resolved yet. Unless comment #146 is wrong?
--
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/142
It should also just be working with the firefox snap, what's your
testcase?
--
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/1424201
Title:
Web browsers lacking hardware-accele
Vaapi in Flatpak Firefox works OOTB now ( Just a flag away) so
definitely the best solution.
--
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/1424201
Title:
Web browsers lackin
Yes this bug was supposed to solve it , But I don't think it did
https://mzl.la/3W6JpMQ
--
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/1424201
Title:
Web browsers lacking har
Based on a recent report (https://discourse.ubuntu.com/t/problems-with-
intel-iris-xe-gpu-hardware-video-acceleration-in-22-04/34849/4), I think
Firefox is missing:
* Xwayland support: requires libva >= 2.17 in the gnome-42-2204 snap.
That's also missing from jammy-updates.
* Intel 13th gen suppo
** Tags added: kivu performance
--
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/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status in Chromium Bro
Partial duplicate: bug 1816497
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medi
** Description changed:
This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
browsers.
We will close this bug when both browsers will have Va-api decoding working
OOTB without user interaction like in WinOS and MacOS
August 2022 :
- * Ubuntu 22.04 :Launch firefox sna
** Description changed:
This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
browsers.
We will close this bug when both browsers will have Va-api decoding working
OOTB without user interaction like in WinOS and MacOS
Auhust 2022 :
* Ubuntu 22.04 :Launch firefox sna
** Description changed:
- This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
- browsers.
+ This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
browsers.
+ We will close this bug when both browsers will have Va-api decoding working
OOTB without user interactio
It looks like the old Chrome bug has been dead for a while:
https://bugs.chromium.org/p/chromium/issues/detail?id=463440
But some newer bugs offer hope:
https://bugs.chromium.org/p/chromium/issues/detail?id=1121948
https://bugs.chromium.org/p/chromium/issues/detail?id=1262051
--
You rece
Indeed, before closing the firefox task for this bug, we need to look
into the situation with the deb package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browse
Could we track the firefox deb OOTB support ?
IMO FF deb still does not use the GPU OOTB to decode video.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers l
Yes indeed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status in Chromium Browser:
Unknown
Status in Moz
Tracking in bug 1947115 for the Firefox snap, although once fixed that's
probably enough to close this one for Firefox too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
** Description changed:
- The chromium team has done a great job to totally disable hardware
- decoding on Linux.
+ This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
+ browsers.
- Even ignoring the GPU blacklist does not enable GPU decoding.
+ In 2015 I opened this bug , no
This should depend on bug 1616185 and bug 1619523 so it's easier to find
where the work happened.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking ha
** Changed in: firefox
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
This needs to be closed to claim the bounty at
https://www.bountysource.com/issues/55506502-meta-add-va-api-hardware-
decoding-support-on-linux so closing this one.
Wayland va-api decoding was implemented by Bug 1616185
X11 variant is pending at Bug 1619523
--
You received this bug notification
(In reply to Robert Mader [:rmader] from comment #35)
> (In reply to eric.riese from comment #34)
> >
> > In my opinion the bounty was already earned when this issue was resolved
> > but I don't know who gets to be the arbiter.
>
> That would certainly be Martin Stránský :)
> Martin, do you want
(In reply to eric.riese from comment #34)
>
> In my opinion the bounty was already earned when this issue was resolved but
> I don't know who gets to be the arbiter.
That would certainly be Martin Stránský :)
Martin, do you want to claim the bounty? If you don't care about it / don't
need it yo
Reminder that there is still a bounty for this issue at BountySource
https://www.bountysource.com/issues/55506502-add-va-api-hardware-
decoding-support-on-linux
I got an email from BountySource that they're going to start taking old
bounties for themselves starting *2020-07-1* (reproduced below)
re-opening as a meta bug for VA-API implementation (including X11)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decodi
(In reply to lilydjwg from comment #30)
> I'm glad to here that, but what about support for Firefox on X11? Is it given
> up?
Hardware decoding is platform independent so it generally works under X11 as
it's implemented as Bug 1616185.
For whole playback chain see Bug 1610199 what's needed to b
HW decoding support has landed at Bug 1616185.
*** This bug has been marked as a duplicate of bug 1616185 ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web brows
(In reply to lilydjwg from comment #30)
> I'm glad to here that, but what about support for Firefox on X11? Is it given
> up?
Filed Bug 1619523 for it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.laun
I'm glad to here that, but what about support for Firefox on X11? Is it
given up?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerat
It looks like the VAAPI version is gone from the snap store again. Is
there some reason why this hasn't been merged yet as mentioned in #96?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bu
If anyone's interested, I've attempted to add VP9 support to the VDPAU/VA-API
wrapper for NVIDIA here: https://github.com/xtknight/vdpau-va-driver-vp9
Testers are welcome. I've used it successfully on 19.10 with chromium-vaapi.
--
You received this bug notification because you are a member of De
That should be bug 1572697 for Wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status in Chromium Brow
@grmat libplacebo is a renderer not a hardware decoder and is unfit to
be used in a browser. First thing we need dmabuf support so that we can
import decoded frames without copying them back to the system RAM and
then display it on the screen. If I understand it correctly this is the
toughest part.
Also, please note that this would save the users a few GWh of electric
energy and thus help protect the climate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web brow
I've recently spent some time testing the implementations in various
browsers. Chromium implements VA-API but it's disabled in official
builds and fragile, breaking regularly. Webkit uses gstreamer-vaapi and
I've had quality issues with that using both Intel (wrong colours) and
AMD (blur) hardware.
Yes, this bug affects me.
ср, 3 июл. 2019 г. в 05:54, Robert Mader <1424...@bugs.launchpad.net>:
> Although this bug is only about decoding support, I'd like to leave a note
> about the rendering: AFAIK rendering without any slow copies requires
> DMABUF support, so processes can share resources
Although this bug is only about decoding support, I'd like to leave a note
about the rendering: AFAIK rendering without any slow copies requires DMABUF
support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:
> Wayland dmabuf surfa
Launchpad has imported 24 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1210727.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://h
** Changed in: firefox
Importance: Medium => Unknown
** Changed in: firefox
Status: Invalid => Unknown
** Changed in: firefox
Remote watch: Mozilla Bugzilla #563206 => Mozilla Bugzilla #1210727
--
You received this bug notification because you are a member of Desktop
Packages, which
*** This bug has been marked as a duplicate of bug 1210726 ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
** Changed in: firefox
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status in
** Changed in: firefox
Importance: Wishlist => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status
The vaapi-enabled snap currently lives in the candidate/vaapi channel,
which was automatically closed due to lack of updates, but an update
bringing it to the latest stable version is pending publication, so it
will soon be re-opened and available.
Once confirmed this works as expected, I plan to
wrt #91 which snaps might those be?
If its the regular 'chromium' snap it certainly doesn't make any mention
of the fact it supports hardware video acceleration or includes the
vaapi patch.
# snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
pu
As stated by Daniel, the problem is one of maintenance. Maintaining a
patch against a large and fast-moving code base such as chromium has a
cost, which is why it's always preferable to have such changes
upstreamed.
As it is clear that upstream is not going to enable hardware-accelerated
video dec
Last I heard, Ubuntu "applying the patch" wasn't feasible because it
kept breaking due to upstream changes in Chromium. It's not a patch we
can carry without someone volunteering to maintain it. But oSoMoN is the
expert here and will have more current information...
P.S. You can watch YouTube vide
Good to know. What is downside of enabling hardware acceleration in deb
packages too?
--
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/1424201
Title:
Web browsers lacking hardw
There are snap packages in Ubuntu that enable hardware video
acceleration.
--
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/1424201
Title:
Web browsers lacking hardware-acceler
Fedora started enabling video acceleration in this build late last year:
* Tue Nov 27 2018 Tom Callaway - 70.0.3538.110-2
- enable vaapi support (thanks to Akarshan Biswas for doing the hard work here)
--
You received this bug notification because you are a member of Desktop
Packages, which is
As neither Chrome/Chromium or Firefox has any real interest in Linux
support can we get Ubuntu to apply the patch? The patch has existed for
5 years already.
Even a partial solution where its built in but you still have to enable
it in config would be fine. Having to hunt down a ppa to get working
One of the use cases where this is sorely needed are WebRTC video
conferencing applications like WebEx and the like. Without GPU
acceleration, they become very CPU heavy, which cripples them on laptops
especially.
--
You received this bug notification because you are a member of Desktop
Packages,
FYI Fedora has now included the VAAPI
https://src.fedoraproject.org/rpms/chromium/c/278c62709d1dba5883c3b69047706837bb402bd7?branch=master
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad
Launchpad has imported 75 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=563206.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
I've created a new bug to enable hardware acceleration via v4l2 codecs
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686
. Patches linked in the bug. This would give machines like the
Raspberry Pi hardware acceleration (although currently the kernel needs
patches too!).
--
** Summary changed:
- Chromium does not use the GPU to decode videos
+ Web browsers lacking hardware-accelerated video decoding
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Bug watch added: Mozil
Hi Olivier.
I totally understand Canonical's position, Upstream is always better.
But we have here with google a competitive unfair distrortion.
They are doing their best to keep desktop linux behind by ignoring this
patch for several years.
The result is that Linux laptops are not competitive
The current upstream effort is tracked at https://chromium-
review.googlesource.com/c/chromium/src/+/532294. However it doesn't seem
to be getting much traction. I am reluctant to distro-patching as it's a
rather large patch that often gets outdated with new chromium versions,
with non-trivial conf
Hi olivier , can we see if the Ubuntu package can include the patch at
least for 18.04 ? We talk about version 66 which is available now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.n
** Bug watch added: Red Hat Bugzilla #1462493
https://bugzilla.redhat.com/show_bug.cgi?id=1462493
** Also affects: chromium-browser (CentOS) via
https://bugzilla.redhat.com/show_bug.cgi?id=1462493
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
@dino99 : are you working at google on chromium ?
Your argument is pretty wrong, there is Zero impact if this feature is
hidden with a flag that one could enable when deployed.
Today we are stuck because we need to recompile.
Sorry but one could think that google wants to slow DesktopLinux
prog
Tentatively assigned myself to re-assess the situation, and try to
understand if enabling VAAPI support is doable with a distro-patch, and
how much work that would represent.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug
hi Michel
i understand the general frustation, but chromium is not the only choice after
all. Its clear that nothing will be done to support that feature on linux (pure
management resources decision)
--
You received this bug notification because you are a member of Desktop
Packages, which is su
** Description changed:
- The chromium team has done a great job to totally disabl hardware
+ The chromium team has done a great job to totally disable hardware
decoding on Linux.
Even ignoring the GPU blacklist does not enable GPU decoding.
How ever the patch is quite simple and it's
Saikrishna Arcot clarified that this feature request doesn't affect
Opera users.
--
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/1424201
Title:
Chromium does not use the GPU t
Seems like this issue also affects Opera users.
--
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/1424201
Title:
Chromium does not use the GPU to decode videos
Status in Chromi
Hi chad , For few versions chromium was unable to use the vaapi , It's
now possible again using the patch from the dev branch :
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev
Can you integrate this patch ?
Also a lot of GPU VP8/VP9 decoding become possible with nvidia and
Inte
** Bug watch added: code.google.com/p/chromium/issues #463440
http://code.google.com/p/chromium/issues/detail?id=463440
** Also affects: chromium-browser via
http://code.google.com/p/chromium/issues/detail?id=463440
Importance: Unknown
Status: Unknown
--
You received this bug not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launc
Public bug reported:
The chromium team has done a great job to totally disabl hardware
decoding on Linux.
Even ignoring the GPU blacklist does not enable GPU decoding.
How ever the patch is quite simple and it's already working using this
PPA ( using libVA ) :
https://launchpad.net/~saiarcot895
75 matches
Mail list logo
