NO_PUBKEY error

DoctorG

@lfisk Nice find.
Yes, i saw this old blog post about older help page advice, too, minutes ago.

lfisk

@DoctorG I'd been working around the problem for several seasons. While following this discussion last year I finally understood the problem and then it was easy to fix it

michaa7

I don't remember, but I think it was, as far as I remember, someone here in this forum who gave or pointed me to this script when I complaint about settings being overwritten on vivaldis update.

@ lfisk
Ok, here comes light into the dark

My only concern is, I created my-vivaldi.list due to a problem and not for self-expression and I do not want to solve a problem by recreating an old-one. I have to dive back to find what the exact problem was and see how it might be solvable today. Or are you actually speaking about it?

EDIT:
I immediatly gave up searching as there is no search. I cannot understand how someone sees fit to simply copy the content of all postings and not providing a list of posting titels. This "eigene Beiträge" is high gloss sh** (or garbage if you like diplomacy). I is an usless because unsearchable archive. (for anyone interested how to create ergonomicaly searchable info go to debianforum.de; you can search in consecutive levels within what you found and restrict itto a search within your own postings ).

Now for the current problem. How do I solve it. Is there a way to solve it correcting the shell command?

lfisk

@michaa7 I like Snypatic because you can visualize confusing things. So look carefully at the Vivaldi repo and make sure it reads exactly the same. There was one word different in my old troublesome entry that was causing the problem.

Screenshot from 2024-02-01 11-22-26.png

lfisk

@lfisk So I removed the bad entry, nothing for Vivaldi. When you make the next install Vivaldi has a built in script that adds the proper Repo Entries and Keys. It runs as Cron job. Likely it is already installed and will fix this when the Cron runs again. I think it's a Daily one...

DoctorG

The current help page Manual setup of the Vivaldi Linux repositories
It says: no need for fiddling with GPG keys and manual created package manager repo configs.

edwardp

The error will clear once the Vivaldi repository is added to your installation, there will be a standard prompt to accept/reject the key.

lfisk

@edwardp I never received any "accept/reject the key" but this runs as a Cron job, so it has Root privileges. You can find the Daily script here on Deb 12 for the current Vivaldi installation if you want to better understand how it works:

/opt/vivaldi/cron/vivaldi

michaa7

We are talking past each other.

I did NOT create my-vivaldy.list due to pub-key problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I created it because of some other problem which I really liked to reinvestigate but now can't chase down because the vivald forum archive is UNsearchable ill-considered USELESS high gloss SH!T.

Yes, I understand that deleting my-vivald.list and reenabling vivaldi.list(.save) would possibly solve the pub-key problem. But it most certaily would recreate the see-above-original-problem.

@lfisk
The wording was correct, except for a trailing "/" which doesn't change the outcome.

michaa7

@DoctorG said in NO_PUBKEY error:
...

The best way is to delete the packages.vivaldi.gpgkeyring,
remove the vivaldi stable with
sudo apt purge vivaldi-stable
fetch installer deb package
wget https://downloads.vivaldi.com/stable/vivaldi-stable_6.5.3206.59-1_amd64.deb
and install with
sudo dpkg -i vivaldi-stable_6.5.3206.59-1_amd64.deb
and in case of errors
sudo apt -f install

does NOT solve the problem although vivaldi.list was created.

did the pubkey change recently? Because my vivaldi setting worked for month and years. so why a problem today?

DoctorG

@michaa7 Since 2024-01-24 ;
For 6.6.3250.4

[Linux] Rotate keys in packaging and add 74C35BC8 [KEY10]
— https://vivaldi.com/blog/desktop/small-chromium-bump-vivaldi-browser-snapshot-3250-4/

And 6.5 Stable

[Linux] Update the Linux packages and repositories to use 33EAAB8E [KEY09]
[Linux] Rotate keys in packaging and add 74C35BC8 [KEY10]
— https://vivaldi.com/blog/desktop/minor-update-six-6-5/

michaa7

@DoctorG

Ich habe beide Vivaldis geupdatet zu der genannten Version:

# apt policy vivaldi-stable
vivaldi-stable:
  Installiert:           6.5.3206.59-1

# apt policy vivaldi-snapshot
vivaldi-snapshot:
  Installiert:           6.6.3256.4-1

Meine keylist sieht so aus:

# apt-key list | grep -A 5 "/etc/apt/trusted.gpg.d/vivald"
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
/etc/apt/trusted.gpg.d/vivaldi-33EAAB8E.gpg
-------------------------------------------
pub   rsa4096 2023-01-10 [SC] [verfällt: 2025-02-28]
      3360 18F2 63FA 0000 65CE  D7C6 124F 1498 33EA AB8E
uid        [ unbekannt ] Vivaldi Package Composer KEY09 <[email protected]>
sub   rsa4096 2023-01-10 [E] [verfällt: 2025-02-28]
--
/etc/apt/trusted.gpg.d/vivaldi-74C35BC8.gpg
-------------------------------------------
pub   rsa4096 2024-01-23 [SC] [verfällt: 2026-02-11]
      C2A2 445B 0EC3 B396 BD52  6E31 F739 AAC0 74C3 5BC8
uid        [ unbekannt ] Vivaldi Package Composer KEY10 <[email protected]>
sub   rsa4096 2024-01-23 [E] [verfällt: 2026-02-11]
--
/etc/apt/trusted.gpg.d/vivaldi-C27AA466.gpg
-------------------------------------------
pub   rsa4096 2021-01-06 [SC] [verfallen: 2023-02-25]
      CB63 144F 1BA3 1BC3 9E27  79A8 FEB6 023D C27A A466
uid        [ verfallen ] Vivaldi Package Composer KEY07 <[email protected]>


/etc/apt/trusted.gpg.d/vivaldi-snapshot-33EAAB8E.gpg
----------------------------------------------------
pub   rsa4096 2023-01-10 [SC] [verfällt: 2025-02-28]
      3360 18F2 63FA 0000 65CE  D7C6 124F 1498 33EA AB8E
uid        [ unbekannt ] Vivaldi Package Composer KEY09 <[email protected]>
sub   rsa4096 2023-01-10 [E] [verfällt: 2025-02-28]
--
/etc/apt/trusted.gpg.d/vivaldi-snapshot-4218647E.gpg
----------------------------------------------------
pub   rsa4096 2022-01-31 [SC] [verfallen: 2024-01-31]
      DF44 CF0E 1930 9195 C106  9AFE 6299 3C72 4218 647E
uid        [ verfallen ] Vivaldi Package Composer KEY08 <[email protected]>

/etc/apt/trusted.gpg.d/vivaldi-snapshot-74C35BC8.gpg
----------------------------------------------------
pub   rsa4096 2024-01-23 [SC] [verfällt: 2026-02-11]
      C2A2 445B 0EC3 B396 BD52  6E31 F739 AAC0 74C3 5BC8
uid        [ unbekannt ] Vivaldi Package Composer KEY10 <[email protected]>
sub   rsa4096 2024-01-23 [E] [verfällt: 2026-02-11]
--
/etc/apt/trusted.gpg.d/vivaldi-snapshot-C27AA466.gpg
----------------------------------------------------
pub   rsa4096 2021-01-06 [SC] [verfallen: 2023-02-25]
      CB63 144F 1BA3 1BC3 9E27  79A8 FEB6 023D C27A A466
uid        [ verfallen ] Vivaldi Package Composer KEY07 <[email protected]>

Nach wie vor Fehler:

Fehl:9 https://repo.vivaldi.com/archive/deb stable Release.gpg
  Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 124F149833EAAB8E

becm

@michaa7 the last GPG key KEY08 expired (2024-01-30 I think).
If there is any repo with a signed-by entry pointing to a keyfile that does not contain the expected key, this will lead to an apt (repo update) error.

In your (current) case, the latest package should now be available due to alternative sources.list lines, so (for now) this should be purely cosmetic.

Solution: find the remaining setting(s) with signed-by and remove (or update) this part of the repo source config.

DoctorG

@michaa7 said in NO_PUBKEY error:

Fehl:9 https://repo.vivaldi.com/archive/deb stable Release.gpg

This shows that may you have a sources list with a wrong repo.

Just search it
grep -niR "vivaldi.com/archive" /etc/apt/

My correct lines are
/etc/apt/sources.list.d/vivaldi-snapshot.list:
deb [arch=amd64] https://repo.vivaldi.com/snapshot/deb/ stable main

/etc/apt/sources.list.d/vivaldi.list:
deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main

qazerr

Had the same issue with "signed-by=".
For some reason vivaldi does not use "signed-by=" in vivaldi.list which is a small but still a potential security issue, so i added this setting by myself.
Would be nice if vivaldi would start to use "signed-by=". Thanks.

DoctorG

@qazerr I do not see any packages whose ...list have such entry.
On which OS is this?

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/