Summary: | Undefined color: "WINDOW_FOREGROUND" breaks Emacs GUI | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Tamburrino Roberto <perfinstals> |
Component: | kcm_colors | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | abelits, gjditchfield, jpwhiting, kde, mwoehlke.floss, nate, plasma-bugs, sirn |
Priority: | NOR | ||
Version: | 5.20.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Tamburrino Roberto
2020-10-14 21:54:08 UTC
This is not related to kwin, this is a regression in color handling in X11 resources. There was an option in KCM that extends color settings to non-KDE applications by setting X resources. Now, in KDE 5.20, it was removed, and resources are set unconditionally. For some reason the mechanism enables resources with generic color names but never sets the values for those, so programs that take color configuration from X resources end up with undefined color names. KDE should either always set resource values for colors BACKGROUND and WINDOW_FOREGROUND that it mentions (ex: "*.WINDOW_FOREGROUND: black"), or not set resources with those values at all. I worked around this problem by deleting directory /usr/share/kdisplay/app-defaults. That directory comes from package plasma-workspace. I am reassigning the bug to product "plasmashell" because I think that's a better match than kwin, but there may be a better choice. I ran into this problem on a fresh install of Neon 20.04. An upgrade in place from 18.04 did not have this problem. xrdb colour syncing for really old apps has been removed |