Package Details: firefox-vaapi 122.0.1-1

Git Clone URL: https://aur.archlinux.org/firefox-vaapi.git (read-only, click to copy)
Package Base: firefox-vaapi
Description: Standalone web browser from mozilla.org (with VA-API patches)
Upstream URL: https://www.mozilla.org/firefox/
Keywords: firefox libva va-api vaapi video
Licenses: MPL-2.0
Conflicts: firefox
Provides: firefox
Submitter: ewout
Maintainer: None
Last Packager: ewout
Votes: 10
Popularity: 0.96
First Submitted: 2023-02-24 13:48 (UTC)
Last Updated: 2024-02-10 16:57 (UTC)

Dependencies (36)

Required by (154)

Sources (8)

Latest Comments

1 2 3 4 Next › Last »

dcelasun commented on 2024-03-11 11:05 (UTC)

wayland-proxy patches are no longer needed as of Firefox 123.

NRG commented on 2024-02-12 10:12 (UTC)

I get basically the same error. My knowledge here is very limited; but it seemingly has to do with mesa, starting somewhere at 23.3.3? See aur/mesa-git comments.

dcelasun commented on 2024-02-05 22:47 (UTC) (edited on 2024-02-05 22:47 (UTC) by dcelasun)

Under X11 with Nvidia (not sure if relevant) PGO build fails with:

started SP3 server on port 8000                                                                                                                                                                
DRI3 not available       
failed to load driver: zink
console.warn: services.settings: Ignoring preference override of remote settings server
console.warn: services.settings: Allow by setting MOZ_REMOTE_SETTINGS_DEVTOOLS=1 in the environment
ATTENTION: default value of option mesa_glthread overridden by environment.
MESA: error: CreateSwapchainKHR failed with VK_ERROR_OUT_OF_DEVICE_MEMORY
MESA: error: zink: could not create swapchain
ExceptionHandler::GenerateDump cloned child 13022
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error. 
Exiting due to channel error.        
Firefox exited with code 11 during profile initialization

It seems like VK_ERROR_OUT_OF_DEVICE_MEMORY is a red herring, there is plenty of VRAM available. Non-PGO build works fine.

unknown78 commented on 2024-01-27 23:42 (UTC)

Just an info -> i was only able to compile 122 in a full wayland session. X11 or a terminal werent able to run the requiered tests with and zink environment.

X11: zinkrun glxgears

DRI3 not available
failed to load driver: zink
Error: couldn't get an RGB, Double-buffered visual

gamescope with a terminal inside wasn't enough it broke once it should have started the test session with the compiled firefox

a tty (aka login shell / terminal) did complain it couldn't start the tests either

I got it compiled under plasma wayland but othere wayland based environments might work too. I also needed to close the spawned firefox window ...

ewout commented on 2024-01-09 19:38 (UTC) (edited on 2024-01-09 19:39 (UTC) by ewout)

@deemon Included the wayland proxy patches per your suggestion. Appreciate the feedback! Maybe create a ticket for the regular firefox package in the repos to include these patches as well?

Drommer commented on 2024-01-02 16:35 (UTC) (edited on 2024-01-02 16:36 (UTC) by Drommer)

deemon, you can download the prebuilt package from here (or take the patch and add it to the build): https://build.opensuse.org/package/show/home:drommer:archlinux/firefox-kde-stable.

P.S. Please let me know if it works as expected.

deemon commented on 2023-12-26 23:05 (UTC) (edited on 2023-12-31 02:53 (UTC) by deemon)

Since Firefox 121 now runs natively on Wayland, it crashes A LOT for me. Apparently I am not the only one and Fedora guys have included in their firefox build something called "wayland-proxy" to fix this crap ( https://www.phoronix.com/news/Wayland-Proxy-Firefox ; https://mastransky.wordpress.com/2023/12/22/wayland-proxy-load-balancer/ ). Can you somehow add this wayland-proxy to this firefox-vaapi build also please? Or it will probably/hopefully added to the mainline Firefox for everyone hopefully. This "mastransky" seems to be firefox dev, who packaged this proxy into fedora package (for more humal trials? -- https://bugzilla.mozilla.org/show_bug.cgi?id=1743144#c100 )

Anyway, right now as we don't have it yet, testing it out as standalone proxy between wayland and firefox:

git clone https://github.com/stransky/wayland-proxy.git
cd wayland-proxy/src
chmod +x compile
./compile
./wayland-proxy /usr/lib/firefox/firefox

EDIT: SO FAR THIS HAS WORKED PERFECTLY FOR ME! Firefox has not crashed once for 4 days now. (whereas it did crash like 5-20 times a day previously in wayland mode)

remmy commented on 2023-12-10 20:31 (UTC) (edited on 2023-12-10 20:31 (UTC) by remmy)

@maxpayne3

I'm running a ThreadRipper with 96GBs of RAM and I will say that even with that, it was using 35GB of RAM and maxing out all 48 cores during compile. It went pretty quick, but compilation time could take quite awhile.

xzntest commented on 2023-12-10 06:25 (UTC)

@deemon the automated testing is for profile guided optimization. you should be able to edit the PKGBUILD to disable pgo

deemon commented on 2023-12-07 11:42 (UTC)

is it possible to turn off the automated testing BS in the middle of compilation that shoots up a browser and does all the wrong things in my computer?

1 2 3 4 Next › Last »