Flickering all the time on Wayland
-
I updated to Plasma 6.0 and switched to Wayland.
In the search bar and on most sites characters appear with a delay, tabs and websites flicker when scrolling, sometimes the whole windows turns black for 0.5s. (This doesn't happen with other (electron/chromium) apps.)Can someone help me troubleshoot these issues?
Makes Vivaldi nearly unusable.system details:
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: i7-3770 CPU @ 3.40GHz
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 -
Most of it can't be seen on screenshots but 2 examples:
https://aronkvh.hu/vivaldibug2.webm
https://aronkvh.hu/vivaldibug1.webm -
running ''vivaldi --disable-gpu'' makes it better, doesn't completely disappear though
-
As explained in this post, Vivaldi does not officially support Wayland.
Plasma 6.0 was released only today and I'm sure there are issues yet to be worked out.
My advice is to use X11 with Vivaldi. Or, if you prefer Wayland, switch to a distro still using Plasma 5.27.
Vivaldi on Linux:
openSUSE Tumbleweed and Slowroll (Xfce 4.20)
Fedora 42 and Rawhide (Xfce 4.20)Android (10)
Vivaldi user since 2016. Thank you to all Vivaldi users.
-
I'm actually running Fedora Kinoite 40-PreRelease with KDE 6.0 on Wayland. I have no issue at all. It has been working like a charm!
-
In the past mostly a GSync/VSync NVidia panel setting caused such flicker.
-
Hi @voyager1sun, I got unexpectedly "upgraded" to Wayland today and also experienced massive flickering in Vivaldi. I finally found a fix based on some other Chromium based browser forum posts. If you 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, clicked the provided button to restart the browser, and thankfully it seems to have completely fixed it. It can be a challenge to get to the setting and click the button due to all the crazy flickering, but keep at it and hopefully it will work for you too. Life without Vivaldi is just too painful to contemplate!
-
@seanjseymour said in Flickering all the time on Wayland:
Hi @voyager1sun, I got unexpectedly "upgraded" to Wayland today and also experienced massive flickering in Vivaldi. I finally found a fix based on some other Chromium based browser forum posts. If you 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, clicked the provided button to restart the browser, and thankfully it seems to have completely fixed it. It can be a challenge to get to the setting and click the button due to all the crazy flickering, but keep at it and hopefully it will work for you too. Life without Vivaldi is just too painful to contemplate!
This worked for me. Thanks!!
-
@seanjseymour
Thanks for the feedback, it should be possible to set this in a terminal but I cant test it, no flickering.
vivaldi --ozone-platform-hint=auto
Maybe other user can try if they cant reach the flags because of the flickering.
One can enable the flag then in vivaldi://flags.Cheers, mib
-
@seanjseymour Thanks for the tip, I've tried that but for me it resulted in OpenGL being disabled in Figma, Penpot and similar apps that use hardware acceleration - so they are unusable with that setting for me.
-
There is an ongoing issue with Mesa that affects certain GPU's, the AMD Radeon HD-5450 in my other desktop, is one of them. I disabled Hardware Acceleration in the Vivaldi settings as a workaround. It was said Mesa 24.1 will fix this.
-
@edwardp said in Flickering all the time on Wayland:
Vivaldi does not officially support Wayland
The problem is not so much because of this, but because of the combination
@voyager1sun said in Flickering all the time on Wayland:
Wayland
NVIDIA -
@voyager1sun said in Flickering all the time on Wayland:
switched to Wayland
In KDE Neon, you can't run Plasma with X11?
-
@sedative29rus you can, but Wayland offers some advantages and is the main focus for Plasma developers going forward
-
You can try setting this -> vivaldi://flags/#ozone-platform-hint to wayland. It causes some, but also fixes some, issues.
-
Setting the flag as described above didn't help for me. In fact, it made Vivaldi start up on a blank window and then stall (I had to kill the process).
But starting it as follows from the command line did help:
vivaldi --enable-features=UseOzonePlatform --ozone-platform=waylandI am on Plasma 6 and using the nvidia driver.
-
@jogojapan , @voyager1sun for decades,
nvidia =
in terms of supporting Linuxthus => nvidia + Wayland = another disaster
But... they are finally doing something by supporting explicit GPU synchronization in their 555 drivers, which GNOME, KDE and mesa already support, so things should get better in the near future (no flickering).
-
@jogojapan That was my experience when I tried that flag, it opened up a blank window on Wayland. With the flag on Auto, Vivaldi launches fine, but I don't know which setting it is actually using, plus I'm not noticing any difference on-screen between Wayland and X11.
No issue with the flag on Default (uses X11).
-
I had the same problem with the latest zorin 17 which also uses wayland. If I switch ozone to anything other than default it will die and if I don't disable hardware acceleration at some point the browser will cause my laptop to freeze. I really hope the linux version of vivaldi starts getting some attention and this is dealt with because if I have to switch between changing my entire distro or my browser I know what I will do. And I suspect many others will. Which will be bad because I also suspect vivaldi appeals disprotionately more to linux users.
-
@sedative29rus Wayland is a more secure windowing system than X11. Unfortunately, X11 has greater support. Canocial may switch to using it in the future as the primary according to their help documents.
*