Just installed Ubuntu 13.10 (Saucy) and anything I try to install via sudo apt-get install is failing and throwing a series of 404 erros. Example - installing tmux jeeves@HAL hadoop sudo apt-get install tmux sudo password for jeeves: Reading package lists. By default, Spotify is not available in Ubuntu 18.04 default repository. So you will need to add the repository for that. First, import the GPG key to your system with the following command. Spotify online app.
Hello linuxquestions.org,
As i stated in the title, when i open the driver manager app it says 'failed to download repository information, check your internet connection'. And then within the driver manager application it states that 'this device is not working' in reference to my intel wireless 7260 (dual band wireless N 7260) driver. There are 3 options but i cant seem to choose them.. My internet connection is fine but when i try to access most websites on chrome it won't open. I did sudo apt-get update and it shows this: Ign:1 http://mirrors.nic.cz/linuxmint-packages tricia InRelease Hit:2 http://mirrors.nic.cz/linuxmint-packages tricia Release Err:3 http://repository.spotify.com stable InRelease Could not resolve ‘repository.spotify.com’ Hit:4 http://ftp.sh.cvut.cz/ubuntu bionic InRelease Hit:5 http://ftp.sh.cvut.cz/ubuntu bionic-updates InRelease Hit:6 http://ftp.sh.cvut.cz/ubuntu bionic-backports InRelease Hit:7 http://netcologne.dl.sourceforge.net/project/d-apt d-apt InRelease Ign:8 http://dl.google.com/linux/chrome/deb stable InRelease Hit:9 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic InRelease Hit:10 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:11 http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu bionic InRelease Hit:13 http://dl.google.com/linux/chrome/deb stable Release Hit:14 http://ppa.launchpad.net/nathan-renn..ck/flux/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/slgobinath/safeeyes/ubuntu bionic InRelease Hit:16 http://archive.canonical.com/ubuntu bionic InRelease Reading package lists.. Done W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease Could not resolve ‘repository.spotify.com’ W: Some index files failed to download. They have been ignored, or old ones used instead. Package Details: spotify 1:1.1.42.622-2Package Actions
To install the Spotify snap package in all currently supported versions of Ubuntu, open the terminal and type: sudo snap install spotify Features of the Spotify free version.
Dependencies (12)
The repository information in your /etc/apt/sources.list.d/spotidy.list file isn't correct and the other commands fail because you haven't actually installed the spotify client yet. Check that the /etc/apt/sources.list.d/spotify.list contais the following line. Deb stable non-free. Sudo apt-get update. This is the Debian package repository of Jenkins to automate installation and upgrade. To use this repository, first add the key to your system: WARNING: The gpg key use to sign our packages has been updated on 16th of April 2020, therefore you need to reimport it if you imported before this date.
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'. Mac play button spotify.
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. Spotify offline download mod.
On my machine:
/usr/lib/NetworkManager/conf.d/20-connectivity.conf :
Failed To Download Repository Information
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.
Ubuntu Failed To Download Repository Info
Spotify premium 8.4.81.558 apk. 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.
Ubuntu Failed To Download Repository Information
And Spotify have been working since, time will tell if this was the problem.
jvloendersloot commented on 2020-11-02 13:52Spotify Stable Ubuntu Failed To Download Repository Information Ubuntu
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 |