Description: I have Libreoffice 7.0 (Opensuse Tumbleweed). When I use the Breeze theme, Writer shows the fonts preview without problems (in the drop-down menu, white background and black fonts). But when I use the dark theme, the drop-down menu fails and looks almost illegible. Steps to Reproduce: 1. Apply Breeze dark theme (Opensuse Tumbleweed) 2. Check fonts preview (in Writer) 3. Drop-down fonts menu looks illegible (-very- light grey fonts with white background). 4. The normal Breeze theme (light) works with any problems (in Writer). Actual Results: When I apply de dark Breeze theme the drop-down fonts menu fails: white fonts (in fact, light grey) with white background. When I disable de fonts preview the drop-down menu looks normal (black background with white fonts, obviously without preview). Expected Results: The drop-down fonts menu (in dark mode, with fonts preview checked in Writer) should be legible, (dark background with white fonts). Reproducible: Always User Profile Reset: Yes Additional Info: The fonts size menu or paragraph works properly with dark theme. The problem is only in the fonts menu with preview activated.
Rule of thumb is search before reporting. Looks like a duplicate. *** This bug has been marked as a duplicate of bug 127138 ***
This doesn't look like a dupe of bug 127138...
Created attachment 165622 [details] A screenshot of the issue Happens to me as well. Arch Linux, KDE Plasma 5.19.5, using Breeze Dark Theme.
Moving this to UI because it happens not just in Writer, but also in Calc, Impress and Draw.
New per Comment 3. Please test with master, from https://dev-builds.libreoffice.org/daily/master/current.html or Appimage from https://libreoffice.soluzioniopen.com/daily-version/.
Could be a duplicate of, or at least related to, bug 135565.
Thanks Timur and Ming. I think the evidence is so strong that we should put this to NEEDINFO.
While this bug was reported earlier, technically making bug 135565 a duplicate of this bug, I'll mark this one as duplicate since the issue was (mostly) resolved there. Thanks Timur and Ming. *** This bug has been marked as a duplicate of bug 135565 ***