NO_PUBKEY error

qazerr

@DoctorG Ubuntu 23.10. But it does not matter. Those are external packages.
Some examples of lists that use signed-by=:
https://packages.microsoft.com/ubuntu/23.10/prod/pool/main/p/packages-microsoft-prod/packages-microsoft-prod_1.1-ubuntu23.10_all.deb
https://repo.steampowered.com/steam/pool/steam/s/steam/steam-launcher_1.0.0.78_all.deb
https://docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linux

edwardp

@DoctorG This message appears with the Linux DEB package of Stable. It's seen when installing Vivaldi for the very first time/or anew, using the DEB package.

Xmetal

I am here after my older (a few months i guess) Vivaldi install started having issues with GPG key messages. I apt removed (not purged) vivaldi-stable and made sure there were no leftover gpg key files or sourcelist files ... then i went to the Vivaldi Homepage and got then newest deb of 6.5 ... install went off with no issues but now apt is not able to do tasks and its complaining about the Vivaldi key again ... not sure what happened here

DoctorG

@Xmetal Check now apt config lists.
Open shell
To check what is stored in sources lists run command
grep -iR "vivaldi" /etc/apt/sources.list /etc/apt/sources.list.d/

Xmetal

/etc/apt/sources.list.d/my-vivaldi.list:deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/packages.vivaldi.gpg] https://repo.vivaldi.com/archive/deb stable main

@DoctorG said in NO_PUBKEY error:

grep -iR "vivaldi" /etc/apt/sources.list /etc/apt/sources.list.d/

Xmetal

@Xmetal i did have vivaldi.list and i think (??) vivaldi-archive.list or something like that before i removed vivaldi trying to fix the issue .. .now in /etc/apt/source.list.d/ (did i typo that?) i do only see my-vivaldi.list when it comes to anything vivaldi related in there ... FYI

DoctorG

@Xmetal I do not understand why you create your own source list with a wrong repo and a user-defined gpg keyring. Weird experments?

fourier

@CtrlAltDel

Missing Keys Issue SOLVED

It works (updates) current versions Vivaldi 6.6, and Linux Mint 21.3 (March 2024...)

as
https://repo.vivaldi.com/archive/deb stable Release:
NO_PUBKEY 124F149833EAAB8EE
repository... not signed

This is a short solution, just in 3 steps, taken from previous messages in forum topic.

https://forum.vivaldi.net/post/740192

Regards,

DoctorG

@fourier You post tips, but you have a broken apt repo configuration – could mislead users.

fourier

OMG, I regret if I did a mess. I
worked fine for me for the first time. The previous URL (terminal install...) does not solved MY issue.

Where (URL) this apt repository information for VIvaldi can be found ?.
It is not cristal clear, neither a manual installation solved apt issue since 5.x/6.0 (I recall that it worked before) . The forum is plenty of unpleased(disoriented) users,

DoctorG

@fourier said in NO_PUBKEY error:

OMG, I regret if I did a mess.

No problem. Such can happen

Where (URL) this apt repository information for VIvaldi can be found ?.

With the old Vivaldi archive repo? As i remember, that could have been a old help page from 3 or more years ago or a tip from an other user.
Oh, or from 2015 or later as a search told me.

Official Linux install is in help page (F1)

edwardp

@DoctorG @fourier I recall seeing this error when installing Vivaldi (Stable) on Debian. But during Snapshot installation, I recall key information being displayed at that point.

But after adding the repos to an RPM-based installation, then installing both Stable and Snapshot at the same time, dnf displays the key information and prompts to install it.

Maybe there is something dnf is doing differently than dpkg?

DoctorG

I doe not imagine why package management on Debian/Ubuntu-alike distributions can fail with apt, but i suffered over the years sometimes with Ubuntu, Debian and Mit from this. Only way to solve it was: uninstall with apt, delete all vivaldi*gpg and install by downloaded package with dpkg.
More insteresting fact: my office PCs (Debian 10,11,12 over the years) did not had such trouble. Only my test Linux installations on my testing workstation. Perhaps i crapped some Mint/Debian/Ubuntu installation? Linux desktop is not my daily work, only Linux servers and Windows PCs.

alexisss0022

@dejanbatic said in NO_PUBKEY error:

I installed Vivaldi last month on Ubuntu with no issues using this:

wget -qO- http://repo.vivaldi.com/stable/linux_signing_key.pub | sudo apt-key add -
sudo add-apt-repository "deb [arch=i386,amd64] http://repo.vivaldi.com/stable/deb/ stable main"
But now when I try it, I get this error after doing
apt-get update:

Ign:7 http://repo.vivaldi.com/stable/deb stable Release.gpg
Reading package lists... Done
W: GPG error: http://repo.vivaldi.com/stable/deb stable Release: The following signatures couldn't be verified because the public key is n
ot available: NO_PUBKEY 8D04CE49EFB20B23
E: The repository 'http://repo.vivaldi.com/stable/deb stable Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Help please.

edwardp

I have seen this with both the .deb and .rpm installation packages.

I have filed a bug report on this: VB-105521.

lfisk

@alexisss0022 Guessing... should be "https:"

In theory you could just remove the signing key you installed (important!!), download the latest vivaldi manually and install/upgrade. It should install the correct signing keys during install via a daily cron job

themet4lgod

This issue is still happening on Ubuntu 24.04 (LTS). I just upgraded this evening. The signed-by field is missing from the file. Only Microsoft VS Code and Vivaldi are generating this warning with apt. Steam, OBS, PgAdmin 4, and UnityHub are all fine and have this information.

vivaldi.sources

Types: deb
URIs: https://repo.vivaldi.com/stable/deb/
Suites: stable
Components: main

All of the other valid apt sources are adding a gpg key to the keyring.

That said, I can still just download the update from Vivaldi directly and sudo dpkg -i <package name>.

It is also throwing an error/info message about i386 not being supported anymore:

Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://repo.vivaldi.com/stable/deb stable InRelease' doesn't support architecture 'i386'

edwardp

@themet4lgod said in NO_PUBKEY error:

It is also throwing an error/info message about i386 not being supported anymore:

Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://repo.vivaldi.com/stable/deb stable InRelease' doesn't support architecture 'i386'

Vivaldi discontinued support for 32-bit Linux some time ago.

themet4lgod

@edwardp said in NO_PUBKEY error:

@themet4lgod said in NO_PUBKEY error:

It is also throwing an error/info message about i386 not being supported anymore:

Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://repo.vivaldi.com/stable/deb stable InRelease' doesn't support architecture 'i386'

Vivaldi discontinued support for 32-bit Linux some time ago.

This was on 64-bit Linux so I'm not even sure why it said this.

At any rate, I installed the latest Vivaldi on Fedora 40 (decided to switch from Ubuntu 24.04) and didn't get that message.

edwardp

@themet4lgod What I noticed, was once I install Stable via the download from Vivaldi's web site, then use the distro's package installer (rpm/dpkg/zypper) to install Snapshot afterwards, I was then prompted to import a key for the Vivaldi repository. This may or may not be the same key referenced.

Good luck with Fedora. I'm also testing Rawhide (Fedora's development branch).