@DoctorG Looks like it was an issue on Twitch's side. Was able to login today even with "Vivaldi" header. 👍

@barbudo2005
Thanks. That CSS method works!

Thank you for the comprehensive update.

😀 😂

Mail client has been and is great. Recently however, after a manual clean-up of cache, I started getting following inconvenience. I have a separate, portable instance of Vivaldi, specifically dedicated to email, since I use 6 separate email accounts and and keep all my email history locally in the client. Of those email accounts, 3 require Oauth authentication and the other 3 have standard way of authentication. So the problem I experience lately can be described so. The first time I open Vivaldi in the morning, I see a brief message, from the default account, that I am connected. However moments later the default, same as the rest of accounts appear to go offline and get a red circle. They all don't react and are unable to receive or send mails in this state. The solution I found, was to go into mail settings, click on the "Server" tab and wait for each account to show "Verified". Than I close Vivaldi and reopen it and it begins to function properly (receiving and sending emails). Subsequently I can keep opening and closing Vivaldi in the day and it will work correctly. However in the following morning the problem returns a new. About a month ago, when I set up those 6 accounts, Vivaldi was working without a glitch. I don't know if I, by cleaning cache, triggered some sort of a bug. Please help. The error on the red dot states: "Socket timed out!". Now it also started to give this error every time I reopen Vivaldi for mail.

Nice owl, thanks

Waiting for Arch repo sync

@iPristy Thanks for report.

@chimer-rokovoy You should give a big Thanks to @Adam1331, he contacted the author of the blocklist: see https://forum.vivaldi.net/post/770421

Since the "memory saver" update, every now and then (honestly pretty often) restoring hibernated tabs just goes into an endless loop where Vivaldi consumes one full core 100% and never ever stops, the tab of course does not load. Closing the tab usually stops the cpu usage (but then reopening it does not always load it properly..). Also what I've noticed is that often tabs from the same site crash in various ways when that happens (so likely something related to one process/site thing + restoring from hibernation).
I don't use memory saver, but I do use lazy load on start.

Am I really the only one encountering this? I'm talking about STABLE Vivaldi on Win (however this happens in snapshots too, I have both Vivaldis on this desktop and both have that issue).

I'm not really willing to clear my profile over and over again, because frankly a lot of updates break things (I still can't use the Vivaldi button menu, because it just isn't there, and the option centers my tabs in the tabbar in some weird way; this was introduced in "revamped menus" STABLE update and never fixed) and for a browser that boasts high customizability (true) not even being able to transfer settings (no, sync wont do that) is a, uh. Plus, it's not just settings but also site data that I'd lose.

"That's great news! The addition of Memory Saver and the auto-detection of feeds with the Feed Reader will significantly enhance the user experience. Memory Saver will help in optimizing system resources, making Vivaldi run smoother, especially on systems with limited memory. The auto-detect feature for feeds is a fantastic addition for those of us who rely on Vivaldi's Feed Reader for staying updated with our favorite content. Kudos to the Vivaldi team for these useful enhancements!"

@slavau: I can confirm, unable to print. I get "Print preview failed" in the dialog, can't switch printer drivers, all grayed out. The only option is "Cancel" button. Installed and portable setups. Printing is broken in everything for me. On Windows that is, latest updates. No antivirus installed, all extensions disabled, as stated both installed and portable setup. Any other browser (Firefox, Waterfox, Chrome, ungoogled chromium, Edge, Arc), all of them print just fine. Vivaldi at fault.
And after some testing, running with "--disable-features=PrintCompositorLPAC" solves the problem.

@rseiler I messed up the recipe. If I open a New Private Window from the Private Window where I logged in, then I am still logged in. However, if I close the Private Window, and open a New Private Window from the original window, then I am not logged in.

@Ruarí
Thank you once again for your tireless efforts, even on public holidays and weekends, to ensure Vivaldi's safety.

😂 😀 🥳

@yngve
Thank you for your contribution too.

I always enjoy reading you.

😀

Looks like there will be another minor update soon

source: https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_21.html

"The Stable channel has been updated to 125.0.6422.76/.77 for Windows, Mac and 125.0.6422.76 for Linux
...
This update includes 6 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$11000][336012573] High CVE-2024-5157: Use after free in Scheduling. Reported by Looben Yang on 2024-04-21
[$10000][338908243] High CVE-2024-5158: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-05-06
[$5000][335613092] High CVE-2024-5159: Heap buffer overflow in ANGLE. Reported by David Sievers (@loknop) on 2024-04-18
[TBD][338161969] High CVE-2024-5160: Heap buffer overflow in Dawn. Reported by wgslfuzz on 2024-05-01
"

Thanks in advance for you hard work, team!

@izero To add to what @DoctorG suggested, if you want those issues fixed, you should file descriptive bugs about the problems, and crashdumps for the crash issues.

I found no bugs filed by you about those issues you mention, and the only one filed with your email address was for an issue that was also present in Google Chrome, so it have to be fixed by them.

I'll also note that you should run your tests in clean, standalone installs, If that environment works, then you can start gradually introducing other changes you have made to your main environment, so that you can figure out which broke the browser.

@ThirdGenerationAI
Hm, the screen cast is from Windows 11.
As many issues in Vivaldi cause by extensions this could be the reason.
The best way to test this is to block loading them with editing your Vivaldi desktop shortcut.
Add --disable-extensions to it.

desktop_shortcut.png

If this not change anything I would create a new profile for testing.

Profiles

Actually, it should be since the second 6.7 minor update

We do not hide whether an update has security fixes 🙂
In fact, we are quite open about it:

"Aside from bug fixes, almost every release will contain security fixes, security enhancements, new security protections or something related to security, either directly from us, or as part of the Chromium updates. They often also include stability fixes (for crashers). Skipping updates is almost never a good idea. They are all important, or we wouldn't be releasing them. This is pretty standard for security oriented software products like browsers, and the same would apply to any other browser."

The main reason we don't list security fixes for Chromium is that we do not run the Chromium project. The Chromium project announces their security fixes, and we inherit them, as with all products that use an open source package. We often add security patches ahead of time too, even if we are using an older release of Chromium, but most of time, the people making our changelogs don't actually check exactly how many security fixes are in Chromium, and which of them we already patched by the development team in previous updates. They just say "it got a Chromium update", and you can assume that every Chromium update is important in some way, whether it is new functionality, new website compatibility changes, security enhancements or security fixes.

We already tell you to update, and the browser tells you to update. We are working on a way to remind you if you have fallen behind on updates.