| Summary: | Plasma 6.3.4 breaks Panel Colorizer | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | EatMe <glacourse> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | luisbocanegra17b, nate, niccolo.venerandi, notmart |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
EatMe
2025-04-06 09:42:54 UTC
Is there any problem when *not* using Panel Colorizer? If everything is fine in that case, then probably this is a case where a bug we fixed caused the issue by inverting an inappropriate workaround that Panel Colorizer was applying; possibly this was https://invent.kde.org/plasma/libplasma/-/commit/f37ea393ff97ec5b8ac66ed33028e5c7b7539659. If removing or discontinuing the use of Panel Colorizer resolves the issue for you, I'd recommend reporting this its developer, referencing the information I've provided here. Hi, Panel Colorizer dev here, my widget uses a weird hack with two invisible rectangles to keep a hold of the Kirigami.Theme colors, but something changed somewhere and now these invisible rectangles have become black, making them visible with opacity of 0 seems to get around this change. If I recall correctly I had to use that approach to avoid overriding the color bindings or something like that, but maybe there is a better approach I am unaware of patch: https://github.com/luisbocanegra/plasma-panel-colorizer/commit/d167eafe75c2c8cc06b88687ac15130621ff53a2 downstream report: https://github.com/luisbocanegra/plasma-panel-colorizer/issues/212 Not sure if it still can break due to https://invent.kde.org/plasma/libplasma/-/commit/f37ea393ff97ec5b8ac66ed33028e5c7b7539659 but it seems it doesn't I've posted on her, the forum, and on the github page so no matter where this issue is coming from it can hopefully be addressed. I'm not assuming where the issue is occurring cause I know nothing about the underpinning of the code involved. |