Vivaldi browser and the packagekit

[alexsid]

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?

[eriefisher]

Fix your key problem like it says.
https://linuxcapable.com/how-to-install-vivaldi-browser-on-debian-linux/

[alexsid]

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.
-----------------------------------------

[towo]

Don't use 3rd-party-repos if you have no skill,  to handle them.

[alexsid]

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?

[eriefisher]

The point of the link was to show you how to add the key. Your error shows you have a key issue.

[alexsid]

The point of the link was to show you how to add the key. Your error shows you have a key issue.

HOW?

[eriefisher]

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.

[Camelot]

About packagekit: packagekit-tools is obsolete, and some tools have been merged into the packagekit package.
Install packagekit and uninstall packagekit-tools.

Changelog:

* 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

Code Select Expand

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

[alexsid]

Code Select Expand

[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.

[alexsid]

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.

[eriefisher]

Missing key 8D1FA52AEF58A09D889DD4221256C34716BD9233, which is needed to verify signature.

Your missing the key.

Import Vivaldi GPG Key and Repository

To begin, download and install Vivaldi's GPG signing key, which APT uses to verify package authenticity:

Code Select Expand

curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg

[michaa7]

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.

Code Select Expand

curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | (sudo) gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg
does nothing if you have older gpg keys installed.

I have no clue how to solve the problem this time.

OpenPGP-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.

-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.

[unklarer]

The given procedure would work here...   

Code Select Expand

curl -fsSL https://repo.vivaldi.com/archive/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi.gpg


Code Select Expand

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. 

Code Select Expand

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?

[Pip]

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.

Code Select Expand

wget -qO- https://repo.vivaldi.com/stable/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/vivaldi-browser.gpg

Code Select Expand

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

Code Select Expand

sudo apt -qq update

Code Select Expand

sudo apt -qq full-upgrade