See the Security and Bug Fixes Section - Grub EFI Install Updates Fix Sticky


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] Install Updates - Spotify and Proton VPN keys
#1
Hi All,

Anybody who can help me out with below error log? Updates not working.


Thanks!

Sam


===========================
Install Updates Error Log
===========================

Install Updates could not fetch the package cache information lists.
Go to https://www.linuxliteos.com/forums/ and paste the log below into
a new or existing thread for assistance.

============ Log ===========

Hit:1 http://mirror.koddos.net/linuxlite galena InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 https://linux.teamviewer.com/deb stable InRelease
Get:5 https://repo.protonvpn.com/debian stable InRelease [2,967 B]
Hit:6 https://packages.microsoft.com/repos/edge stable InRelease
Hit:7 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Get:2 https://repository.spotify.com stable InRelease [3,316 B]
Hit:8 https://ppa.launchpadcontent.net/mozilla...ext/ubuntu noble InRelease
Hit:9 https://packages.mozilla.org/apt mozilla InRelease
Hit:10 http://mirror.serverion.com/ubuntu noble InRelease
Hit:11 http://mirror.serverion.com/ubuntu noble-updates InRelease
Err:5 https://repo.protonvpn.com/debian stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EDA3E22630349F1C
Hit:12 http://mirror.serverion.com/ubuntu noble-backports InRelease
Err:2 https://repository.spotify.com stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C85668DF69375001
Hit:13 http://mirror.serverion.com/ubuntu noble-security InRelease
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.protonvpn.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EDA3E22630349F1C
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
W: GPG error: https://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C85668DF69375001
E: The repository 'http://repository.spotify.com stable InRelease' is not signed.
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
Reply
#2
You've got a couple of problems with software that you've added to the system, but

Can you tell us what instructions you followed to install these two packages and any error messages during the installs ?
Spotify
Proton VPN

Do you have a System Restore Utility (Timeshift) snapshot taken before adding these packages ?
stevef
clueless
Reply
#3
(Yesterday, 01:14 PM)stevef Wrote: You've got a couple of problems with software that you've added to the system, but

Can you tell us what instructions you followed to install these two packages and any error messages during the installs ?
Spotify
Proton VPN

Do you have a System Restore Utility (Timeshift) snapshot taken before adding these packages ?

I'm afraid I don't know (anymore) about Proton and Spotify instructions or errors..... :-(  It's a couple of months ago and more important I guess, no snapshot too.

Removing Proton and Spotify will not solve this I think?

(Yesterday, 01:59 PM)SamBC Wrote:
(Yesterday, 01:14 PM)stevef Wrote: You've got a couple of problems with software that you've added to the system, but
Can you tell us what instructions you followed to install these two packages and any error messages during the installs ?
Spotify
Proton VPN
Do you have a System Restore Utility (Timeshift) snapshot taken before adding these packages ?

I'm afraid I don't know (anymore) about Proton and Spotify instructions or errors..... :-(  It's a couple of months ago and more important I guess, no snapshot too.
Removing Proton and Spotify will not solve this I think?


Removed those two (don't use them anyway on this laptop); new/current error log (still both there:
===========================
Install Updates Error Log
===========================

Install Updates could not fetch the package cache information lists.
Go to https://www.linuxliteos.com/forums/ and paste the log below into
a new or existing thread for assistance.

============ Log ===========

Hit:1 http://mirror.koddos.net/linuxlite galena InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 https://linux.teamviewer.com/deb stable InRelease
Hit:5 https://packages.microsoft.com/repos/edge stable InRelease
Get:6 https://repo.protonvpn.com/debian stable InRelease [2,967 B]
Hit:7 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Get:2 https://repository.spotify.com stable InRelease [3,316 B]
Hit:8 https://ppa.launchpadcontent.net/mozilla...ext/ubuntu noble InRelease
Hit:9 https://packages.mozilla.org/apt mozilla InRelease
Err:6 https://repo.protonvpn.com/debian stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EDA3E22630349F1C
Err:2 https://repository.spotify.com stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C85668DF69375001
Hit:10 http://mirror.serverion.com/ubuntu noble InRelease
Get:11 http://mirror.serverion.com/ubuntu noble-updates InRelease [126 kB]
Get:12 http://mirror.serverion.com/ubuntu noble-backports InRelease [126 kB]
Get:13 http://mirror.serverion.com/ubuntu noble-security InRelease [126 kB]
Get:14 http://mirror.serverion.com/ubuntu noble-updates/main amd64 Components [164 kB]
Get:15 http://mirror.serverion.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:16 http://mirror.serverion.com/ubuntu noble-updates/universe amd64 Components [377 kB]
Get:17 http://mirror.serverion.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:18 http://mirror.serverion.com/ubuntu noble-backports/main amd64 Components [7,076 B]
Get:19 http://mirror.serverion.com/ubuntu noble-backports/restricted amd64 Components [216 B]
Get:20 http://mirror.serverion.com/ubuntu noble-backports/universe amd64 Components [28.4 kB]
Get:21 http://mirror.serverion.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Get:22 http://mirror.serverion.com/ubuntu noble-security/main amd64 Components [21.5 kB]
Get:23 http://mirror.serverion.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:24 http://mirror.serverion.com/ubuntu noble-security/universe amd64 Components [52.3 kB]
Get:25 http://mirror.serverion.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.protonvpn.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EDA3E22630349F1C
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
W: GPG error: https://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C85668DF69375001
E: The repository 'http://repository.spotify.com stable InRelease' is not signed.
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
Reply
#4
Quote:Removing Proton and Spotify will not solve this I think?

To get the update/upgrade working again you can do one of the following
1) Fix the failed installations so that update/upgrade works and you have the functionality of the applications.
2) Reverse all the steps of the failed installations so that the applications are completely removed.
3) Make the update/upgrade process ignore the failed installations.

Options 1 and 2 are technically neater, but rely on knowing the installation methods used or have a viable snapshot.
Option 3 is a bodge.

The choice depends on your answers to these questions.
Are the Spotify and ProtonVPN applications working ?
Do you need them ?
stevef
clueless
Reply
#5
(Yesterday, 02:21 PM)stevef Wrote:
Quote:Removing Proton and Spotify will not solve this I think?

To get the update/upgrade working again you can do one of the following
1) Fix the failed installations so that update/upgrade works and you have the functionality of the applications.
2) Reverse all the steps of the failed installations so that the applications are completely removed.
3) Make the update/upgrade process ignore the failed installations.

Options 1 and 2 are technically neater, but rely on knowing the installation methods used or have a viable snapshot.
Option 3 is a bodge.

The choice depends on your answers to these questions.
Are the Spotify and ProtonVPN applications working ?
Do you need them ?

Removing and reinstalling Spotify was the solution. After that the updates ran like a charm and everything is up to date again.

Thanks for the assistance!
Reply


Forum Jump:


Users browsing this thread: