Bug 470193

Summary:	Kinfocenter inconsistently respecting chosen monospace font
Product:	[Applications] kinfocenter	Reporter:	leonardogilrojo
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	ASSIGNED ---
Severity:	minor	CC:	nate, sitter, usr_40476
Priority:	NOR
Version First Reported In:	5.27.4
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description leonardogilrojo 2023-05-24 05:27:08 UTC

SUMMARY
I have chosen another font other than the default for monospace. If I go into Devices > Firmware Security, I see my chosen font. If instead go into Devices > CPU I see the default font from KDE. 

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 5.15.0-70-generic (64-bit)

Comment 1 Nate Graham 2023-05-24 17:20:06 UTC

Can confirm. The difference between them is that the firmware security KCM has `textFormat: TextEdit.RichText` set on it.

In CommandOutputKcm, we probably want to b explicitly setting the text to the user's chosen monospaced font, instead of using font.family: "monospace".

Comment 2 Bug Janitor Service 2024-03-11 18:57:34 UTC

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/197

Comment 3 Harald Sitter 2024-11-28 14:20:01 UTC

*** Bug 496787 has been marked as a duplicate of this bug. ***