Seems like it messes up spotify client. Somebody needs to verify that. Spotify opens normally, but all songs are greyed out and you can’t play them. Besides that you can control other playing devices as expected.
When running from terminal error appears: /usr/lib/libcurl-gnutls.so.4: no version information available
But it’s some old bug.
EDIT: seems like killing NetworkManager solves the problem.
FIX for now - disable NetworkManager connectivity check: echo -en "[connectivity]\n.set.enabled=false" | sudo tee /etc/NetworkManager/conf.d/20-connectivity.conf sudo systemctl restart NetworkManager
Today has been my initiation with the connectivity check. I’ve never seen it before and had no idea what was wrong. In addition to limited connectivity notices, wifi connects fine but with another notice saying “unable to reach the internet” which sent me to the router’s reset button, among other things.
Before this thread was started I found the same post@acarasimon96 mentions and it helped get Manjaro online without the exclamation mark. I’m relieved and glad to have my sanity back regardless of when it’s ok to remove 20-connectivity.conf.
This is the first time I realized there was such a limited method for determining if you have internet connectivity. It really threw me off and I wasted a lot of time troubleshooting a virtual machine (to run Manjaro for testing certain scenarios) because I thought I misconfigured my network settings.
There should be multiple URLs to check for internet connectivity, and a further fallback IP address, such as 1.1.1.1 to see if it’s only DNS-related.
It’s NetworkManager that does the connectivity check, not KDE Plasma as I initially thought. As you can see, the issue has affected other people in the forum too and I assume they run other DEs in addition to Plasma. NetworkManager started as a Gnome project after all…
I found an older thread here that outlines there are 2 places the config could be. I found mine under /usr/lib/NetworkManager/conf.d/20-connectivity.conf
I have tried just commenting out all settings to see if It can just be ignored as I am on a Desktop at home with ethernet not wifi.
I think it would be great to move this to something like a Cloudflare page with a worker to set the required headers. that way we can use the always online feature to ensure even when the website has work to do it won’t cause this issue.