https://bugs.kde.org/show_bug.cgi?id=420859
--- Comment #15 from Matej Mrenica <matejm98m...@gmail.com> --- (In reply to Vlad Zahorodnii from comment #14) > @Matej What if you set the cursor size to 24 and reboot the computer? Also, > can you reproduce this issue with a scale factor of 1? With scale factor of 1 or 100% everything works correctly. I am testing this with KDE Neon live so I cannot reboot, I do re-login after every change though. The following findings are from KDE Neon but the previous experience was exactly the same as on Arch so I will also test this on Arch later. Someone mentioned there was an update (I am assuming a change in master) but the experience on Neon dev unstable + updates is the same. Setting a cursor size doesn't have any effect inside Qt apps - the size is always the same inside an app it is only changed over SSDs. For example: if I set it to 24 it is small over SSDs and huge and pixelated/corrupted inside the window. If I set the size to 36 it is bigger (than before) over SSDs and the same (huge) size inside apps. Setting it to 48 produces the same cursor size as "36" (?!) over SSDs and is again exactly the same (huge) inside apps as before. Over gtk apps, there are three different cursor sizes for all three size options (24, 36, 48), however they are all a little bit smaller than over SSDs and all three are pixelated/corrupted. I tested this with Firefox Wayland (not XWayland) and gtk3-demo. -- You are receiving this mail because: You are watching all bug changes.
