Bug 433642

Summary: Breeze Light color scheme in kdeglobals incomplete after Plasma 5.21 migration
Product: [Plasma] Breeze Reporter: Nils <bugs.kde.org.trustful938>
Component: Color schemeAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, nate, o.freyermuth
Priority: HI    
Version: 5.21.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=384950
Latest Commit: Version Fixed In:
Attachments: Showing inconsistencies and weird tooltip
compositor
New grey header consistent with the others

Description Nils 2021-02-26 08:40:24 UTC
Created attachment 136183 [details]
Showing inconsistencies and weird tooltip

SUMMARY

Sometimes the header is grey, sometimes it has the same color than everything. Tooltip within those header seem broken too. See attached file for more information.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.11.1-arch1-1
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Comment 1 Nate Graham 2021-02-26 16:23:10 UTC
The color thing works fine for me.

Tooltips being broken would be a separate issue; can you file a separate bug report for it?

Also, do things start working better if you turn on compositing? I notice it is turned off.
Comment 2 Nils 2021-02-26 16:56:14 UTC
Still broken even after turning on the compositing. It had crashed sometimes in the past and never launched again after that. Not the first time it happened to me. I would like very much to see the compositing restart when it crash and not just turn-off? Or maybe have a notification somewhere that it has been permanently disabled.
Comment 3 Nils 2021-02-26 16:56:33 UTC
Created attachment 136199 [details]
compositor
Comment 4 Nate Graham 2021-02-26 17:30:16 UTC
Can you try something for me:

Turn on compositing.

Go to System Settings > Appearance > Colors > switch to Breeze Light color scheme

Then see if the color issue is fixed.

Then change back to the Breeze color scheme (which is what you appear t be using)

And see if it's fixed or broken again.

Thanks!
Comment 5 Nils 2021-02-26 17:41:25 UTC
I was using Breeze Light in fact. I switched back and forth with Breeze. And now I have the same grey everywhere. A bit surprising but I suppose it's the new appearance. 
See attached file to confirm the issue is fixed.
Comment 6 Nils 2021-02-26 17:41:50 UTC
Created attachment 136202 [details]
New grey header consistent with the others
Comment 7 Nate Graham 2021-02-27 02:56:52 UTC
There go.

So it looks like your colors got incompletely migrated following the upgrade.
Comment 8 Nate Graham 2021-02-27 22:40:59 UTC
Please don't close bug reports with no explanation.
Comment 9 Nils 2021-02-27 22:44:52 UTC
Hu sorry, I was thinking that it was now solved because it's consistent? I don't have the issue anymore. And because I didn't think initially that the header would then be grey I'm not sure that the problem wasn't the compositor.
Comment 10 Nate Graham 2021-02-27 23:19:11 UTC
Applying the manual workaround I described may have fixed it for you, but there's still a problem that can affect other people. :) We can't tell millions of users to apply a manual workaround.
Comment 11 David Redondo 2021-03-01 08:11:29 UTC
I would suspect maybe plasma cache instead? Color scheme does not explain for example only one corner not colored. By switching the color scheme the plasma cache was updated?
Comment 12 Nate Graham 2021-06-09 22:05:41 UTC
*** Bug 438357 has been marked as a duplicate of this bug. ***
Comment 13 Nate Graham 2021-09-17 21:02:49 UTC
Would be fixed automatically if we fixed Bug 384950.
Comment 14 Bug Janitor Service 2021-09-21 17:04:11 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze/-/merge_requests/146
Comment 15 Nate Graham 2021-09-22 15:15:19 UTC
(In reply to David Redondo from comment #11)
> I would suspect maybe plasma cache instead? Color scheme does not explain
> for example only one corner not colored. By switching the color scheme the
> plasma cache was updated?

In retrospect, it was probably that, yeah. We haven't gotten other reports of this (if it was widespread, this bug report would have 20 duplicates).