Bug 465306 - wps cursor is scaled wrongly when "applying scaling themselves"
Summary: wps cursor is scaled wrongly when "applying scaling themselves"
Status: RESOLVED DUPLICATE of bug 467061
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.26.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-05 07:31 UTC by rosswzyang
Modified: 2023-03-16 22:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Reproduce video (1.92 MB, video/x-matroska)
2023-02-05 07:31 UTC, rosswzyang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rosswzyang 2023-02-05 07:31:14 UTC
Created attachment 155951 [details]
Reproduce video

SUMMARY
wps cursor is scaled wrongly when "applying scaling themselves", specifically cursor is scaled wrongly when the cursor is rendered by wps itself.


STEPS TO REPRODUCE
1. install wps(an office application)
2. enable fractional scaling
3. open wps spreadsheets, move cursor to the cell and to the top menu area

OBSERVED RESULT
cursor is scaled wrongly when the cursor is rendered by wps itself.

EXPECTED RESULT
cursor is scaled correctly when the cursor is rendered by wps itself.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230202
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11320H @ 3.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: TIMI
Product Name: A18R

ADDITIONAL INFORMATION
Comment 1 Vlad Zahorodnii 2023-02-06 09:34:27 UTC
Does it look fine in Xorg session?
Comment 2 rosswzyang 2023-02-20 11:27:53 UTC
(In reply to Vlad Zahorodnii from comment #1)
> Does it look fine in Xorg session?

yes
Comment 3 David Edmundson 2023-03-16 22:03:20 UTC
The cursor

*** This bug has been marked as a duplicate of bug 467061 ***