Trouble with update manager

[jorgenask]

Hi guys!

Since yesterday I have gotten this message trying to refresh and check for updates:

"The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct."

and

"An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repository.spotify.com stable InRelease: The following signatures were invalid: EXPKEYSIG EFDC8610341D9410 Spotify Public Repository Signing Key <tux@spotify.com>Failed to fetch http://repository.spotify.com/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG EFDC8610341D9410 Spotify Public Repository Signing Key <tux@spotify.com>Some index files failed to download. They have been ignored, or old ones used instead."

This happens no matter which mirror I choose in software sources.

When I select a new mirror in software sources and click ok to update APT cache , I get this message:

"Failed to downdload repository information, check your internet connection"

This is strange as I do have internet connection.

Any ideas guys ?

[jorgenask]

Update:

I booted the linux mint 19 usb stick just to see if I get the same error there and I did, so apparently nothing wrong with my install.

[Sir Charles]

GPG error: http://repository.spotify.com stable InRelease

Hi,

Seemingly, there is some issue at the moment at Spotify's end. Please see: viewtopic.php?f=90&t=274158

Cheers

[jorgenask]

Thanks!

when I removed Spotify from repositories it works fine

[Sir Charles]

I guess we would need to keep an eye on Spotify to see when the repository is back in order.

[jorgenask]

No it seemes like its more than spotify creating issues, after I disabled updates for spotify it was fine for a while .. but now it is giving me a similar error message as before.

[Moem]

Can we see the error message please?

[expat_tony]

I'm having a similar issue currently.
Here's my error message...

GPG error: http://dl.google.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1397BC53640DB551Failed to fetch https://repo.skype.com/deb/dists/stable ... 4/Packages Hash Sum mismatch
Some index files failed to download. They have been ignored, or old ones used instead.

Having read links to other forums, I'm guessing that what happened with Spotify earlier this year has now happened with Skype.
Can anyone offer self-help advice, or do I have to wait for Skype (or Google???) to fix the repo?
Thanks for your time.

[gm10]

I'm having a similar issue currently.
Here's my error message...

GPG error: http://dl.google.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1397BC53640DB551Failed to fetch https://repo.skype.com/deb/dists/stable ... 4/Packages Hash Sum mismatch
Some index files failed to download. They have been ignored, or old ones used instead.

Having read links to other forums, I'm guessing that what happened with Spotify earlier this year has now happened with Skype.
Can anyone offer self-help advice, or do I have to wait for Skype (or Google???) to fix the repo?
Thanks for your time.

No, those are completely different issues, which is why the forum rules ask you to make your own thread for you own issues, otherwise things just get confusing.

The first error message is because you did not add the google repository correctly. Usually the software that needs it (Google Chrome?) sets it up correctly for you, so I suggest you didn't correctly install that, either. You should just remove that repo and reinstall the software. Otherwise see https://www.google.com/linuxrepositories/.

The second issue can happen if you try to use the repo just when it updates. Simply try again later. It's nothing you can resolve on your end, the issue is with the repository.