Solved Broken text on tabs
-
@zesko The browser UI is created by HTML, CSS and JS, comparable to a webpage.
-
@doctorg I see, that is why ...
-
@zesko said in Bad reading inactive tabs in Gnome 42 Wayland:
I disabled --enable-gpu-rasterization in the flags
Just being curious: you had enabled the flag before on your own for optimisation or perhaps it was set by Chromium core's GPU detection?
-
It was enabled by default after installation of Vivaldi. Like Chromium.
I checked any websites with 3D simulation, I do not notice any issue.
-
Good evening,
I do the exact same issue. I tought first the problem came from my laptop as I updated it to Ubuntu 22.04 - so I did what I wanted to do for a long time and switch to Fedora.
But the problem is still there, and that's pretty annoying.
Im not as advanced as you all and I'm not sure to have understood : waiting for a fixing update is the only thing we can do ?
Thanks
-
See attached screen shot. The tab looks like it's duplicating the text over top of itself and makes it illegible.
If I hover over a tab with this problem the text is temporarily fixed.
It also does not happen on an active tab. -
@exist2resist Seems all fine here [but i'm only using a VM, not on-metal].
Suggestions:
- can you verify in a clean test profile [eg, via
vivaldi-stable --profile-directory="NewTestProfile"
in terminal]? - Fedora WS session default is Wayland; have you retested in X11?
- still in Wayland, try launching your V as a full-W app, not its default Xwayland app mode, by
vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
? - try launching your V from terminal with either of these switches appended:
--disable-gpu
or--disable-gpu-compositing
?
- can you verify in a clean test profile [eg, via
-
Have exact same problem on latest Manjaro with 5.2. Somehow it fixes itself for a few minutes depending on mouse focus, new tabs created / existing tabs closed.
-
@guigirl I'm on X11, and neither of profile / gpu / gpu comp suggestions fixed anything.
-
Reverting to 5.1 fixes the issue.
-
Aha, a clue!
maltazar1
·
16 hr. ago
You can fix it by disabling gpu rasterization in flags temporarily
1
User avatar
level 2
givbra
Op ·
7 hr. ago
disabling gpu rasterization in flags
Thank you. I confirm that disabling GPU rasterization fixes the issue for now ...
vivaldi://flags
GPU rasterization -> Disabled -
This post is deleted! -
@vaygr Downgrade is not advised by Vivaldi, such will crap browser data and cause strange effects.
-
@DoctorG said in Tab text issue in Vivaldi 5.2 on Fedora 36 and Gnome 42:
supposed
supported, i presume?
-
@guigirl Thanks for hint. Sorry, i meant "advised", i fixed this in posting.
-
Same problem! Screen was made with default user profile, on others same bug. Its was happens after update ubuntu to 22.04.
hardinfo report
-
Same issue here, Arch with Gnome on Wayland with Iris Xe graphics.
It worked perfectly before 5.2.
-
@guigirl said in Broken text on tabs:
@exist2resist Seems all fine here [but i'm only using a VM, not on-metal].
Suggestions:
- can you verify in a clean test profile [eg, via
vivaldi-stable --profile-directory="NewTestProfile"
in terminal]? - Fedora WS session default is Wayland; have you retested in X11?
- still in Wayland, try launching your V as a full-W app, not its default Xwayland app mode, by
vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
? - try launching your V from terminal with either of these switches appended:
--disable-gpu
or--disable-gpu-compositing
?
I do not use Wayland, my default is xorg.
Your suggestions did not help anything still getting the same issue.
Was fine on Fedora 35 prior to upgrading.Thanks
- can you verify in a clean test profile [eg, via
-
You are all using Intel Xe Graphics and you have all moved to a newer kernel, newer mesa version etc. Newer is not always better.
you can do one of the following:
- try with an older kernel
- try with Vulkan instead of GL (assuming you have everything vulkan necessary)
$ vivaldi-stable --use-vulkan --enable-features=Vulkan
- try disabling hardware acceleration or parts as instructed
- try living with a basic Vivaldi (without its UI) with
$ vivaldi-stable --disable-vivaldi
- try Vivaldi Snapshot (5.3) to see if it is also affected
- report the bug to the bugtracker
- wait for 5.3 hoping/in case it is not affected
- use another browser which is not affected
-
@npro said in Broken text on tabs:
You are all using Intel Xe Graphics and you have all moved to a newer kernel, newer mesa version etc. Newer is not always better.
you can do one of the following:
- try with an older kernel
- try with Vulkan instead of GL (assuming you have everything vulkan necessary)
$ vivaldi-stable --use-vulkan --enable-features=Vulkan
- try disabling hardware acceleration or parts as instructed
- try living with a basic Vivaldi (without its UI) with
$ vivaldi-stable --disable-vivaldi
- try Vivaldi Snapshot (5.3) to see if it is also affected
- report the bug to the bugtracker
- wait for 5.3 hoping/in case it is not affected
- use another browser which is not affected
There is no world where I run a modern browser without hardware acceleration, so that is not an option.
Do you have a link to 5.3 snapshot for rpm package?