Created attachment 117612 [details] screenshot STEPS TO REPRODUCE 1. set breeze dark theme in system settings > look and feel 2. open a text file with kate 3. OBSERVED RESULT Dark text on dark background, see the screenshot. EXPECTED RESULT readable text SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0
Can anyone else confirm this bug? It persists here. Operating System: Arch Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1
Well, I'm also on Arch, so no surprise/new to confirm this. I have observed that the colors differ from file type to file type and have fumbled in the config settings to make some of them halfway readable. Very annoying.
Have ever used the "Use KDE color scheme" button in kate -> settings -> configure kate -> fonts & colors? I suspect that this issue happens if the "use kde color scheme" functionality is used; to confirm please attach ~/.config/kateschemarc.
Created attachment 118485 [details] kateschemarc file I clicked "Use KDE color scheme" button a few days ago to try to solve the problem. Nothing changed. I can't reproduce starting plasma with another user account.
The attached file confirms it; if you delete the [Normal] section of that file and restart kate, I think the problem will be fixed for the Normal kate color scheme.
(In reply to Ahmad Samir from comment #5) > if you delete the [Normal] section of that > file and restart kate, I think the problem will be fixed for the Normal kate > color scheme. I just deleted [Normal] section, it's fixed now. Thanks.
Created attachment 118499 [details] screenshot, xslt file, config file Then I was a little too quick with my confirmation. My problem seems to be different. That xslt file is the only one I can find currently as example which is still almost unreadable (at least that blue), because I didn't need it. All other file types I had changed by that config page. Beside that dummy entry was my config section empty.
@Lothar: it looks like your issue is different. The original report here looks like a duplicate of bug 315141. *** This bug has been marked as a duplicate of bug 315141 ***