The system cannot update Vivaldi browser stable. After sudo apt update I get the following message:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://repo.vivaldi.com/archive/deb stable Release: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.
What shall I do? Wait?
The following update was skipped during the latest update:
packagekit
Why?
Fix your key problem like it says.
https://linuxcapable.com/how-to-install-vivaldi-browser-on-debian-linux/
Quote from: eriefisher on 2026/01/30, 12:10:29
Fix your key problem like it says.
https://linuxcapable.com/how-to-install-vivaldi-browser-on-debian-linux/
Thank you. I followed the link kindly provided by you and did everything step by step and managed to reinstall Vivaldi. I have the latest version now, but when I do
sudo apt update
I still get the error:
-----------------------------------------
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://repo.vivaldi.com/archive/deb stable Release: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.
-----------------------------------------
Don't use 3rd-party-repos if you have no skill, to handle them.
Quote from: towo on 2026/01/30, 14:21:42
Don't use 3rd-party-repos if you have no skill, to handle them.
Your advice is good but it does not answer the question.
I installed Vivaldi several months ago and had no issues until now.
What shall I do to resolve the missing key issue? Shall I remove Vivaldi?
And what about
packagekit
skipping update?
The point of the link was to show you how to add the key. Your error shows you have a key issue.
Quote from: eriefisher on 2026/01/30, 14:46:44
The point of the link was to show you how to add the key. Your error shows you have a key issue.
HOW?
In the link scroll down to "Import Vivaldi GPG Key and Repository" and follow what it says. You have the repo so that shouldn't be an issue.
Did you read the link at all?
I don't know about packagekit. apt Solver could be holding it back because of a mismatch somewhere. I'm not having that issue.
About packagekit: packagekit-tools (https://packages.debian.org/forky/packagekit-tools) is obsolete, and some tools have been merged into the packagekit package.
Install packagekit and uninstall packagekit-tools.
Changelog (https://metadata.ftp-master.debian.org/changelogs/main/p/packagekit/packagekit_1.3.4-1_changelog):
Quote* New upstream version: 1.3.4
* Drop packagekit-tools package
- The pkcon/pkmon tools are obsolete, and the replacement `pkgcli` tool
is available in the main package. The old split into a separate -tools
package was for historical reasons only.
- Nothing in Debian uses pkcon, and there is plenty of time to adjust any
scripts while this change sits in unstable/testing. But if there is a
huge, justifiable need to reintroduce pkcon, we can add the -tools
package back (please file a bug in that case). The `pkgcli` utility
should be an adequate replacement for both pkcon & pkmon.
* Update symbols file
-- Matthias Klumpp <mak@debian.org> Wed, 28 Jan 2026 21:28:30 +0100
apt full-upgrade
Not upgrading:
packagekit
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1
apt install packagekit
Upgrading:
packagekit
REMOVING:
packagekit-tools
Summary:
Upgrading: 1, Installing: 0, Removing: 1, Not Upgrading: 0
(...)
Continue? [Y/n] y
[quote author=Camelot link=topic=9892.msg78636#msg78636 date=1769792712]
REMOVING:
packagekit-tools
Summary:
Upgrading: 1, Installing: 0, Removing: 1, Not Upgrading: 0
(...)
Continue? [Y/n] y
[/quote]
Thanks! I did it and everything is OK. No issues.
Quote from: eriefisher on 2026/01/30, 16:03:53
In the link scroll down to "Import Vivaldi GPG Key and Repository" and follow what it says. You have the repo so that shouldn't be an issue.
Did you read the link at all?
I don't know about packagekit. apt Solver could be holding it back because of a mismatch somewhere. I'm not having that issue.
Here goes the whole error message. I can see no "Import Vivaldi GPG Key..." message.
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://repo.vivaldi.com/archive/deb stable Release: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.
Quote from: alexsid on 2026/01/30, 22:09:12
Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.
Your missing the key.
QuoteImport Vivaldi GPG Key and Repository
To begin, download and install Vivaldi's GPG signing key, which APT uses to verify package authenticity:
curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg
The commands you provide with your link donot solve the problem. I'am a vivaldi user since years, and most vivaldi upgrades went well. But I had those gpg problems in the past, happens about once a year.
curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | (sudo) gpg --dearmor -o /usr/share/keyrings/vivaldi.gpgdoes nothing if you have older gpg keys installed.
I have no clue how to solve the problem this time.
QuoteOpenPGP-Signaturüberprüfung fehlgeschlagen: https://repo.vivaldi.com/archive/deb stable Release: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.
Quote-rw-r--r-- 1 root root 2285 24. Jan 06:25 vivaldi-16BD9233.gpg
-rw-r--r-- 1 root root 2285 15. Jan 2025 vivaldi-33EAAB8E.gpg
-rw-r--r-- 1 root root 2285 24. Jan 06:25 vivaldi-74C35BC8.gpg
-rw-r--r-- 1 root root 2285 21. Dez 2022 vivaldi-C27AA466.gpg
-rw-r--r-- 1 root root 2285 27. Jan 02:25 vivaldi-snapshot-16BD9233.gpg
-rw-r--r-- 1 root root 2285 9. Jan 2025 vivaldi-snapshot-33EAAB8E.gpg
-rw-r--r-- 1 root root 2285 11. Jan 2024 vivaldi-snapshot-4218647E.gpg
-rw-r--r-- 1 root root 2285 27. Jan 02:25 vivaldi-snapshot-74C35BC8.gpg
-rw-r--r-- 1 root root 2285 10. Jan 2023 vivaldi-snapshot-C27AA466.gpg
To it seems the key IS there.
???
The given procedure would work here... ;D
curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg
sudo apt update
OK:1 http://deb.debian.org/debian trixie InRelease
OK:2 http://security.debian.org/debian-security trixie-security InRelease
Holen:3 http://deb.debian.org/debian trixie-updates InRelease [47,3 kB]
Ign:4 https://repo.vivaldi.com/stable/deb stable InRelease
OK:5 https://pkg.bunsenlabs.org/debian carbon InRelease
Holen:6 https://repo.vivaldi.com/stable/deb stable Release [3.840 B]
Holen:7 https://repo.vivaldi.com/stable/deb stable Release.gpg [833 B]
Holen:8 https://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1.558 B]
OK:9 https://apt.hatcherylinux.org gila InRelease
Es wurden 53,6 kB in 1 s geholt (99,2 kB/s).
Alle Pakete sind aktuell.
apt-cache policy vivaldi-stable
vivaldi-stable:
Installiert: (keine)
Installationskandidat: 7.8.3925.56-1
Versionstabelle:
7.8.3925.56-1 500
500 https://repo.vivaldi.com/stable/deb stable/main amd64 Packages
7.7.3851.67-1 500
500 https://repo.vivaldi.com/stable/deb stable/main amd64 Packages
Where is the problem?
I had this myself a couple of days ago - it happens every now and then, as it should, when a key expires - and decided to change my .list to a .source while I was doing it. Used a slightly different but exactly the same approach to getting the key.
wget -qO- https://repo.vivaldi.com/stable/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi-browser.gpg
cat /etc/apt/sources.list.d/vivaldi.sources
Types: deb
URIs: https://repo.vivaldi.com/stable/deb/
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/vivaldi-browser.gpg
sudo apt -qq update
sudo apt -qq full-upgrade
Quote from: michaa7 on 2026/01/31, 02:20:06
The commands you provide with your link donot solve the problem.
The command works fine. The fact that it did not solve your problem is another issue. Can you verify there is a /usr/share/keyrings/vivaldi.gpg after the command is run. Does you .sources file point to the correct directory/file?
Keys expire. You could be pointing to expired keys.
I did not mean to doubt the functionality of the command for you or others. It worked ... without any visible output on the CL and no funcionality change. It only showed a new prompt.
/usr/share/keyrings/vivaldi.gpg was there before as was and is /etc/apt/keyrings/vivaldi.gpg, the "missing" key was and is available, the signed-by line worked for month and years and it points to the allegedly missing key in /etc/apt/keyrings/vivaldi.gpg. But I tried /usr/share/keyrings/vivaldi.gpg too, to no avail.
so I have not the slightes clue why a setting which was working for month and years (and is once a year failing due to gpg missfunctionality) does not work this time.
@michaa7 I'm not quite certain of the data you've sent through and I'm hoping you can explain it: you've shown a list of gpg files with vivaldi in the name, all individual with an identifier. Are these all within your keyrings directory? Which one does your sources file point to? You suggest that the update won't work if old keys are in place, but why are they in place? Your sources file should only be pointing to the current one, so the old keys would not even be consulted as they wouldn't match what's in your "Signed-By:" line. Sorry if I'm not following what you've stated properly. Perhaps you could give the output of
ls -l /usr/share/keyrings/vivaldi*
(if that isn't what you showed before), and a
cat /etc/apt/sources.list.d/vivaldi.sources
(or whatever the name of your sources/list file is) so that it's clearer to me?
Thanks.
Currently both Signed-By_s are disabled. I used to use /etc/apt/keyrings/vivaldi.gpg at least for the last year, but tried /usr/share/keyrings/vivaldi.gpg now as well, to no avail.
Quote# cat /etc/apt/sources.list.d/vivaldi.sources
Types: deb
URIs: https://repo.vivaldi.com/stable/deb/
Suites: stable
Components: main
#Signed-By: /usr/share/keyrings/vivaldi.gpg
#Signed-By: /etc/apt/keyrings/vivaldi.gpg
Enabled: Yes
I see this error: Warnung: https://repo.vivaldi.com/archive/deb/dists/stable/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/vivaldi.gpg are ignored as the file is not readable by user executing gpgv.
How does apt know about keyring /etc/apt/trusted.gpg.d/vivaldi.gpg if it is commented out?
But strange enough, I do not get any error for vivaldi-snapshot. Apt downloaded the newest snapshot without any complaint, but throws an key-error for vivaldi-stable.
Quote# ls -l /usr/share/keyrings/vivaldi*
-rw-rw-r-- 1 root root 2285 31. Jan 12:22 /usr/share/keyrings/vivaldi-browser.gpg
-rw-r--r-- 1 root root 0 1. Feb 2024 /usr/share/keyrings/vivaldi-browser.gpg.save
-rw-rw-r-- 1 root root 2285 31. Jan 02:04 /usr/share/keyrings/vivaldi.gpg
-rw-r--r-- 1 root root 2285 31. Jan 2025 /usr/share/keyrings/vivaldi.gpg.save
Quote# ls -l /etc/apt/trusted.gpg.d/vivaldi*
-rw-r--r-- 1 root root 2285 1. Feb 06:25 /etc/apt/trusted.gpg.d/vivaldi-16BD9233.gpg
-rw-r--r-- 1 root root 2285 15. Jan 2025 /etc/apt/trusted.gpg.d/vivaldi-33EAAB8E.gpg
-rw-r--r-- 1 root root 2285 1. Feb 06:25 /etc/apt/trusted.gpg.d/vivaldi-5220E3E9.gpg
-rw-r--r-- 1 root root 2285 31. Jan 02:46 /etc/apt/trusted.gpg.d/vivaldi-74C35BC8.gpg
-rw-r--r-- 1 root root 2285 21. Dez 2022 /etc/apt/trusted.gpg.d/vivaldi-C27AA466.gpg
-rw-r--r-- 1 root root 2285 1. Feb 06:25 /etc/apt/trusted.gpg.d/vivaldi-snapshot-16BD9233.gpg
-rw-r--r-- 1 root root 2285 9. Jan 2025 /etc/apt/trusted.gpg.d/vivaldi-snapshot-33EAAB8E.gpg
-rw-r--r-- 1 root root 2285 11. Jan 2024 /etc/apt/trusted.gpg.d/vivaldi-snapshot-4218647E.gpg
-rw-r--r-- 1 root root 2285 1. Feb 06:25 /etc/apt/trusted.gpg.d/vivaldi-snapshot-74C35BC8.gpg
-rw-r--r-- 1 root root 2285 10. Jan 2023 /etc/apt/trusted.gpg.d/vivaldi-snapshot-C27AA466.gpg
Without a Signed-By: in place, apt won't know where your specific key files are. Maybe it tries searching a default, I don't know, but if you uncomment the /usr/share line and delete the /etc/apt line in sources, you should be able to get some output that is consistent with what we would expect, as long as /usr/share/keyrings/vivaldi.gpg is the latest download, as it appears to be.
Quote from: Pip on 2026/02/01, 13:06:05
... delete the /etc/apt line in sources, ....
What do you mean by that?
EDIT: Never mind, got it.
Ok, done the changes. Still the same output of apt.
QuoteWarnung: https://repo.vivaldi.com/archive/deb/dists/stable/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/vivaldi.gpg are ignored as the file is not readable by user executing gpgv.
Is this path cached somewhere?
And
# curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg
still gives me only a new promt. Should I not see some d/l occurring?
Quote from: michaa7 on 2026/02/01, 13:21:11...still gives me only a new promt. Should I not see some d/l occurring?
The -s switch for curl is 'silent', verbose would be -v, so change s to v in the curl part. gpg also has a -v switch for verbose.
Check again if you have besides your *.sources files some .list files around that are active (don't think so, but better check twice;) )
Also, are you running as root? If not (which I almost never do), make it sudo gpg instead of just gpg.
It seems to me the problem is the file Release.gpg in the repo contains an error. I checked it with the help of Kleopatra and it got a warning that the file is wrong.
I see just two ways now. 1. To wait a week and hope Vivaldi fix the error. 2. To delete the poor buggy Vivaldi.
Since I was able to update Vivaldi just a few days ago, I wouldn't think of Vivaldi as being directly the source of the problem. Since we all have the latest siduction in place, it seems unlikely to be the OS as well. As you have made sure the key file is updated and that your sources file points to it, it doesn't seem to be the obvious side of a configuration fault either. I fear I have little to suggest as to where else the problem may lie. Apologies.
Quote from: alexsid on 2026/02/01, 17:32:28
It seems to me the problem is the file Release.gpg in the repo contains an error. I checked it with the help of Kleopatra and it got a warning that the file is wrong.
I see just two ways now. 1. To wait a week and hope Vivaldi fix the error. 2. To delete the poor buggy Vivaldi.
Release.gpg this is not a KEY. The key is called vivaldi.gpg! Release.gpg is an "Isolated OpenGPG Signature". Every file manager will tell you that.
Quote from: towo
Don't use 3rd-party-repos if you have no skill, to handle them.
Again: Why does whoever check "/etc/apt/trusted.gpg.d/vivaldi.gpg" which isn't configured anymore?
Fehl:11 https://repo.vivaldi.com/archive/deb stable Release.gpg
Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring "/etc/apt/trusted.gpg.d/vivaldi.gpg" Caused by: 0: Reading "/etc/apt/trusted.gpg.d/vivaldi.gpg": No such file or directory (os error 2) 1: No such file or directory (os error 2)
EDIT: I for some reason have a secondary vivaldi repo configured. It did not occur to me that it pointed to a different repo, archive instead of stable. It worked until the last days policy change @ vivaldi. After switching archive to stable the error is gone.
Solved.
From your error "Reading "/etc/apt/trusted.gpg.d/vivaldi.gpg": No such file or directory"
The path in you .sources file is "/etc/apt/keyrings/vivaldi.gpg"
Your pointing to the wrong path.
solved (see above).
Thanks.
Good stuff!