Created attachment 170942 [details] Screenshot of window *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open up Display Configuration -- System Settings 2. Compositor is misspelled as "Compos tor" ("i" is missing) 3. OBSERVED RESULT Compos tor EXPECTED RESULT Compositor SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 6.6.32-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:41:25 UTC 2024 x86_64 GNU/Linux (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
It's definitely correctly spelled in the source, and it's also correct on my PC. What display scale are you using? Does the "i" appear when you change it to 100%?
(In reply to Zamundaaa from comment #1) > It's definitely correctly spelled in the source, and it's also correct on my > PC. > What display scale are you using? Does the "i" appear when you change it to > 100%? I’ve just logged in to edit my “bug”, it was a display issue when I increased the zoom, I only noticed it later, my apologies for wasting your time
(In reply to Mark from comment #2) > (In reply to Zamundaaa from comment #1) > > It's definitely correctly spelled in the source, and it's also correct on my > > PC. > > What display scale are you using? Does the "i" appear when you change it to > > 100%? > > I’ve just logged in to edit my “bug”, it was a display issue when I > increased the zoom, I only noticed it later, my apologies for wasting your > time Thank you for your patience
No time wasted here, it's still a bug, even if it's not in KWin. What scale were you using where the problem appeared?
Some kind of fractional scaling glitch, yeah. Please report your scale factor for actual monitor resolution. Also, what anti-aliasing setting are you using, and is this on a rotated monitor?
Created attachment 170990 [details] Screenshot_20240626_073851.png Good morning Nate, from Pretoria, South Africa Herewith screenshots that should answer your questions. My monitor is not rotated. After changing my resolution per the 'Display Configuration' the "i" in "Compositor" disappeared. I can't remember the resolution at the time, but it was less than 125%. I have tried to replicate the issue with resolutions from 100% to 125%, in 6.25% increments (dictated by the system), but it's perfect now at every resolution. I'm glad I took the screenshot of the issue, otherwise I would think I'm losing my mind. Kind regards Mark On 25/06/2024 16:52, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=489159 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Summary|Misspelling of Window Menu |Fractional scaling text > |Item |rendering glitch that > | |causes horizontal > | |stretching and squashing of > | |letters > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #5 from Nate Graham <nate@kde.org> --- > Some kind of fractional scaling glitch, yeah. > > Please report your scale factor for actual monitor resolution. > > Also, what anti-aliasing setting are you using, and is this on a rotated > monitor? >
Created attachment 170991 [details] Screenshot_20240626_073902.png
Created attachment 170992 [details] Screenshot_20240626_073922.png
Created attachment 170993 [details] Screenshot_20240626_073947.png
Created attachment 170994 [details] Screenshot_20240626_074015.png
Created attachment 170995 [details] Screenshot_20240626_074024.png
Created attachment 170996 [details] Screenshot_20240626_074110.png
Created attachment 170997 [details] Screenshot_20240626_074941.png
Created attachment 170998 [details] Screenshot_20240626_075419.png
Thanks. Being on X11 and using an NVIDIA GPU with the NVIDIA control center complicates the scenario, since now we have multiple things touching how stuff is rendered on the screen. I see you've also changed the value of the Force Font DPI setting from its default value of 114 (calculated as `scale factor * 96`) to 120. Given all the custom settings at play here, I'm not sure there's any chance we'll be able to figure this out if it can't be reproduced anymore, sorry. :(