Bug 329273 - Text not readable due to wrong text color
Summary: Text not readable due to wrong text color
Status: REPORTED
Alias: None
Product: KSystemLog
Classification: Applications
Component: general (show other bugs)
Version: 0.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Nicolas Ternisien
URL:
Keywords:
: 361359 419205 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-12-27 11:00 UTC by Heiko Tietze
Modified: 2020-03-25 01:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
screenshot (157.12 KB, image/png)
2018-03-01 06:35 UTC, gapon 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Tietze 2013-12-27 11:00:06 UTC 
Using a dark theme like Wonton Soup makes it hard if not impossible to read the list of messages with font in navy color. The first, fix columns are painted correctly with light grey color. 
And consider to provide a configuration for user-defined colors.

Reproducible: Always

Steps to Reproduce:
Switch to Wonton Soup, open ksystemlog and try to read messages.
Actual Results:  
Text color is navy.

Expected Results:  
Text color as defined in theme.
Comment 1 Christoph Feck 2013-12-29 14:41:34 UTC 
As a workaround, you can uncheck "Colored log lines" in General Settings.
Comment 2 Heiko Tietze 2013-12-29 14:56:43 UTC 
Thanks for this tip. I was desperately looking for such an option - and obviously missed it.
Comment 3 Christoph Feck 2016-06-20 17:37:49 UTC 
*** Bug 361359 has been marked as a duplicate of this bug. ***
Comment 4 gapon 2018-03-01 06:33:53 UTC 
I can confirm that the issue is still valid. Attaching screenshot from Kubuntu 17.10.

Thanks.
Comment 5 gapon 2018-03-01 06:35:15 UTC 
Created attachment 111102 [details]
screenshot

The text is difficult to read, especially the blue one. I am not aware of any other KDE application having similar issues with a dark theme.
Comment 6 Christoph Feck 2020-03-25 01:16:28 UTC 
*** Bug 419205 has been marked as a duplicate of this bug. ***