Hello everyone!
For the past few days, Chromium-based browsers (Chrome, Brave) have been displaying an enormous cursor with Wayland and scaling greater than 100%. No issues in the sandbox versions (flatpak, snap). I suspect the problem started with Chromium version 135. For now, I've worked around the issue by reinstalling Chrome 134.0.6998.165.
The problem has been verified on two up-to-date installations of ZORIN 17.3.
Hmm ... my System runs in Wayland and my Scaling is set up to 200%. I have Brave installed (.deb Version) and the Cursor has the normal Size.
Do You have Fractional Scaling active? And what Graphics Card do You have? And when You switch to Xorg does it change?
Yes, I'm referring to fractional scaling with Wayland. On my laptop, I have an AMD GPU, and on my desktop, I have an NVIDIA RTX 3050 GPU.
On my desktop, I'm using X11 at 125% scaling with no issues, but when I switched to Wayland at 125% to check for the bug, the problem occurs just like on my laptop.
Ah, okay. Here coming several Things together. The Wayland Implementation in Gnome 43 (the Base for the Zorin Desktop) isn't on a too good Level. So, this can cause Issues. To this comes the Situation that You use an Nvidia Card. On up-to-date Desktops, You can have a good Wayland Experience because of Progress in the DE's and the Nvidia Drivers.
But here on Zorin, You don't have this Benefits yet. When You are on Zorin 17, it would be better to stay on Xorg when You have a Nvidia Card. Because of Your AMD Card: What is it for a Card?
I have two PCs running Zorin OS 17.3. The first is a laptop with an AMD GPU, and the second is a desktop PC with an NVIDIA GPU. I can reproduce the problem on both, and it is recent (less than 8 days).
I found this in relation :
https://www.reddit.com/r/chrome/comments/1jphlw8/chrome_135_new_look_on_wayland/?rdt=37348
It's true that I have also noticed this problem with the @
Hmm ... I guess then it could be an Issue with the Browser. But when You switch to Xorg it works on both Machines, yes? Then You should do this temporarly until it is fixed.
There was another thread reporting the same issue, I guess this one just confirms it's an issue with upstream Chromium. We'll have to wait on a fix for it...
Yes, it works correctly with X11. Now we just need to wait for a Chromium fix.
Yes, I guess that is neccessary.
Issue fixed in the latest stable versions of Chrome and Brave.
However, @ special character trouble remains.
Thanks, it works!
