Description: Very often, I need to restart LibreOffice (Writer, Calc, etc...) because of the unreadable menu that it shows in a dark grey background with black text for the options (it doesn't follow the personalization settings of the Libre Office app). I've also tried the reset solution with no Theme, no personalized colors and the result is the same. Sometimes the menu bar (in white background) shows dark menus, sometimes it shows correctly in white bkg and black foreground text Steps to Reproduce: 1.Open a LibreOffice App set with no Theme and light mode 2.click on a menu (File, Edit, View, Insert, .... 3.the Menu background is dark grey (as set in Windows 11 dark mode); the Menu foreground is black (as expected from the LibreOffice personalization settings) Actual Results: Default look: no Theme: Menus are black on dark grey (unreadable) Expected Results: Menus colors should follow entirely the customization settings of the App, not only the text foreground color Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 4; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: it-CH (it_CH); UI: en-US Calc: threaded
Created attachment 184830 [details] LibreOffice BUG:: Menus in black on darkgrey colors (unreadable)
Dark mode support for Windows builds is experimental through the 7.4 releases. Please enable experimental features active (Tools -> Options -> Advanced) and restart LO. If that corrects this is a dup of bug 118320 where https://gerrit.libreoffice.org/c/core/+/138381 has now set the Dark mode support as non-experimental for the 7.5 release.
IIRC, there were many similar bugs, closed somehow as "there is a proper dark mode in 7.5". Which is not what these issues are about; having proper dark menu with bright text in dark mode is not the same as having proper light menu with dark text in app's light mode when running on system with dark mode. In the light of bug 153229, this will have own significance.
This can not be reproduced with 7.5.0.3 or current master against 7.6.0; it was "fixed".