Bug 496592

Summary: Icons in fingerprint configuration are misplaced
Product: [Applications] systemsettings Reporter: kostadinshishmanov
Component: kcm_usersAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate, uhhadd
Priority: NOR    
Version First Reported In: 6.2.3   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.3.0
Sentry Crash Report:
Attachments: image that appears when you have no fingerprint enrolled
image that appears after you enrol a fingerprint

Description kostadinshishmanov 2024-11-22 18:42:14 UTC
Created attachment 176046 [details]
image that appears when you have no fingerprint enrolled

SUMMARY
While trying to register a fingerprint, I noticed that the images that appear in the KCM (The one that appears when you have no fingerprint enrolled, and the other one after you successfully enrol a fingerprint) are misplaced.

STEPS TO REPRODUCE
1. Open System Settings and go to Users
2. If you have no fingerprint enrolled, the fingerprint image will be misplaced (attachment 1 [details]).
3. Start enrolling a fingerprint
4. When the process is finished, the image that appears is also misplaced (attachment 2 [details]).

OBSERVED RESULT

Images are misplaced.

EXPECTED RESULT

Images appear in the centre or wherever just so they are properly visible.

Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.3
Kernel Version: 6.11.9-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 5650U with Radeon Graphics
Memory: 14.4 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

Device is a Lenovo ThinkPad X13 Gen 2 AMD. Resolution used is 1920x1200 and scaling is set to 100%
Comment 1 kostadinshishmanov 2024-11-22 18:42:31 UTC
Created attachment 176047 [details]
image that appears after you enrol a fingerprint
Comment 2 Nate Graham 2024-11-25 20:42:05 UTC
This was fixed already for Plasma 6.3, also possibly in conjunction with changes in Frameworks 6.9 or later.