Description: I just upgraded to LibreOffice 6.0.0.3, and now toolbar backgrounds are white instead of following the Windows hight contrast theme (and I haven't been able to find any way to change this in the settings). Steps to Reproduce: 1. set Windows to dark high-contrast theme 2. run any of the LibreOffice programs Actual Results: Toolbar background is white Expected Results: Toolbar background uses theme colour Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.121 Safari/537.36 Vivaldi/1.95.1077.41
Created attachment 139525 [details] Screenshot of the problem
Reproduced. It kind of feels like the return of bug 43131. I mean even High contrast white looks bad (see the bold, italics, underline, align icons). Version: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group
*** Bug 119237 has been marked as a duplicate of this bug. ***
Created attachment 144742 [details] Toolbar High Contrast problem in 6.1.0.3 Problem persists in 6.1.0.3.
*** Bug 120090 has been marked as a duplicate of this bug. ***
Dear Jernej Simončič, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 155293 [details] 6.3.1.2 screenshot showing the bug Bug is still present in 6.3.1.2. Help → About: Različica: 6.3.1.2 (x64) ID gradnje: b79626edf0065ac373bd1df5c28bd630b4424273 Niti CPE: 8; Op. sistem: Windows 10.0; Upodobitev vmesnika: privzeta; VCL: win; Področna nastavitev: sl-SI (sl_SI); Jezik vmesnika: sl-SI Calc: threaded
In 6.3.3.2 and 6.4.0.0.alpha1 this issue is still present; Versie: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU-threads: 4; Besturingssysteem: Windows 10.0; UI-render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-taal: nl-NL Calc: threaded Versie: 6.4.0.0.alpha1 (x64) Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787 CPU-threads: 4; Besturingssysteem: Windows 10.0 Build 17763; UI-render: GL; VCL: win; Locale : nl-NL (nl_NL); UI-taal: nl-NL Calc: threaded Attached: * theme-dark-01.png * theme-dark-02.png Steps to reproduce: * Star LO Writer with a clean profile, in Extra Settings set you Personal Theme to Dark as shown in theme-dark-01.png * Shutdown LO and restart Writer, now the Theme appears as in theme-dark-02.png
Created attachment 155893 [details] theme-dark-01.png
Created attachment 155894 [details] theme-dark-02.png
Dear Jernej Simončič, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still present in LibreOffice 7.2.2.2, and as my original comment states, this regression started with LibreOffice 6.0 – v5 did not have this problem.
Regression introduced by : https://git.libreoffice.org/core/commit/7f0bf6220bd69cf119878ebd1352b55a042b88ed commit 7f0bf6220bd69cf119878ebd1352b55a042b88ed [log] author Stephan Bergmann <sbergman@redhat.com> Wed Oct 04 10:16:31 2017 +0200 committer Stephan Bergmann <sbergman@redhat.com> Wed Oct 04 13:45:39 2017 +0200 tree 30590d14fbe352ddedb20ce3c916657939a64ebd parent aed1870375cd2b718fcc5fe19cdc27b711747d9c [diff] Bisected with : win32-6.0 Adding CC : to Stephan Bergmann
(In reply to Deep17 from comment #14) > Regression introduced by : > > https://git.libreoffice.org/core/commit/ > 7f0bf6220bd69cf119878ebd1352b55a042b88ed It doesn't seem like the correct result. Did you check it by saying git checkout for the binary hash of the bad commit, testing, then moving to the preceding commit by saying git checkout HEAD^ and testing again (bug should not appear)? You can find out the binary hash of the bad commit with this when in the win32-6.0 repo: git log --all --grep='7f0bf6220bd69cf119878ebd1352b55a042b88ed'
(In reply to Buovjaga from comment #15) > (In reply to Deep17 from comment #14) > > Regression introduced by : > > > > https://git.libreoffice.org/core/commit/ > > 7f0bf6220bd69cf119878ebd1352b55a042b88ed > > It doesn't seem like the correct result. Did you check it by saying git > checkout for the binary hash of the bad commit, testing, then moving to the > preceding commit by saying git checkout HEAD^ and testing again (bug should > not appear)? > > You can find out the binary hash of the bad commit with this when in the > win32-6.0 repo: > > git log --all --grep='7f0bf6220bd69cf119878ebd1352b55a042b88ed' I followed the steps you mentioned. I can see bug in the git checkout for the binary hash of the bad commit and I couldn't see bug on git checkout HEAD^.
Can affected users please test again with LO 7.5? Many high contrast and dark mode improvements made it into this version. Thank you.
7.5 seems to have fixed the problem.
(In reply to Jernej Simončič from comment #18) > 7.5 seems to have fixed the problem. Thank you for the quick reply! Let's resolve as "works for me" then.