Vivaldi browser and the packagekit

[eriefisher]

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.

[michaa7]

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.

[Pip]

@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

Code Select Expand

ls -l /usr/share/keyrings/vivaldi*

(if that isn't what you showed before), and a

Code Select Expand

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?

[michaa7]

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.

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

# 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

# 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

[Pip]

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.

[michaa7]

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

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.

Is this path cached somewhere?

And

Code Select Expand

# 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?

[der_bud]

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

[Pip]

Also, are you running as root? If not (which I almost never do), make it sudo gpg instead of just gpg.

[alexsid]

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.

[Pip]

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.

[unklarer]

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.

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

[michaa7]

Again: Why does whoever check "/etc/apt/trusted.gpg.d/vivaldi.gpg" which isn't configured anymore?

Code Select Expand

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.

[eriefisher]

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.

[michaa7]

solved (see above).

Thanks.

[eriefisher]

Good stuff!