Bug 380986 - kscreenlocker text and icons (breeze) are not crisp when using KDE Plasma Scale Display unlike the rest of the interface
Summary: kscreenlocker text and icons (breeze) are not crisp when using KDE Plasma Sca...
Status: RESOLVED FIXED
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 390548 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-06-08 18:33 UTC by Alexis M.
Modified: 2022-11-04 20:33 UTC (History)
5 users (show)

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


Attachments
A screenshot showing the fuzzy text + icon (3.16 MB, image/png)
2017-06-08 18:33 UTC, Alexis M.
Details
kscreenlocker without scaling turned on (2.41 MB, image/jpeg)
2017-06-08 18:38 UTC, Alexis M.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexis M. 2017-06-08 18:33:18 UTC
Created attachment 105996 [details]
A screenshot showing the fuzzy text + icon

When using the KDE Plasma Scale Display setting the interface scales correctly and with crisp text and icons, but kscreenlocker icons and text get fuzzy.
kscreenlocker is fine when not using the Scale Display setting.

See screenshot.

KDE Plasma version 5.10.1
KDE Frameworks version 5.34.0
Qt version 5.9.0
Kernel: 4.11.3-1

Intel iGPU
3200x1800 display
Comment 1 Alexis M. 2017-06-08 18:38:40 UTC
Created attachment 105997 [details]
kscreenlocker without scaling turned on
Comment 2 Alexis M. 2017-06-08 18:40:09 UTC
BTW, the scaling factor I use is 1.5.
Again, the rest of KDE remains crisp while using this.
Comment 3 Patrick Silva 2017-12-27 17:04:45 UTC
I replaced my old monitor with a 23 inches 1080p monitor yesterday and now I'm affected by this issue, some elements in lock screen looks pixelated.
My monitor scale is 1.2

Arch Linux, Plasma 5.11.4.
Comment 4 Patrick Silva 2018-02-08 20:44:47 UTC
same bug in plasma 5.12.
Comment 5 Patrick Silva 2018-02-16 20:49:27 UTC
*** Bug 390548 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2022-11-04 20:33:10 UTC
This was fixed a few years ago!