Bug 357202

Summary: Using Dark Themes, menus in the Desktop Wallpaper Settings Plugin are unreadable because those menus have white background instead of using the dark background from the theme or dark color scheme
Product: [Plasma] plasmashell Reporter: Colin <colinnkeenan>
Component: Image WallpaperAssignee: Marco Martin <notmart>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, plasma-bugs
Priority: NOR    
Version: 5.5.2   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
URL: http://i.imgur.com/9hEjjTj.png
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Colin 2015-12-27 05:02:13 UTC
Menus in the Desktop Wallpaper Settings Plugin obey the color scheme when presenting text but don't obey the color scheme for the background of that text. They use a white background while also using the white text as defined. The result is white text on a white background which is completely unreadable. It's only possible to see what the menu entries are as they are highlighted during mouseover.

Reproducible: Always

Steps to Reproduce:
1. Choose a dark theme
2. Right-click on desktop and choose Desktop Settings
3. Click the Wallpaper Type drop-down menu

Actual Results:  
The drop-down menu displays an empty white rectangle with a single highlighted entry showing the currently selected wallpaper type. The reason the rest of the rectangle is empty is that the text is the same color as the background: white.

Expected Results:  
The drop-down menu should display a list showing what wallpaper types are available. This list should be displayed as white text on a black background.

Appearance Settings In Use When The Linked Screenshot Was Taken

-Workspace Theme-
Look And Feel: Breeze Dark
Desktop Theme: SimpleGrey

-Color-
Scheme: vertex negro

-Application Style-
Widget style: Breeze

There is not a "Breeze Dark" widget style. This should not matter for the drop-down menu because drop-down menus in other settings windows do not have this problem.
Comment 1 David Edmundson 2015-12-27 15:02:41 UTC

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