Minor update (4) for Vivaldi Desktop Browser 5.6
-
This update includes security fixes from the Chromium project and several crash fixes.
Click here to see the full blog post
-
@Ruarí Thank you!
-
2nd nice update
Is there a reason why on macOS force grabs focus multiple times during Vivaldi load? -
@chas4: new bug? If not have you logged this yet?
-
@Ruarí Not new, I think it had been mentioned in the past, not sure if it has already been logged (the force grabbing of focus prevents typing in a different app as Vivaldi steals focus a few times before the main app shows)
-
@Ruarí No, not a new issue at all. Vivaldi has always grabbed focus multiple times (at least twice) during startup on Mac for as long as I can remember.
The open/confirmed bug for this is VB-56637
-
Very violent graphics on this post @Ruari with picture of a hand-gun..
-
I'm not able to update it via Vivaldi's Debian repo. Receiving errors pertaining to the public key not being available:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.vivaldi.com/archive/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY (group of letters and numbers removed)
W: Failed to fetch https://repo.vivaldi.com/archive/deb/dists/stable/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY (same group of letters and numbers removed)
-
@edwardp: Did you configure the repo by hand? When did you last update?
Also can you not remove the "group of letter and numbers". I need to see that to help debug.
-
@Ruarí I run apt several times a day. This error started appearing earlier this afternoon (local U.S. time), presumably when the new version first appeared in the repo.
The repo was apparently configured automatically when the original .deb package was first installed.
No problems updating Vivaldi until today.
Could:
[Linux] Rotate keys in packaging and add 33EAAB8E key
have something to do with it?
EDIT: Removed installation of vivaldi-stable, downloaded new deb package. Package installed, but apt is still showing the same error as above when run.
Are there other files that need to be removed to fix this? The Vivaldi repo entry is not in /etc/apt/sources.list
-
@edwardp: Yes it is because you configured our apt repository by hand likely using our help page. I am tempted to remove those instructions on our help page to stop people doing that. It always causes issues. I only added that page because people asked for it but it is redundant and just causes people to have an issue every time we update the keys. I can have a look at tweaking the page to work better or explain the issue but to be honest I wish I had never put it up.
If you did not configure our repo manually, the first time you installed one of our packages it would do it for you and then it "just works". The help page does state this but nobody reads it and those who find the page think that they should hand configure this.
Anyway, run this to fix it for now.wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpg
(triple-click to select the entire line above)
-
@Ruarí
wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg –dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpggpg: WARNING: no command supplied. Trying to guess what you mean ... gpg: can't open '–dearmor' 0+0 records in 0+0 records out 0 bytes copied, 4.1311e-05 s, 0.0 kB/s
Same error whether it's done as root or via sudo.
-
@edwardp said:
The repo was apparently configured automatically when the original .deb package was first installed.
If that was true I would not expect this line "https://repo.vivaldi.com/archive/deb", I would expect it to say "https://repo.vivaldi.com/stable/deb" because that is what the package would configure. The fact that it says "archive" means it was likely configured by hand as that is what our help page suggests (unlike the package autoconfiguration).
You can confirm what the package would have tried to setup after install by looking at
grep '^REPOCONFIG' /opt/vivaldi/cron/vivaldi
You will note the '/stable/' rather that '/archive/'.
-
@edwardp: That is a double - but I suspect that the markdown to html on this page is being too clever. I will work around it, try this
wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpg
-
This post is deleted! -
sudo wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/usr/share/keyrings/vivaldi-browser.gpg 4+1 records in 4+1 records out 2285 bytes (2.3 kB, 2.2 KiB) copied, 0.130831 s, 17.5 kB/s
Running apt after this, is still giving me the same error previously mentioned.
The Vivaldi repo information is in /etc/apt/sources.list.d/ I just checked all three entries, vivaldi.list is showing stable, vivaldi-archive.list is showing archive and vivaldi-snapshot.list is showing snapshot. Should vivaldi-archive.list be removed??
-
@edwardp Did you run
apt update
before attempting to install/upgrade Vivaldi again?And yes you can kill vivaldi-archive.list as well if you like. The packages did not make that file.
-
@Ruarí Yes I did.
I removed vivaldi-archive.list and the aforementioned error did not appear afterwards.
I then removed both Stable and Snapshot via Synaptic (selecting to completely remove both, which will also remove any configuration files), then reinstalled the Stable .deb package again. The .deb package installed without error.
Ran apt update again, no errors displayed. Then installed vivaldi-snapshot via apt, no errors reported during installation.
Have since run apt update twice, no errors reported.
-
@edwardp Good news. Glad it is working for you and sorry for the trouble. I have removed the parts of help page that told people how to hand configure the repos. This is not the first time it has done more harm than good and people do not need to do that since the packages will setup everything anyway.
-
@Ruarí It's definitely best to let the package configure it automatically.
Thank you for the assistance.