Created attachment 143369 [details] Screenshot: Left Kate, Right Info Center STEPS TO REPRODUCE 1) Open Info Center 2) Click in section "Detailed Information" on "Devices" 3) Click on "SMART Status" 4) Pick on of your drives and click on "Detailed Information" 5) Copy the result into Kate OBSERVED RESULT The report is hard to read in Info Center as they indention are not correct. However, the necessary information is there since, when you select and paste the report into Kate, it shows the indention just fine. Please see the screenshot. EXPECTED RESULT Correctly indented text in Info Center. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211106 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2
Looks like it's using a variable-width font when it should be using a fixed-width font.
https://invent.kde.org/plasma/plasma-disks/-/blob/afc0180990f2e6f944bfa313e9b5682ea4992594/src/kcm/package/contents/ui/ReportPage.qml#L15 Surely your system has as non-monospace font configured as monospace font?
(In reply to Harald Sitter from comment #2) > Surely your system has as non-monospace font configured as monospace font? Nope, it should be fine as in Kate or Konsole: I use `Hack 9pt`, which is a monospace font, for the fixed font size.
Let me change this bug to the more general "kinfocenter", as I experience the same issue also for `Devices: "CPU" and "Interrupts"`.
It looks like it ignores the monospace font setting from Systemsettings: Whatever I choose there and restart KInfocenter, the font looks all the same in these subsections.
(In reply to postix from comment #3) > (In reply to Harald Sitter from comment #2) > > Surely your system has as non-monospace font configured as monospace font? Sorry, one coffee more this Monday morning: Surely the setting of the Systemsettings has nothing to do with it. In ``` /usr/share/kpackage/kcms/plasma_disks/contents/ui/ReportPage.qml ``` I have manually changed `font.family: "monospace"` to `font.family: "hack"`, restarted the KInfocenter and the bug has vanished for the report page. Though, I have a font called `monospace` installed though (which I can choose in Systemsettings). Why doesn't it work with that default one?
What's the complete output of `fc-match monospace -s`
Oh, actually, you have a font called monospace? Why surely that gets used here. This would break all sorts of things. 'monospace' is a well defined alias in fontconfig referring to the monospace fonts list. I'm honestly not sure we can do anything about this malfunctioning if you have a font called monospace, longer term a bit better API would help but in the end that font always conflicts with the fontconfig alias.
Created attachment 143728 [details] `fc-match monospace -s` Answer to Comment 7
Created attachment 143729 [details] Screenshot: Systemsettings, fontselection Dialog (In reply to Harald Sitter from comment #8) > Oh, actually, you have a font called monospace? Why surely that gets used > here. According to `fc-match monospace -s` no, but there's a font called "Monospace" in the font selection dialog in the Systemsettings, which can be seen in the screenshot.
What I think we are seeing is that Monospace is a font and so fc-match -s gives us the fallback list. Which makes sense, since your Monospace is a sans serif font so its first fallback is the default sans font (Noto). I would suggest that you try finding and removing the monospace ttf, logout and back in and see if that helps at all. In any even it's not really a kinfocenter bug since fc-match clearly resolves a sans fonts. So, that may be a fontconfig problem, but really the fact that you have a font called the name of a font family and then not even be member of that family is 9 types of edge case all at once. Like if Monospace was actually monospace we'd probably never have noticed.
> I would suggest that you try finding and removing the monospace ttf I have searched and found the reason: When I had set up ``` ~/.config/fontconfig/fonts.conf ``` to use preferably `Noto Sans` and `Noto Color Emoji` in order to correctly display Emojis across Plasma, I had accidentally entered both too for the `monospace` font family. Riddle solved and sorry again for this stupid mistake!
And finally thank you all for your help and hints as always!