Bug 389502 - Detailed memory information of a process doesn't respect color scheme
Summary: Detailed memory information of a process doesn't respect color scheme
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: 5.17.4
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
: 423322 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-01-27 10:49 UTC by Christian Muehlhaeuser
Modified: 2022-11-10 11:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Strange fonts and partly broken color scheme in memory details (159.55 KB, image/png)
2018-03-11 05:15 UTC, Christian Muehlhaeuser 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Muehlhaeuser 2018-01-27 10:49:26 UTC 
The detailed memory information view of a process doesn't seem to respect color schemes or font settings.

Steps to reproduce:
1. Use a dark color scheme
2. Open system monitor
3. Right click a process, click Detailed Memory Information

Actual Results:  
Black text (incorrect fonts seemingly) on white background.

Expected Results:  
Follow the color scheme and font settings.
Comment 1 Christoph Feck 2018-02-15 00:38:25 UTC 
Hm, commit for bug 360214 should have solved it. Does Archlinux have a patch to make libksysguard use QtWebEngine instead of QtWebKit?
Comment 2 Christian Muehlhaeuser 2018-03-11 05:15:02 UTC 
Created attachment 111312 [details]
Strange fonts and partly broken color scheme in memory details
Comment 3 Christian Muehlhaeuser 2018-03-11 05:20:13 UTC 
It seems to still link to QtWebKit, and I don't think Arch patches ksysguard.
Comment 4 postix 2019-12-10 20:12:55 UTC 
Still broken on:

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2
Comment 5 Patrick Silva 2021-06-09 15:13:46 UTC 
*** Bug 423322 has been marked as a duplicate of this bug. ***
Comment 6 Christian Muehlhaeuser 2022-11-10 11:01:41 UTC 
If I'm not mistaken this has been completely revised and the issue doesn't apply any longer. Closing.