@dcelasun I tried to build it using pikaur and paru. I also asked for help to check on another system. the assembly also failed.

@tagnupip what is it that you're trying to do? That's a weird command. Just run makepkg normally.

The command could not be executed 'sudo --user=#1000 --preserve-env=VISUAL -- makepkg --force'.

Oh cool. Since Firefox 136 I don't even need this vaapi patched firefox anymore. Standard Firefox video HW decoding works now out of the box for AMD users :-) ( https://www.mozilla.org/en-US/firefox/136.0/releasenotes/ )

Thanks for making this available for the previous 2 years though 🥰

Updated to 134.0 which builds fine for me with Python 3.13.1 from the repos.

Currently, building fails at:

Installing collected packages: zstandard
Successfully installed zstandard-0.23.0
Traceback (most recent call last):
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/./mach", line 155, in main
    mach = check_and_get_mach(os.path.dirname(os.path.realpath(__file__)), args)
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/./mach", line 39, in check_and_get_mach
    return load_mach(dir_path, mach_path, args)
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/./mach", line 25, in load_mach
    return mach_initialize.initialize(dir_path, args)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/build/mach_initialize.py", line 344, in initialize
    command_site_manager.activate()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 602, in activate
    self.ensure()
    ~~~~~~~~~~~^^
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 563, in ensure
    result = self._up_to_date()
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 800, in _up_to_date
    pthfile_lines = self._pthfile_lines()
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 782, in _pthfile_lines
    PythonVirtualenv(self._mach_virtualenv_root).site_packages_dirs()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 853, in site_packages_dirs
    platlib = self.resolve_sysconfig_packages_path("platlib")
  File "/home/admin/.cache/yay/firefox-vaapi/src/firefox-133.0/python/mach/mach/site.py", line 843, in resolve_sysconfig_packages_path
    relative_path = path.relative_to(data_path)
  File "/usr/lib/python3.13/pathlib/_local.py", line 385, in relative_to
    raise ValueError(f"{str(self)!r} is not in the subpath of {str(other)!r}")
ValueError: '/usr/lib/python3.13/site-packages' is not in the subpath of '/home/admin/.cache/yay/firefox-vaapi/src/mozbuild/srcdirs/firefox-133.0-f725f8cfd913/_virtualenvs/mach'

---

Note that you are running Mach with Python 3.13.1, which is higher
than the highest known working version of Python for Mach. Consider
running Mach with Python 3.11 or lower.

Running the following command may solve your issue:

    python3.11 ./mach build --priority normal

==> ERROR: A failure occurred in build().
    Aborting...

The message may slightly vary as I installed python311 after my first failed build; without it, the message stating to run mach on python311 doesn't show up.

I can confirm that going into the source directory and building/calling mach with python311 does in fact work and the build process finishes successfully, however I don't know what the steps are to force the PKGBUILD to use python311 as opposed to 3.13 (my guesses are: python311 needs to be a dependency/build dependency and run mach with that version)

I tried by adding an env variable to the PKGBUILD under build() "export PYTHON=/usr/bin/python3.11" but the build process failed with the same error. (In addition to having to delete the built package as yay would fail because src/mozbuild already existed, therefore not reaching the build stage).

I'm guessing I should've changed the actual line where mach is called to explicitly use python311, but since it took quite a while to build and I need to get back to work I can't provide a satisfactory solution to this issue at this time. I will update if I go through with it again and successfully finish the entire install process.

EDITS: redaction/clarity, formatting, punctuation

I was wondering, why there is no HEVC support enabled in about:support? I only see HW decoding enabled for H264, VP9 and AV1; and SW for everything except also HEVC. Although my vainfo seems to show, that I have totally HEVC HW thing supported to some degree?

Trying display: wayland
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 24.3.2-arch1.1 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.8, DRM 3.54, 6.6.65-1-MANJARO)
vainfo: Supported profile and entrypoints
      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
      VAProfileAV1Profile0            : VAEntrypointVLD
      VAProfileAV1Profile0            : VAEntrypointEncSlice
      VAProfileNone                   : VAEntrypointVideoProc

I noticed a lot of those in the journal: firefox[12302]: Failed to create /home for shader cache (Permission denied)---disabling. Apparently others on "normal" firefox are having the same issue... https://bugzilla.mozilla.org/show_bug.cgi?id=1921742 -- fixed as workaround by putting into /etc/environment MESA_SHADER_CACHE_DIR=$HOME/.cache/mesa_shader_cache. no more spam in logs. :-)