Solved Broken text on tabs
-
@doctorg Unfortunately I doubt this will fix the issue, as I downgraded chromium to version 100.0.4896.88-2 (I couldn't find the specific version you mentioned in the arch linux archive) and it still doesn't exhibit any issue, even with hardware accelerated rasterization enabled. I guess I'll live without that feature in vivaldi for now ! Not like I really notice a difference (:
-
@amazingkitchen Perhaps Chromium 100.0.4896.127?
-
@doctorg Works fine as well, unfortunately!
-
@amazingkitchen Perhaps only Vivaldi with 100.0.4896.133 core had such trouble. I do not know as we have no confirmed issue in bug tracker.
-
@doctorg I did find a difference between vivaldi://gpu and chrome://gpu, chromium seems to correctly identify my integrated graphics while vivaldi doesn't for some reason. Under DAWN Info I see:
In chrome:
<Integrated GPU> Vulkan backend - Intel(R) Xe Graphics (TGL GT2)
In Vivaldi:
<CPU> Vulkan backend - SwiftShader Device (Subzero)
I'm not sure what causes this, I'm going to investigate a little tomorrow and report back!
-
Just for information. The "Intel GPU issue" in chromium 101 is not fully fixed for me. Here a Screenshot:
Now the sourcecode is readable, but the buttons are still broken. In version 100 the sourcecode is unreadable, too.
-
Hi everyone,
If multiple tabs are on the browser in Gnome 42 Wayland, you can not read writing on the inactive tabs.
If you grab any tab with the mouse without clicking, then the tab is good to read.
When I change the tab bar to any position e.g. left or right or bottom:
Enable "Use native window" in the setting does not help.
Vivaldi: 5.2.2623.41 (Stable channel) stable (64-bit)
OS: Manjaro Gnome 42.1, Wayland.But KDE X11 has no issue with that.
-
@zesko Trouble with hardware accel or Vivaldi GPU driver incompatibility.
I do not know if some drivers GSync/VSync setting can help.But some users helped this:
Settings → Webpages → Disable Use of Hardware Acceleration → Restart -
-
@zesko Yes, some Intel GPU drivers do not work nice with Wayland & Vivaldi - known.
-
X11 has the same issue in my testing, Wayland is not alone.
Probably Intel GPU driver and Vivaldi don't work well together.
-
@zesko Seems trouble with some Intel GPU drivers.
I have some Intel GPUs on my office PCs (i5-7500 , e3-1200 ) which do not have such issue. -
If I disabled
--enable-gpu-rasterization
in the flags, any tabs are good to read.But its description is "Use GPU to rasterize web content."
Why is the tab as a website itself?
My expectation is that the tab should be independent of website. -
@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