Note: _This is specific to Linux and possibly KDE._
When cloning an entry with "Replace username and password with references" selected, the username and password are replaced with references like {REF:U@I:UID}. This causes the color of that entry to use the window background instead of a more appropriate color like inactive text, negative text, etc. This makes the text unreadable with a dark scheme.
The text should be readable.
The text is unreadable due to the color used. I know it's not really the color, rather the widget property used to style the item. I'm not a GUI programmer and don't know the proper terminology.
Style it with an appropriate color from the view color set.
{REF:U@I:UID} to the username and reopen KeePassXC.
I can't read entries with references.
KeePassXC - Version 2.2.0 (2.2.0-15.1 from the openSUSE repository)
Revision: caa49a8ef3ee28ed478192389b21d61107b3b8e0
Libraries:
Operating system: openSUSE Leap 42.2
CPU architecture: x86_64
Kernel: linux 4.4.74-18.20-default
Enabled extensions:
This is the Obsidian Coast scheme. The 3rd entry is highlighted.

If I change the Window Background to green...

I get green text.

I have _Apply colors to non-Qt applications_ checked.
Here's the KDE version from KInfocenter.
Any update to this issue? It also occurs on MacOS Mojave 10.14.3

Same issue here in Manjaro Linux with KDE Plasma 5.14.5 and gnome 3.28.

Any update? Since 2.4.0 will use dark mode when enabled in Mojave this is a huge problem, as 80% of my entries use references and they are not readable anymore:

I'm still seeing this happening on KDE Plasma 15.5.5. I'm using the Breeze Transparent Dark theme:

KeePassXC - Version 2.4.1
Revision: 7bafe65
Qt 5.12.3
Debugging mode is disabled.
Operating system: Arch Linux
CPU architecture: x86_64
Kernel: linux 5.1.5-arch1-2-ARCH
Enabled extensions:
Cryptographic libraries:
libgcrypt 1.8.4
This fix was specific to macOS.
Oh, my bad. Should I open a new issue then?
Yes please. We need to have a more generic way of detecting "dark mode" across platforms.
Most helpful comment
Any update to this issue? It also occurs on MacOS Mojave 10.14.3
