https://bugs.kde.org/show_bug.cgi?id=364218
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #10 from Thomas Lübking <thomas.luebk...@gmail.com> ---
It would seem that the cursor size is based upon the physical resolution
instead of the logical then.
The other bug (which I googled up ;-) has a similar constellation.
The internal screen has a physical resolution of 96dpi and that is set by the
server (the condition might stem from an Xorg config snippet in your case) but
the second screen has a resolution of ~131dpi and as soon as it's added, the
bigger cursor is used (wrt 72dpi being the base, 131 is 1.82 times larger, so
the big cursor should be used while 96dpi is only 1.33 times 72dpi)
Unfortunately I don't know who's in charge here - it's either Qt or the plasma
QPA.
I cannot even say whether this would be considered a bug given that the
physical resolution is used to determine an input event (*shrug*)
What is stunning though is your claim to work around it by altering the font
resolution, for this would actually rule out physical resolution trumping the
logical one.
*** This bug has been marked as a duplicate of bug 301622 ***
--
You are receiving this mail because:
You are watching all bug changes.
