@ogredale Ze magicks of ze interwebs. Sometime it work sometime it don't.

I think it's the curse of your sad face avatar... 🤪

@Aviyr
Hi, the help about page shows only the main version, Vivaldi 6.6.3271.48 is Chrome 122.0.6261.116.
You cant change the Chromium version, only the Vivaldi developer can.
If you like you can show the exact version in the status bar.
Open the Vivaldi Settings and type "biscuit" in the search field.
A hidden setting appear:

e33342f7-07c4-47dd-be32-ebd08acbd336-image.png

The bug tracker form track your Vivaldi and some system informations automatically.
Please report this, it should work.

Cheers, mib

Just read the solution. I don't know if it's the proper way, but no more flickering for me in Wayland.

https://forum.vivaldi.net/topic/95521/flickering-all-the-time-on-wayland/13 -> @seanjseymour mentions: "Enter vivaldi://flags into the address bar, then search for Ozone, you will see a "Preferred Ozone platform" setting. I changed it from Default to Auto,"
I changed it to "Wayland" , it was set to "Default" already for me... ... It works now.

Would you mind sharing a screenshot how Vivaldi looks on KDE?

A bigger problem for me with the permissions we currently have on flathub is that we cannot currently make use of ptrace which our crashlogger uses. Thus no valid crashlog can be produced by flatpak'd Vivaldi in it's default configuration. As a user you could fix this with flatseal or if the crash was reproducible you run it with the following command in a terminal before causing the crash: flatpak run --allow=devel com.vivaldi.Vivaldi

We have a bunch of other small flatpak/flathub specific issues as well, such as when you come to Vivaldi from another browser we cannot detect the other browsers on the system to help you import things like bookmarks, or that Vivaldi cannot set itself as the default browser from within our UI (we can only give you text explainations on how to do it manually). And so on…

This is part of why the flatpak is still not official (despite it being maintained by an employee [me]). Certain things are a indeed a worse experience. However on the flip side it is a trade off many users might want to make for things like additional protection or a more "universal install".

I finally found a workaround.

Run flatpak permissions desktop-used-apps | grep Vivaldi and check that the wrong app is in the "Permissions" column. It should be something like this: Table Object App Permissions Data desktop-used-apps application/pgp-keys com.vivaldi.Vivaldi org.kde.kwrite,1,3 0x00 desktop-used-apps x-scheme-handler/zoommtg com.vivaldi.Vivaldi org.kde.ark,1,3 0x00

In this case, I am interested in the second row. The "Object" contains the mime-type of interest.

Run flatpak permission-remove desktop-used-apps x-scheme-handler/zoommtg, replacing x-scheme-handler/zoommtg with your custom mime type.

Done!

P.S. It's a shame that Vivaldi doesn't provide a menu ala Firefox for resetting such file associations, though...