Seconded. It seems the new client checks the OS to determine whether it is connected to the internet (the Windows client does that too ). However, the OS is not reliable. In my case, I have internet on Wi-Fi, but not on ethernet (which also consequently has lower routing priority). Disconnecting ethernet temporarily allows Spotify to realize that there is internet, and everything works from there on, even with ethernet reconnected.
Similarly, I'm seeing "No internet connection detected" with the most recent update. This is a bogus message; I use the same machine as a proxy server with WireGuard and my laptop, using this proxy server, has no issues connecting to Spotify.
I am also unable to roll back the changes ("apt-cache madison spotify-client" only shows the most recent version).
Could you please issue a fix for this? Does anyone have instructions for working around this in the interim? I'm far from a networking expert.
@igaoghug Thanks for this. I'm using KDE, and I've known for awhile that the "network connectivity limited" message in Network Manager applet is bogus when you're connected to a VPN, but I didn't know Spotify was relying on that for its own connectivity check. I forgot where the issue specifically lied with Network Manager + VPN, but it'd always say that whenever I'm connected to VPNs.
I've confirmed that Spotify would work immediately as long as I can get Network Manager to not warn that (i.e. disconnecting VPN, then reconnecting to Ethernet). However, Network Manager seemed like it'd re-check connectivity every few minutes, so after I connected to VPN again, it'd warn limited network connectivity again before long.
Anyway, I'm using PIA, and the Linux client has Split Tunneling. For the time being I can confirm that Network Manager will be able to successfully check network connectivity as long as I have the IP address of "networkcheck.kde.org" bypassing VPN (I was thinking of bypassing the "process" for Network Manager applet instead, but the know-how for that is beyond me). Anyway, that in extension will cause Spotify to remain working.
This is more like a temporary solution for me however, so I'd really love it if the Spotify Linux team could think of an alternative connectivity check, instead of relying on the OS for it.