Bug 443677

Summary: "Titlebar buttons" tab of the "Window decorations" KCM shows buttons out of bounds
Product: [Applications] systemsettings Reporter: Andrei Rybak <rybak.a.v>
Component: kcm_kwindecorationAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs
Priority: NOR    
Version: 5.22.5   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: screenshot of "Titlebar buttons" tab with the problem
Same issue in the standalone settings module

Description Andrei Rybak 2021-10-13 17:35:01 UTC
Created attachment 142408 [details]
screenshot of "Titlebar buttons" tab with the problem

SUMMARY
Some buttons in "Titlebar buttons" tab of system settings are shown out of bounds of the designated area.

STEPS TO REPRODUCE
1. Open "System Settings > Appearance > Global Theme / Window Decorations > Titlebar Buttons" or the same tab in a standalone settings module (right click on titlebar of any window > More actions > Configure Window Manager...)
2. Observe the titlebar in the preview box

OBSERVED RESULT
Some buttons (minimize, maximize, close) are out of bounds (circled in red). Only part of minimize button is visible.

EXPECTED RESULT
Buttons in the preview correspond to buttons on actual windows (circled in green).

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-37-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
Comment 1 Andrei Rybak 2021-10-13 17:35:25 UTC
Created attachment 142409 [details]
Same issue in the standalone settings module
Comment 2 Andrei Rybak 2021-10-13 17:37:58 UTC
Now that I've read it more carefully, I think this might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=442355
Comment 3 Nate Graham 2021-10-14 23:32:34 UTC
Yup, looks like it. Thanks.

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