Bug 250579 - x11/plasma5-plasma-workspace: krdb does not replace "WINDOW_FOREGROUND" and similar with current colour scheme
Summary: x11/plasma5-plasma-workspace: krdb does not replace "WINDOW_FOREGROUND" and s...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-kde (Team)
Depends on:
Reported: 2020-10-24 15:59 UTC by Bengt Ahlgren
Modified: 2020-10-25 15:41 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (kde)


Note You need to log in before you can comment on or make changes to this bug.
Description Bengt Ahlgren 2020-10-24 15:59:30 UTC
After the update to 5.20.0, the directory /usr/local/share/kdisplay/app-defaults contain, e.g., Emacs.ad with this content:

Emacs.default.attributeForeground:      WINDOW_FOREGROUND
Emacs.default.attributeBackground:      WINDOW_BACKGROUND
Emacs*Foreground:               WINDOW_FOREGROUND
Emacs*Background:               WINDOW_BACKGROUND
Emacs*menubar*foreground:       FOREGROUND
Emacs*menubar*background:       BACKGROUND
Emacs*popup*Foreground:         FOREGROUND
Emacs*popup*Background:         BACKGROUND
Emacs*Dialog*foreground:        FOREGROUND
Emacs*Dialog*background:        BACKGROUND
Emacs*XlwScrollBar.Foreground:  FOREGROUND
Emacs*XlwScrollBar.Background:  BACKGROUND
Emacs*topToolBarShadowColor:    BACKGROUND
Emacs*bottomToolBarShadowColor: BACKGROUND
Emacs*backgroundToolBarColor:   BACKGROUND
Emacs*toolBarShadowThickness:   0

emacs then cannot run:

$ emacs
Undefined color: "WINDOW_FOREGROUND"

Should the files in this directory perhaps be run through a preprocessor to resolve the uppercase words to proper colour values?
Comment 1 Bengt Ahlgren 2020-10-24 16:16:15 UTC
Hmm, those *.ad files are likely as they should be.

krdb should replace "WINDOW_FOREGROUND" and the like with the current colour scheme, if I understand correctly.  Updating the bug title...
Comment 2 Bengt Ahlgren 2020-10-25 15:41:12 UTC
There is an upstream bug report:


According to it, the bug is fixed in 5.20.1 so I'll just close this issue!