Content
Even when you use ARM parts of Manjaro, most likely you will also have some x86_64 machines you might run at your home with Manjaro too. Introduce “Arch Linux Ports” as testbed for unofficial architectures until they are integrated in the main Arch Linux repositories. This integration is meant to provide infrastructure…
After a big update yesterday ssh no longer works although installed
And for the record – I have been using 6.1 all throgh the development stages – and no issues at all. I cannot possible know each and every VPN provider but don’t underestimate the value of knowing this little piece of info. I doubt it was anything to do with the update though. The command mentioned there seemed to fix the problem for me. The topic is a wiki entry – improvements are welcome. All VPN providers maintains compatibility with Ubuntu, Debian and Fedora and as they all use systemd-resolved as DNS resolver, in fact they expect it to be so.
It helps to have always 2 kernels (one of them LTS)
Every now and then the topics on troubleshooting a given VPN provider surfaces and a lot of topics boils down to DNS and for good reason. I try to make a post as each package get’s upgraded in the Raspberry Pi Kernels thread. X86_64 architecture is more active as more people are using it.
The system settings in /etc/resolv.conf is not restored on command nordvpn disconnect but remains using nordvpn dns. I inspected the pamac build folder and unpacked the content of the deb file but I was not able to draw any conclusions – everything appeared to be as it should for a systemd installation. As with all software that’s inherited from Arch, it will first have to go through their process before it arrives in out Unstable branch, and trickling down from there. I have one more question, but I don’t know if it’s appropriate to ask it here. I just wanted to know how quickly Manjaro releases DE version updates.
Using the –disable-gpu option has enabled a temporary fix and allowed accessing the settings to disable graphics acceleration. Google-chrome is in the AUR, and you don’t say what sort of update you did. If you have not already tried, a re-build might help (pamac build google-chrome). My google chrome only works if I call with –disable-gpu.
So, posting here, even if vague, was a last line of defense move. You’ll notice from a quick plinko slot Internet search that these reports are all current, and quite widespread. As of writing, there is no official fix for this issue, but you can use the following workaround.
root tip How To NordVPN on Manjaro
If your installation .ISO came with an LTS kernel and it works OK, I’d generally suggest keeping with that series. But that’s more down to my own preferences and equipment; I’ve had some issues with certain HWE kernels, specifically trackpad related. In terms of dependencies, xdotool and wmutils I’ve had for quite some time and looking at the install dates there were no recent updates. Rofi was updated last month, so I can also eliminate it.
VPN compatibility
It’s possible any issue is with the Chromium/Chrome codebase. In the article on Arch Wiki – systemd-resolved is another tip for the case VPN or DHCP clients expects a working resolvconf binary – it was not necessary to add – but it is good to know it is there. I took a long chat with NordVPN – first the chat-bot – then a human – which – due the complete lack of logfile – repeatedly told me Arch is not supported and they were not able to assist me. Generally, you’d expect an installer (snapshot) to be the latest LTS kernel… so the answer will depend on exactly which snapshot/ISO is downloaded. I believe the .ISOs are now sticking with LTS versions but I will have to check on that.