Package Details: mullvad-browser-bin 14.5.5-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, GPL-3.0-or-later
Conflicts: mullvad-browser
Provides: mullvad-browser
Submitter: tarball
Maintainer: tarball
Last Packager: tarball
Votes: 58
Popularity: 1.36
First Submitted: 2023-04-03 14:58 (UTC)
Last Updated: 2025-07-24 11:51 (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 Next › Last »

Leia commented on 2025-04-21 01:18 (UTC) (edited on 2025-04-21 01:19 (UTC) by Leia)

The browser keeps crashing after a few minutes of usage. Launching from terminal shows this error continuously repeating:

Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7507) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7637) [GFX1]: Error in eglSetDamageRegion: 0x3009 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7507) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7637) |[2][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8937) [GFX1]: Error in eglSetDamageRegion: 0x3009 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7507) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7637) |[2][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8937) |[3][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8977) [GFX1]: Error in eglSetDamageRegion: 0x3009 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7507) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7637) |[2][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8937) |[3][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8977) |[4][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=4.0257) [GFX1]: Error in eglSetDamageRegion: 0x3009 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7507) |[1][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.7637) |[2][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8937) |[3][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=3.8977) |[4][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=4.0257) |[5][GFX1]: Error in eglSetDamageRegion: 0x3009 (t=4.0267) [GFX1]: Error in eglSetDamageRegion: 0x3009

I'm using Plasma. The behavior is the same under the LTS kernel. Mullvad flatpak works fine. So does Firefox ESR.

tarball commented on 2025-04-05 17:11 (UTC)

Tested it with a fresh clone under a throwaway unix user, it builds fine.

Please try cleaning your AUR helper caches or build the package manually.

akya commented on 2025-04-05 17:01 (UTC) (edited on 2025-04-05 17:17 (UTC) by akya)

Tried multiple times, checksum validation is failing

Validating source files with sha256sums... mullvad-browser-linux-x86_64-14.0.9.tar.xz ... FAILED

Edit - Sorry, my bad, manually cleaning the cache helped. I though using clean build would delete the existing file, but apparently I should have tried manually cleaning the file. Thanks and sorry for the trouble.

tarball commented on 2025-04-01 16:47 (UTC)

Thanks, and sorry about that. Not sure how that happened, I'll add a separate git clean && makepkg step to my update routine to prevent this from happening in the future.

Should be fixed now.

Neurognostic commented on 2025-04-01 16:41 (UTC) (edited on 2025-04-01 16:42 (UTC) by Neurognostic)

sha256sum for the main tar ball was updated in the .SRCINFO, but not the PKGBUILD[1], leading to a checksum failure during build.

[1]: https://aur.archlinux.org/cgit/aur.git/commit/?h=mullvad-browser-bin&id=65506a5c4bfcb73f99772bc02b1446a7c4f825fa

cyberpunkrocker commented on 2025-01-06 14:56 (UTC) (edited on 2025-01-06 14:57 (UTC) by cyberpunkrocker)

It might be better to replace the pipewire-pulse optional dependency with strict dependency of pulse-native-provider meta package. That package pulls in pipewire-pulse automatically according to whether the user is using pulseaudio or pipewire.

lvgr commented on 2024-11-30 14:26 (UTC)

Hello, I think the maintainer could add pipewire-pulse as an optional dependency for having working audio if one is using PipeWire and not PulseAudio. Recently I've had this problem that no audio stream would play, but I've fixed it by installing that package, so I think adding it to the list of optional dependencies could be useful for other people.

Reference: https://github.com/mullvad/mullvad-browser/issues/334

tarball commented on 2024-09-06 22:08 (UTC) (edited on 2025-02-16 16:16 (UTC) by tarball)

I try to avoid changing more configuration than is absolutely necessary, especially in a browser that's built around the idea of sharing the same fingerprint for all users.

edit: nevermind, it doesn't seem to have any effect on the fingerprint. I'll push an update along with the next version.

Automatic updates can also be disabled by letting the browser know that it's managed by an external package manager. 13.5 added some checks for it, and IIUC it was also supposed to introduce a check for @/system-install (which has been created by this package from the beginning because it's needed for some other things), but it looks like nothing came of it.

Instead, they added a check for @/is-packaged-app. If you're feeling adventurous, run:

# touch /opt/mullvad-browser/is-packaged-app

and see if it helps. It works for me, so I'll test it for a couple more days and then push an update if nothing else breaks.

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