Summary: | www-client/firefox shouldn't need USE=wayland for hardware video decoding | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | haarp <main.haarp> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | m_gentoobug |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://forums.gentoo.org/viewtopic-p-8755739.html | ||
See Also: |
https://bugzilla.mozilla.org/show_bug.cgi?id=1839599 https://bugzilla.mozilla.org/show_bug.cgi?id=1848631 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
haarp
2023-08-09 03:25:50 UTC
Hmm 116 should have landed patches that makes it possible for hwaccel to work without wayland flag. It was indeed necessary before that. We also add a custom patch to enable vaapi on more AMD cards. I definitely had this issue with 116.0:rapid. Make sure your vaapi is working with "vainfo" in terminal. If yes, could you open an upstream bug about it? Let them know you've built Firefox with --enable-default-toolkit=cairo-gtk3-x11-only. That is claimed to be a duplicate of their bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1843425 And that reads as: Status: RESOLVED FIXED Milestone: 117 Branch ... with a patch. We're on: www-client/firefox-116.0 Hopefully fixed for the next release? Thanks, Martin Yes, it seems we made a mistake. The patches only landed in 117, not 116. Gonna wait and see. (In reply to haarp from comment #4) > Done: https://bugzilla.mozilla.org/show_bug.cgi?id=1848631 Thanks! (In reply to haarp from comment #6) > Yes, it seems we made a mistake. The patches only landed in 117, not 116. > Gonna wait and see. It was _supposed_ to work in 116 but obviosly it's a bug it didn't. A follow-up fix landed in 117. I also couldn't find the upstream bug because it was RESOLVED already. Anyone can toss the upstream patch into /etc/portage/patches to get it working right now (if it applies). If there's a reason to touch firefox-116, I'll include the patch, but if not I'll wait for 117 where it's natively included. 116.0.3 is out with linux-related fixes so I'll be looking to package that today with upstream fixes for vaapi. But I also found an about:config option to try and force-enable vaapi even with this 116.0 release, media.hardware-video-decoding.force-enabled -> true could you try setting that, restart your browser and see if vaapi works before updating to 116.0.3? I had already tried that, it didn't make a difference. I'm going to try a non-wayland 116.0.3 build later The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8282ad68d79e95724306dfd4cd597c5bab7b71d3 commit 8282ad68d79e95724306dfd4cd597c5bab7b71d3 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2023-08-17 09:16:34 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2023-08-17 09:16:34 +0000 www-client/firefox: add 116.0.3 - include latest upstream vaapi/hwdec patches from upcoming 117 and 118 releases. Closes: https://bugs.gentoo.org/911941 Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-client/firefox/Manifest | 101 ++ www-client/firefox/firefox-116.0.3.ebuild | 1466 +++++++++++++++++++++++++++++ 2 files changed, 1567 insertions(+) 116.0.3 looking good without wayland useflag :) Thanks! |