Bug 441025

Summary: After you use a dark theme, clipboard is permanently dark/unreadable
Product: [Plasma] plasmashell Reporter: David Chmelik <dchmelik>
Component: ClipboardAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.22.4   
Target Milestone: 1.0   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed In:

Description David Chmelik 2021-08-16 02:02:02 UTC 
SUMMARY
After you use a dark theme, clipboard is permanently dark/unreadable.

STEPS TO REPRODUCE
1. Set dark theme/colours.
2. Set light theme/colours.
3. Look at clipboard.

OBSERVED RESULT
Clipboard is still dark grey on black, at some close distance from screen, virtually unreadable even for people with perfect vision.

EXPECTED RESULT
Clipboard should change back to light theme/colours when you change settings->colors to something light.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64-current
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 David Chmelik 2021-08-16 02:03:10 UTC 
And the dark themes should be improved: dark grey on black is a horrible choice, usually almost unreadable, at some close distance, even for people with perfect vision.
Comment 2 Nate Graham 2021-08-16 18:38:29 UTC 
Can you attach a screenshot or set of screenshots or a screen recording that shows the problem? Are you using the Oxygen Plasma theme? If not, which exact Plasma theme or color scheme? How are you setting them? Directly, or by applying a Global Theme?
Comment 3 David Chmelik 2021-08-18 10:13:12 UTC 
It's now not happening after an update.  I use Oxygen theme, but I use Breeze colours altered so the title-bars are one colour instead of a gradient and in the case of dark, background to boxes is black (no other alterations.)
Comment 4 Nate Graham 2021-08-18 14:05:21 UTC 
If the Frameworks 5.85 update fixed it, it's because you were suffering from Bug 438854, which I fixed in that release. :)

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