Created attachment 139821 [details] Screen-shot showing rendering issue. SUMMARY Text of the section headings is not rendered fully. See attached screenshot showing as an example sections "Memory" and "Device Viewer", this happens on all headings, not just those two. STEPS TO REPRODUCE 1. Launch kinfocenter 2. 3. OBSERVED RESULT Sections headings not fully rendered. EXPECTED RESULT Sections headings fully rendered :) SOFTWAOperating System: openSUSE Tumbleweed 20210701 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ Memory: 3.8 GiB of RAM Graphics Processor: NV84RE/OS VERSIONS ADDITIONAL INFORMATION
What font and font size are you using? Have you changed the font DPI from its default value? Are you using any scaling settings?
(In reply to Nate Graham from comment #1) > What font and font size are you using? General: "Noto Sans 8pt" Fixed Width: "Hack 8pt" Small: "Carlito 8pt" Toolbar: "Noto Sans 8pt" Menu: "Noto Sans 8pt" Window Title: "Noto Sans 8pt" > Have you changed the font DPI from its default value? No > Are you using any scaling settings? No
Huh, cannot reproduce with those settings. Out of curiosity, do you see the same problem if you switch System Settings to Icon view? You can do this in its settings window, which is accessible through the hamburger menu above the sidebar. Also, does it happen in a new user account?
(In reply to Nate Graham from comment #3) > Huh, cannot reproduce with those settings. > > Out of curiosity, do you see the same problem if you switch System Settings > to Icon view? You can do this in its settings window, which is accessible > through the hamburger menu above the sidebar. I already had "System Settings" set to Icon View (How does the System Settings view affect "kinfocentre", shared code?) > Also, does it happen in a new user account? No... and Yes... Think I've found the problem. With a default setup all is OK. However when I change the Application Style to "QtCurve" (which I prefer for it's more compact appearance) the problem appears. So I guess you can close this report.
Indeed, the QtCurve theme seems to be the culprit.