Content
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.
Before connect to NordVPN
However, since the ARM team changed and not all supported devices are at our end for testing, less updates were made to arm-stable branch. Device images are currently only auto-generated but not tested at all. There will be some updates to arm-unstable branch, but those might be just kernels or few packages.
Troubleshooting NordVPN on Manjaro
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.
Status of ARM Stable Updates: No Major Update Since March 2024?
Such as, KDE Plasma 6.4 being released today (6/17). I usually install the most recent LTS kernel (currently linux612), and the latest kernel. Although I’m holding off installing linux616 (which is still a release candidate) until the next RC version arrives, as the current RC prevents my system from waking up. Systemctl enable sshd still works for me; it creates the sshd.service symlink as expected.
In my work I use extensions available only on Chrome. I personally recommend Firefox, but it might be worth your effort to try a major Chromium-based alternative such as Vivaldi, in case they have already dealt with the issue. An obvious workaround is to use another (non-Chromium-based) browser until whatever the issue may be is fixed upstream. A reminder that Chrome has frequent recent updates, which may or may not be reflected when sourcing it via the AUR.
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.
Morc_menu on i3 stopped working (conflicting w/ dmenu-manjaro or manjaro-i3-settings?)
The workaround would at least help minimise disruption of your workflow until the actual cause and solution is discovered. Those plinko browsers that feature their own “addon store” usually have a setting to also allow addons from the Google counterpart. I’ve tried searching around for this issue a lot on the internet and got no luck.
On ARM side this happens not so often or for some months not at all. I use Manjaro ARM headless in production for Pi-hole and the SmartHome system ioBroker, so I prefer the stable branch. Even though the unstable branch is currently running well, there’s no guarantee it will always be like that.
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.
The only items left standing are dmenu-manjaro, which depends on manjaro-i3-settings which was also recently updated. I had to scale back my work since my heart attack. I build the 6 new latest pi kernels a week along with the boot related packages and eeprom and push them to unstable. So, I wonder if there’s a way I could support you. I still have a Pi4 in my drawer and could install the latest ARM testing update on it in the coming days. Then, I’d be happy to test how it works with my configuration, especially with pi-hole and ioBroker, and report back to you.