Package Details: mullvad-browser-bin 15.0.9-1

Git Clone URL: https://aur.archlinux.org/mullvad-browser-bin.git (read-only, click to copy)
Package Base: mullvad-browser-bin
Description: Privacy-focused web browser developed by Mullvad VPN and the Tor Project
Upstream URL: https://mullvad.net/en/browser
Keywords: browser firefox mullvad privacy private
Licenses: MPL-2.0
Conflicts: mullvad-browser
Provides: mullvad-browser
Submitter: tarball
Maintainer: tarball
Last Packager: tarball
Votes: 73
Popularity: 4.92
First Submitted: 2023-04-03 14:58 (UTC)
Last Updated: 2026-04-07 14:25 (UTC)

Pinned Comments

tarball commented on 2024-06-26 08:35 (UTC)

Make sure to fetch the developers' signing key before building the package.

The official instructions are here. The link is also mentioned in the PKGBUILD.

If the site is blocked in your region, you'll have to work around it or trust me that this is what it says:

% gpg --auto-key-locate nodefault,wkd --locate-keys torbrowser@torproject.org

which (as of 2024-06-26) should also show this fingerprint:

EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290

If your gpg says otherwise, you may have been fed garbage.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

tarball commented on 2025-07-24 18:05 (UTC)

I can get the same message by running:

PATH=$PATH:./bin yay -S mullvad-browser-bin

But not by simply building the package on any of the systems I've tried.

Since there's nothing touching PATH in the PKGBUILD (and it hasn't been substantially modified in a long time), it looks like a local misconfiguration. Could you check your PATH to be sure?

echo $PATH

If there's nothing suspicious in there, the variable can also be modified during build time by /etc/makepkg.conf and/or /etc/makepkg.conf.d/*.conf (and maybe some other configs — recursive grep through /etc might be useful).

jugs commented on 2025-07-24 17:16 (UTC)

@tarball, just updating from the 14.5.5 version bump with yay. Log here: https://0x0.st/8n7e.log

tarball commented on 2025-07-24 14:04 (UTC)

Could you provide more info on how you're building it? I rebuilt it through makepkg twice before pushing the update, and a couple more times now with no problems. Same with yay.

jugs commented on 2025-07-24 14:00 (UTC)

14.5.5 build isn't happy:

find: The relative path ‘./bin’ is included in the PATH environment variable, which is insecure in combination with the -execdir action of find.  Please remove that entry from $PATH
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: mullvad-browser-bin-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
mullvad-browser-bin - exit status 4

Leia commented on 2025-04-24 07:16 (UTC) (edited on 2025-04-24 07:19 (UTC) by Leia)

Looks line it's a known issue: https://github.com/mullvad/mullvad-browser/issues/422

Launching mullvad-browser with MOZ_ENABLE_WAYLAND=1 environmental variable solved it for me.

Leia commented on 2025-04-22 08:03 (UTC) (edited on 2025-04-22 08:06 (UTC) by Leia)

Launching Mullvad browser from the terminal with MOZ_ENABLE_WAYLAND=0 variable still crashes with the same errors:

Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=2.15888) [GFX1]: Error in eglSetDamageRegion: 0x3009 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=2.15888) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=2.17088) [GFX1]: Error in eglSetDamageRegion: 0x3009

I ran the flatpak versions of Mullvad browser and Firefox ESR forcing x11-only and wayland-only sockets separately. I also ran the regular versions of both the browsers from terminal with MOZ_ENABLE_WAYLAND=1 to make sure they're running under wayland.None of the six scenarios generate either the error or the crash.

tarball commented on 2025-04-21 07:24 (UTC)

Does it happen with the upstream tarball? If so, there's probably not much we can do about it, except…

Mullvad flatpak works fine. So does Firefox ESR.

I'd first see if all three were using x11 or wayland (about:support → Window Protocol), and if mullvad-browser is the only one running through wayland, force it in line with MOZ_ENABLE_WAYLAND=0 /usr/bin/mullvad-browser.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »