Bug 361673 - systemmonitor detailed view : breeze-dark unreadable
Summary: systemmonitor detailed view : breeze-dark unreadable
Status: RESOLVED DUPLICATE of bug 343436
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor (show other bugs)
Version: master
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 14:27 UTC by Bruno Friedmann
Modified: 2017-06-17 13:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
systemmonitor with breeze-dark theme (252.67 KB, image/jpeg)
2016-04-12 14:29 UTC, Bruno Friedmann
Details
systemmonitor with breeze-dark theme detailed view (3.46 MB, image/png)
2016-04-13 09:14 UTC, Bruno Friedmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2016-04-12 14:27:41 UTC
The panel doesn't follow VDG rules about dark theme.
The background is dark, and the font used too. 
See print-screen attached

Reproducible: Always

Steps to Reproduce:
1. Use breeze-dark theme
2. open systemmonitor
3. click right on systemmonitor -> choose detailled view
4. try to read informations


Actual Results:  
a dark background with a dark color for font.

Expected Results:  
have a better readeable panel 

I let it as normal bug level cause you can copy and paste the shown informations elsewhere.
So there's no workaround excepted changing theme each time you need systemmonitor, which is not what we can call "user friendly" ;-)
Comment 1 Bruno Friedmann 2016-04-12 14:29:28 UTC
Created attachment 98359 [details]
systemmonitor with breeze-dark theme
Comment 2 Marco Martin 2016-04-13 09:09:53 UTC
the screenshot seems empty.
what applet exactly is giving the problem?
Comment 3 Bruno Friedmann 2016-04-13 09:14:35 UTC
Created attachment 98371 [details]
systemmonitor with breeze-dark theme detailed view
Comment 4 Bruno Friedmann 2016-04-13 09:15:38 UTC
Sorry Martin, get caught by a spectale bug ;-) 
The new screenshot should better show the problem in the detailled view as described in the report
Comment 5 razrfalcon 2017-06-17 12:10:14 UTC
Same here.
Comment 6 Christoph Feck 2017-06-17 13:34:37 UTC

*** This bug has been marked as a duplicate of bug 343436 ***