@color undefined-section-name-color = red seems to not work

[p.os...@datec.at]

I am on Leo "Leo 6.8.7, October 11, 2025" and for a considerable time now 
"@color undefined-section-name-color = red" shows white text on white background instead of "The color of name in << name >> when name is undefined." as written in the body - which should be red.

I can reveal the text by selecting it, so I see it's there. That's also the reason why I didn't care for so long. Bit now, I'd like to overcome that color problem.

Probably relevant: I'm on EndeavourOS and have to set the env vars before starting Leo:

export QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/qt6/plugins/platforms/  
export QT_PLUGIN_PATH=/usr/lib/qt6/plugins/platforms

Apart from that I guess that the color setting was renamed in one of the earlier versions.

Any idea what to change in my settings?

[Thomas Passin]

Interesting — I have an EndeavorOs VM and I didn't need to set those variables. What counts as an undefined section?  If you use a theme with a dark background, how visible is the text?

[p.os...@datec.at]

If I don't set those env vars, I get

read only: /usr/lib/python3.13/site-packages/leo/config/leoSettings.leo
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted                    (core dumped) leo

when I start leo.

If I use a dark theme (I dont like dark themes), in <<xxx>> the xxx is visible (and underlined), when the child node <<xxx>> is missing.

[Thomas Passin]

In both my Windows and Linux installs, `@color undefined-section-name-color = red` exists in LeoSettings.com. I found that setting name in LeoPyRef in defineDefaultColorsDict in the line

'name'          : ('undefined_section_name_color', 'red')  'red')

I didn't find it anywhere else.