Installing openresolv fixed this issue for me and now my /etc/resolv.conf is updating correctly.
Search Criteria
Package Details: mullvad-vpn 2024.7-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mullvad-vpn.git (read-only, click to copy) |
---|---|
Package Base: | mullvad-vpn |
Description: | The Mullvad VPN client app for desktop |
Upstream URL: | https://www.mullvad.net |
Licenses: | GPL-3.0-or-later |
Submitter: | gin078 |
Maintainer: | yochananmarqos |
Last Packager: | yochananmarqos |
Votes: | 137 |
Popularity: | 2.73 |
First Submitted: | 2018-10-24 17:33 (UTC) |
Last Updated: | 2024-10-30 16:32 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- iputils (busybox-coreutilsAUR, iputils-gitAUR)
- libnftnl (libnftnl-fullconeAUR, libnftnl-gitAUR)
- libnotify (libnotify-gitAUR)
- nss (nss-hgAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, go-sylixosAUR, gcc-go) (make)
- libxcrypt-compat (make)
- nvmAUR (nvm-gitAUR) (make)
- protobuf (protobuf-gitAUR) (make)
Required by (3)
Sources (7)
- git+https://github.com/mullvad/maybenot.git#commit=b06094e81701782d28cd2312f58e0654109d04ce
- git+https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=049d5d3bc0c86c29c20f2073460186a83c1d7094?signed
- git+https://github.com/mullvad/mullvadvpn-app.git#tag=2024.7?signed
- git+https://github.com/mullvad/wireguard-go.git#commit=b1cf09a982bba6f6c63fadc956d88e8c2326d05e?signed
- mullvad-vpn.sh
- no-publish.diff
- no-rpm.diff
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 45 Next › Last »
stmrllr commented on 2021-01-10 13:04 (UTC)
Zenzio commented on 2021-01-10 11:53 (UTC) (edited on 2021-01-10 11:55 (UTC) by Zenzio)
Just a quick update: Installing the beta (bin or non-bin) did not help in my case. Though I am using the non-bin beta now. I ended up downgrading openresolv and networkmanager (not sure which one of those helped). If anybody notices this issue being fixed kindly drop a word about it here, please. Thank you!
Zenzio commented on 2021-01-09 19:07 (UTC)
Mhh. I did everything the way you did it with the tiny exception that I manually removed mullvad-vpn before installing the beta (yay -Rns mullvad-vpn). Rebooting hasn't helped for now. If nothing changes I might try doing the same and installing the bin package this time... Anyway, thank you for your help.
null_matter commented on 2021-01-09 18:12 (UTC)
Yes I had to reboot my system. I use yay as my AUR helper. When I installed mullvad-vpn-beta-bin it prompted me to remove the mullvad-vpn-bin package, which I did.
Then it didn't work, and I went to bed, and in the morning after rebooting it worked. So maybe reboot?
Zenzio commented on 2021-01-09 17:12 (UTC) (edited on 2021-01-09 17:14 (UTC) by Zenzio)
So are you saying switching to the beta helped you? But not at first? I just switched to it (the non-bin package 2020.8.beta2-2) and for now it doesn't seem to help. Do I need to do something besides uninstalling the stable version and a clean build of the beta and restarting my system? Did you do something else before it started working again?
stmrllr commented on 2021-01-09 15:14 (UTC) (edited on 2021-01-09 15:29 (UTC) by stmrllr)
I'm having the same problem with DNS, /etc/resolv.conf doesn't get updated with the Mullvad name server. It's kind of complicated bug at the moment, since the GUI isn't starting either. It shows in processes but I can't get it to show on desktop.
null_matter commented on 2021-01-09 14:34 (UTC) (edited on 2021-01-09 14:35 (UTC) by null_matter)
edit: this is a fix for the DNS issue
I requested feedback via the app and they told me to download the beta: "Please try our latest beta which should resolve this issue in most cases."
I installed the AUR package mullvad-vpn-beta-bin which is 2020.8.beta2-1 and at first it didn't work, I rebooted this morning and now it's working. I'm using the bin version because for some reason I can't build the mullvad package from source. So I would try to install mullvad-vpn-beta or mullvad-vpn-beta-bin and reboot. Cheers!
Zenzio commented on 2021-01-09 13:53 (UTC)
I don't know if I should post about this here. But as the post before mine states: After the system update (networkmanager and openresolv got updated) my system can't connect to anything anymore while Mullvad-VPN is active. It's fine while Mullvad-VPN is not connected. Is this a bug with one of the updated packages? Any pointers?
cedricbambooza commented on 2021-01-09 08:40 (UTC) (edited on 2021-01-09 08:40 (UTC) by cedricbambooza)
Mullvad VPN via App not working after Update of NetworkManager and reboot....
I'm getting an ERR_Name not Resolved Message when opening the Browser, I close the Mullvad App and voila I can visit kernel.org
Mullvad VPN App also connects to the servers just fine, "simply" DNS request don't seem to work anymore.
Rehls commented on 2020-11-27 06:22 (UTC)
Installing via makepkg worked w/o issue for me, thanks!
Yay just would not let me get past the PGP key importing step, even when I had manually added them: ==> :: (1/1) Parsing SRCINFO: mullvad-vpn
:: PGP keys need importing:
-> EA0A77BF9E115615FC3BD8BC7653B940E494FE87, required by: mullvad-vpn
-> 8339C7D2942EB854E3F27CE5AEE9DECFD582E984, required by: mullvad-vpn
==> Import? [Y/n]
:: Importing keys with gpg...
gpg: keyserver receive failed: General error
problem importing keys
Pinned Comments
yochananmarqos commented on 2022-11-11 19:31 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)
PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use
mullvad-vpn-bin
instead.yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2024-06-06 22:09 (UTC) by yochananmarqos)
--> ALWAYS DO A CLEAN BUILD <--
This package will verify the signature of the git tag / commit. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.
Please do not create upstream issues about the AUR package, they do not support it.