Created attachment 173613 [details] Screenshot of Konsole showing the bug along with another panel that has the default Font. SUMMARY Terminus font is not rendered at all on Konsole or other KDE applications that embed konsole. The xos4 variant works fine though. STEPS TO REPRODUCE 1. Create a new konsole profile. 2. Set profile font to Terminus. OBSERVED RESULT No text is rendered. EXPECTED RESULT Text would be rendered with the Terminus font. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 Kernel Version: 6.10.9-zen1-2-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4800MQ CPU @ 2.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600
After upgrading from KDE Frameworks 6.6.0 to 6.7.0 and Qt 6.7.3 to 6.8.0, this bug now also appears on my main desktop too.
Is this problem specific to konsole? Can you set another KDE application (kate, kdevelop, kwrite, etc.) to use this font, and see if the font is rendered correctly?
(In reply to Matan Ziv-Av from comment #2) > Is this problem specific to konsole? Can you set another KDE application > (kate, kdevelop, kwrite, etc.) to use this font, and see if the font is > rendered correctly? I can confirm Terminus in konsole isn't rendered. All glyphs are empty spaces (transparent 100%?). It's not specific to konsole, indeed. All KDE applications (like Kate, or system configuration) won't render Terminus now. I could spot few more fonts (e.g. ProFont) also are not rendered. All them are OTB fonts, so I assume this is regression in rendering engine. On the other hand, not all OTB fonts have such issues. E.g. https://aur.archlinux.org/packages/terminus-font-ll2-td1 is built from the same terminus-font source, but renders properly.
Forgot to reply yesterday, but can confirm this isn't limited to just Konsole. Dolphin, KWrite/Kate and Qt Designer 6 all appear to be affected, while some others such as System Settings or Filelight are only partially broken.
*** Bug 495672 has been marked as a duplicate of this bug. ***