Bug 434402 - "Change password" button renders wrong when using display scaling
Summary: "Change password" button renders wrong when using display scaling
Status: RESOLVED DUPLICATE of bug 414266
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_users (show other bugs)
Version: 5.21.2
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Janet Blackquill
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-14 16:28 UTC by Massimiliano L
Modified: 2021-03-15 23:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of the button (9.94 KB, image/png)
2021-03-14 16:28 UTC, Massimiliano L
Details
Screenshot (3.28 KB, image/png)
2021-03-15 00:10 UTC, Justin Zobel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Massimiliano L 2021-03-14 16:28:11 UTC
Created attachment 136671 [details]
Screenshot of the button

SUMMARY

STEPS TO REPRODUCE
1. set "Global Scale" to 125% in display settings
2. open "Users" module of System Settings

OBSERVED RESULT
The "change password" button has a weird rendering (see attached file).

EXPECTED RESULT
The "change password" button should render smoothly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33 w/Zawertun KDE repository
(available in About System)
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Using XOrg.
Comment 1 Justin Zobel 2021-03-15 00:10:35 UTC
Created attachment 136681 [details]
Screenshot

I'm unable to replicate this issue. I've just set 125% scaling, rebooted and my Change Password looks as expected.
Comment 2 Massimiliano L 2021-03-15 07:29:49 UTC
(In reply to Justin Zobel from comment #1)
> Created attachment 136681 [details]
> Screenshot
> 
> I'm unable to replicate this issue. I've just set 125% scaling, rebooted and
> my Change Password looks as expected.

Thank you for the feedback Justin. I will try to replicate this in a VM.
Comment 3 Nate Graham 2021-03-15 23:12:00 UTC
Ah yes, this. :(

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