The images in the first post look like what happens if you are using a bitmap font (available in specific sizes only) instead of a vector font (FreeType/TrueType). Since the system can't resize the bitmapped font, it displays it at full size but pretends it is the requested size, leading to overlapping text. Sometimes the only thing to do is remove the bitmap fonts from your system to force it to use the vector fonts.

Been some time since I've seen this error, but perhaps it's making a comeback. 😞

So to come to a conclusion, this bug happens with nvidia drivers 565.77 in a Wayland session and using chrome://flags/#ozone-platform-hint=wayland. Chromium is not affected. I think it should be reported.

Ha! Didn't find any related forum posts but didn't think to read the blog.
Thanks @lfisk that worked.

inconsequential update, after some time away...

vivaldi 7.0.3495.29(chromium130) works

chromium 132.0.6834.110 works

@caffeine81 Nice, some report issues when running V. as a Wayland app, some not, I am on the latter group. The best place to see details about the ozone platform is chrome://gpu, otherwise just for what flags/parameters you are using chrome://version.

Okay, I fixed the issue. I edited the .desktop file for Vivaldi and next to

Exec=/usr/bin/vivaldi-stable --password-store=kwallet5 %U

If the file is not in this location, then in the terminal you can use
locate vivaldi-stable.desktop (or vivaldi-snapshot) and it will output the location.

Thanks for the help guys!

I was able to find an open test Confluence, and was able to add comments.
I get this:
7384a49c-c6c8-43c6-bc3e-053bb5e9eb07-image.png

And get comments:
d10ed8bc-20cd-4712-90bc-14fb362fe8d3-image.png

As i know geolocation works by WiFi, Bluetooth and Internet Dialin Endpoint IP (in order of less accuracy).

@bovender Glad to helped you.

Resolved

It was a standard flatpak app configuration setting. In the filesystems= value in the Context section, it quite simply sets the permissions that it requires (as an application). (Like everything on fedora 41, these would be subject to SELinux, but in this case that wasn't an issue - I checked as part of my initial investigation).

I added the Documents folder in home, making sure I used the "xdg-documents" notation for it. That worked like a dream. I suspect that this file will be reset after each upgrade - I'll check on it.

In summary, it was a sensible flatpak setting/restriction, and in this case not an SELinux restriction. Here is the Context section, with my change being on the filesystems line.
File in question:

/var/lib/flatpak/app/com.vivaldi.Vivaldi/current/active/metadata [Application] name=com.vivaldi.Vivaldi runtime=org.freedesktop.Platform/x86_64/23.08 sdk=org.freedesktop.Sdk/x86_64/23.08 base=app/org.chromium.Chromium.BaseApp/x86_64/23.08 command=vivaldi required-flatpak=1.8.2 [Context] shared=network;ipc; sockets=x11;wayland;pulseaudio;pcsc;cups; devices=all; filesystems=~/.config/kioslaverc;~/.local/share/applications:create;/run/.heim_org.h5l.kcm-socket;~/.config/dconf:ro;xdg-download;xdg-run/dconf;xdg-pictures/Vivaldi Captures:create;xdg-desktop;xdg-documents;~/.local/share/icons:create;xdg-run/pipewire-0; persistent=.pki;

I'm not aware of a way to do this via the in-app settings; happy to be corrected.

Scrap that
There is a standard way to modify the application permissions of flatpak installs, via the package manager. A button called "Configure Permissions ..." It's listed there.

I'm guessing it ends up changing the same file, but it also is persistent across application updates.
The changes end up living here, which is why they remain persistent:

/home/nigel/.local/share/flatpak/overrides/com.vivaldi.Vivaldi

Screenshot_20250108_232404.png
(Hope this helps anyone who runs into the same issue/knowledge-gap!)

Hi @Pathduck and @annerelbe

Both are used for sync notifications. We saw that differing operating systems are not able to use the same protocols in our first implementation of sync notifications.

To fix this we use two ports at the moment and it depends on your OS and Vivaldi version which one you use. (Both might be pinged in some versions) One of those ports will be phased out when we have aligned all the different OS's to use the same protocol.

I believe 8080 will be phased out as soon as we are confident that all OS's versions are working as intended using port 61613 for notifications.

This is seamless for our users but as you see, we have two ports there, but they only communicate with the sync notifications servers.

@Andy_teacher Any error ins shell when starting Vivaldi?
Check each:

vivaldi & vivaldi --disable-extensions &

New snapshot, new system updates, et voilà, video decoding is accelerated again:
bb2792df-8d76-4466-b7c1-774c736343cf-image.png

Command Line:

/usr/bin/vivaldi-snapshot --enable-features=UseOzonPlatform,WebRTCPipeWireCapturer,AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoEncoder,WaylandPerSurfaceScale,WaylandTextInputV3 --disable-features=WebRtcAllowInputVolumeAdjustment --flag-switches-begin --ozone-platform-hint=wayland --ozone-platform=wayland --flag-switches-end --flag-switches-begin --flag-switches-end

@cobordism I hope, you find a user who has more fun to investigate differences of browser data of snap and deb version.

I ignore Vivaldi snap version and use deb package for the Debian-related distries.

@luetage in my case I need to be on Wayland otherwise it's annoyingly fuzzy with fractional scaling on gnome. And also smooth pinch to zoom with touchpad only seems to work with Wayland. I know this is a post full of workarounds, but it makes the whole experience more pleasant for me!

I have both the ad-blocker and tracker-blocker on and the full login screen with logo, comes up for me.