Bug 436135 - Zoom is incorrect on display with enabled fractional scaling (on KDE).
Summary: Zoom is incorrect on display with enabled fractional scaling (on KDE).
Status: RESOLVED DUPLICATE of bug 436615
Alias: None
Product: kolourpaint
Classification: Applications
Component: general (show other bugs)
Version: 24.05.1
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: kolourpaint-support
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-24 17:19 UTC by Artem Kliminskyi
Modified: 2024-07-31 20:09 UTC (History)
1 user (show)

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

Attachments
Screenshots of KolourPaint. 100% zoom and 80% zoom. (113.61 KB, application/gzip)
2021-04-24 17:19 UTC, Artem Kliminskyi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Artem Kliminskyi 2021-04-24 17:19:37 UTC 
Created attachment 137876 [details]
Screenshots of KolourPaint. 100% zoom and 80% zoom.

SUMMARY
Main canvas on kde with fractional global scale. 100% canvas scale is not really pixel-perfect when global scale in display settings is 125%. It becomes pixel perfect only when you set 1/1.25=80% zoom.


STEPS TO REPRODUCE
1. System Settings -> Display and Monitor -> Display Configuration -> Global Scale to 125%.
2. Open KolourPaint and draw some random things with it.
3. Set 100% zoom and see that it is not pixel perfect.
4. Set 80% zoom and see that it is pixel perfect.

OBSERVED RESULT
In "STEPS TO REPRODUCE"

EXPECTED RESULT
Set 100% zoom and see that it is pixel perfect on any global scale.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro 20210412-1, KDE Plasma 5.21.4-1
(available in About System)
KDE Plasma Version: 5.21.4-1
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Comment 1 Evren 2024-06-18 12:28:24 UTC 
I can confirm the bug still persists

KolourPaint 24.05.1
ArchLinux 6.9.5
Plasma 6.0.5
Framework: 6.3.0
Qt: 6.7.1
Xorg on SDDM
Comment 2 Christoph Feck 2024-07-31 20:09:43 UTC 

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