Install on Ubuntu. Go to Spotify in Ubuntu Software and click install. If the link doesn’t work, open Ubuntu Software and search for Spotify. Install via command line Snap. If you don’t have access or don’t want to use Ubuntu Software, it is possible to install Spotify from the command line with snap. Run the following command in your. Install on Ubuntu. Go to Spotify in Ubuntu Software and click install. If the link doesn’t work, open Ubuntu Software and search for Spotify. Install via command line Snap. If you don’t have access or don’t want to use Ubuntu Software, it is possible to install Spotify from the command line with snap. Run the following command in your. To get rid of it, you have to delete the repository file. It's in /etc/apt/sources.list.d/ and it is named like spotify.list or similar. Aug 22 '18 at 5:49.
Package Details: spotify 1:1.1.42.622-2Package Actions
Dependencies (12)
Required by (18)
NicoHood commented on 2020-05-27 07:46
The package has been flagged out of date again. I want to remind, that we package the stable version of spotify, not the testing version. Stable versions can be found under the following link and have not been updated for a long time:http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages
You can fix the GPG key issue by using:
DaleYYC commented on 2020-11-17 13:32
> Validating source files with sha512sums.. spotify.protocol .. Passed LICENSE .. Passed spotify-1.1.42.622-Release .. Skipped spotify-1.1.42.622-Release.sig .. Skipped> Validating source_x86_64 files with sha512sums.. spotify-1.1.42.622-x86_64.deb .. Passed spotify-1.1.42.622-x86_64-Packages .. Passed> Verifying source file signatures with gpg.. spotify-1.1.42.622-Release .. FAILED (unknown public key D1742AD60D811D58)> ERROR: One or more PGP signatures could not be verified!
techandy1 commented on 2020-11-14 03:01
@renatoliveira thank you for your input. It finally worked for me.
ClickTek commented on 2020-11-13 03:41> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
--I kept getting this during the download but after spamming to keep trying it after the 5th time it just went through.
ajzcole commented on 2020-11-12 21:28
I get this error:
Clean building does not fix the issue. Neither does a manual wipe of the cache.
EDIT: After installing
gtk2 and gobject-introspection manually, everything was fine.
deafwhippin commented on 2020-11-10 23:53
I'm also having issues installing Spotify having followed all the suggestions below to add GPG keys. Here's the output I receive:
EDIT (16/11/2020): Saw ClickTek's comment to continuously retry. Spotify finally pushed through and installed from cleanbuild.
TheIdealis commented on 2020-11-10 14:51
Just in case someone who has the gpg problems made the same silly mistake I did: I removed
~/.cache/yay/spotify but tried to install spotify-dev . After I removed both, I was able to install the program again.
renatoliveira commented on 2020-11-09 12:41
@techandy1 the difference between PGP and GPG is that one is the private solution developed by Symantec and the other one is the open source implementation. Since GPG is just an implementation of PGP, the correct naming would still be 'PGP key'.
I'm confused. Deleting the cache did not work for you? I would take a look into the previous 3 or 4 pages in the comments. Some commands were mentioned to clear the cache and reinstall the package.
As for anyone reading this: Spotify changed PGP keys used to sign the package, again. It is using a key that was used before, again. It is necessary to trust that key to install (or ignore signatures during install).
techandy1 commented on 2020-11-08 21:26
I am having issues with the GPG keys. None of the suggestions below have worked for me. I am still unable to update Spotify. Does anybody else have any suggestions?? I have also noticed that the validpgpkeys have not been updated in the PKGBuild file and also I thought it would be a validgpgkeys and not validpgpkeys????
voho commented on 2020-11-02 23:14
@kfallah, @bryanOmalley: I also had the same problem. Spotify warning about internet connectivity. I use WireGuard and NetworkManager.
EDIT: Running below should return full , and not limited like it does if I block the connectivity check. If it returns limited Spotify thinks it's offline.
Anyway, I started logging iptables and adding IP's that was being blocked on different interfaces.
https://renewgate637.weebly.com/blog/free-spotify-app-for-macbook-air. What I found out is that apparently NetworkManager does it's own connectivity checking, which Spotify seems to care about.
On my machine:
/usr/lib/NetworkManager/conf.d/20-connectivity.conf :
NetworkManager uses that address for checking connectivity.
The strange thing was that in Wireshark I noticed that even if I was connected to VPN (WireGuard), requests to
138.201.81.199 (archlinux.org) were being sent over both WireGuard and my normal network card.
My firewall/iptables blocked those requests that did not go over VPN. Strange that it would not only go over my VPN connection all the time.
Anyway, so the solution seems to be, either to disable NetworkManager's connectivity checking altogether. Or watching over you firewall / Wireshark to see if you have the same problem. And if so fixing your firewall.
For now I just allowed
138.201.81.199 on my normal network interface, which iptables previously blocked which Spotify noticed.
And Spotify have been working since, time will tell if this was the problem.
jvloendersloot commented on 2020-11-02 13:52
curl not working anymore. Deleting the cache also didn't work.
Package Details: spotify 1:1.1.42.622-2Package Actions
Dependencies (12)
Required by (18)
NicoHood commented on 2020-05-27 07:46
The package has been flagged out of date again. I want to remind, that we package the stable version of spotify, not the testing version. Stable versions can be found under the following link and have not been updated for a long time:http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages
You can fix the GPG key issue by using:
DaleYYC commented on 2020-11-17 13:32
> Validating source files with sha512sums.. spotify.protocol .. Passed LICENSE .. Passed spotify-1.1.42.622-Release .. Skipped spotify-1.1.42.622-Release.sig .. Skipped> Validating source_x86_64 files with sha512sums.. spotify-1.1.42.622-x86_64.deb .. Passed spotify-1.1.42.622-x86_64-Packages .. Passed> Verifying source file signatures with gpg.. spotify-1.1.42.622-Release .. FAILED (unknown public key D1742AD60D811D58)> ERROR: One or more PGP signatures could not be verified!
techandy1 commented on 2020-11-14 03:01
@renatoliveira thank you for your input. Can you stream free spotify on amazon dot. It finally worked for me.
ClickTek commented on 2020-11-13 03:41> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
--I kept getting this during the download but after spamming to keep trying it after the 5th time it just went through.
ajzcole commented on 2020-11-12 21:28
I get this error:
Clean building does not fix the issue. Neither does a manual wipe of the cache.
EDIT: After installing
gtk2 and gobject-introspection manually, everything was fine.
deafwhippin commented on 2020-11-10 23:53
I'm also having issues installing Spotify having followed all the suggestions below to add GPG keys. Here's the output I receive:
EDIT (16/11/2020): Saw ClickTek's comment to continuously retry. Spotify finally pushed through and installed from cleanbuild.
TheIdealis commented on 2020-11-10 14:51
Just in case someone who has the gpg problems made the same silly mistake I did: I removed
~/.cache/yay/spotify but tried to install spotify-dev . After I removed both, I was able to install the program again.
renatoliveira commented on 2020-11-09 12:41
@techandy1 the difference between PGP and GPG is that one is the private solution developed by Symantec and the other one is the open source implementation. Since GPG is just an implementation of PGP, the correct naming would still be 'PGP key'.
I'm confused. Deleting the cache did not work for you? I would take a look into the previous 3 or 4 pages in the comments. Some commands were mentioned to clear the cache and reinstall the package.
As for anyone reading this: Spotify changed PGP keys used to sign the package, again. It is using a key that was used before, again. It is necessary to trust that key to install (or ignore signatures during install).
techandy1 commented on 2020-11-08 21:26
I am having issues with the GPG keys. None of the suggestions below have worked for me. I am still unable to update Spotify. Does anybody else have any suggestions?? I have also noticed that the validpgpkeys have not been updated in the PKGBuild file and also I thought it would be a validgpgkeys and not validpgpkeys????
voho commented on 2020-11-02 23:14
@kfallah, @bryanOmalley: I also had the same problem. Spotify warning about internet connectivity. I use WireGuard and NetworkManager.
EDIT: Running below should return full , and not limited like it does if I block the connectivity check. If it returns limited Spotify thinks it's offline.
Anyway, I started logging iptables and adding IP's that was being blocked on different interfaces.
What I found out is that apparently NetworkManager does it's own connectivity checking, which Spotify seems to care about.
On my machine:
/usr/lib/NetworkManager/conf.d/20-connectivity.conf :
NetworkManager uses that address for checking connectivity. Is spotify free now on iphone xr.
The strange thing was that in Wireshark I noticed that even if I was connected to VPN (WireGuard), requests to
138.201.81.199 (archlinux.org) were being sent over both WireGuard and my normal network card.
My firewall/iptables blocked those requests that did not go over VPN. Strange that it would not only go over my VPN connection all the time.
Anyway, so the solution seems to be, either to disable NetworkManager's connectivity checking altogether. Or watching over you firewall / Wireshark to see if you have the same problem. And if so fixing your firewall.
Ubuntu Failed To Download Repository Information
For now I just allowed
138.201.81.199 on my normal network interface, which iptables previously blocked which Spotify noticed.
And Spotify have been working since, time will tell if this was the problem.
Spotify Stable Ubuntu Failed To Download Repository Information Repositoryjvloendersloot commented on 2020-11-02 13:52Spotify Stable Ubuntu Failed To Download Repository Information Search
curl not working anymore. Deleting the cache also didn't work.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |