https://bugs.kde.org/show_bug.cgi?id=438273
--- Comment #7 from Nate Graham <n...@kde.org> --- Found the real bug. People who are affected have at least one more kdeglobals file on their system besides ~/.config/keglobals, and this other kdeglobals file has a color scheme specified in it that includes a [Colors:Header] group. Those people can work around it by removing the [Colors:Header] and [Colors:Header][Inactive] groups from that file. When this file exists, the code that deletes the [Colors:Header] group when switching to a non-header color scheme doesn't actually delete the group and all its entries, it sets the keys' values to [$d] which is supposed to override the other file. However something about this does not work with the way we read colors from the color scheme to actually apply them to the system. Probably we are failing to check for whether the [Colors:Header] group exists or not, and are instead unconditionally reading its entries, rather than either checking for the group's existence using hasGroup() or verifying the existence of its entries' values with hasKey(). -- You are receiving this mail because: You are watching all bug changes.
