Description: Version 7.5 of LO Calc changed Input line background from white to gray (like the rest of the UI) which makes is slightly harder to quickly find. Steps to Reproduce: 1. Open LO Calc Actual Results: Input line is grey Expected Results: It should be white... Reproducible: Always User Profile Reset: No Additional Info: ``` Version: 7.5.0.3 (AARCH64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 10; OS: Mac OS X 13.1; UI render: default; VCL: osx Locale: pl-PL (es_PL.UTF-8); UI: en-US Calc: threaded ```
Can you please share a screenshot of the issue?
Created attachment 185223 [details] Screenshot of gray background in Input field
Added.
[Automated Action] NeedInfo-To-Unconfirmed
I cannot reproduce the issue on Linux/Windows. It may be an osx backend issue, but I don't have a Mac to test it. Let's wait for someone else to test it.
It is also black in dark mode I wonder if this change is related to the new dark mode support?
There were changes as to how LibreOffice follows dark / light mode on macOS. @Wojtek: Could you install LibreOffice nightly build and see if the problem persists using that build: https://dev-builds.libreoffice.org/daily/master Note: To open LibreOffice nightly on macOS please refer to: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616
@steve which version should I use? tb94, tb93, tb92? Will it run on independent (user-data) profile so I can run in in the same system user profile? (so to avoid messing up LO configuration I have)
Main builds use a separate profile. Use the architecture that matches your mac chip (aarch64 for Apple Silicon, x86_64 for Intel).
I know I should choose correct OS and architecture, but even for that combination there are a couple of options. Previously there were 3, but now they are still two: ``` MacOSX-aarch64@tb92-TDF/ - 2023-Apr-22 03:21 MacOSX-aarch64@tb94-TDF/ - 2023-Apr-23 22:05 ``` Which one should I use?
(In reply to Wojtek from comment #11) > Which one should I use? https://dev-builds.libreoffice.org/daily/master/current.html
(In reply to ady from comment #12) > (In reply to Wojtek from comment #11) > > > Which one should I use? > > https://dev-builds.libreoffice.org/daily/master/current.html Sorry, I pressed "save changes" too early. By now, just pick one of those that match your OS and architecture.
@Wojtek: if more than a singel build is available for your computer, why not choose the latest?
@adv I downloaded `LibreOfficeDev_7.6.0.0.alpha0_MacOS_aarch64.dmg` (MacOSX-aarch64@tb92-TDF / 2023-04-22 05:19:34 / https://dev-builds.libreoffice.org/daily/master/MacOSX-aarch64@tb92-TDF/2023-04-22_05.20.54/LibreOfficeDev_7.6.0.0.alpha0_MacOS_aarch64.dmg) But when trying to run it I get the error that the application is broken, and I should move it to trash: `“LibreOfficeDev.app” está dañado y no se puede abrir. Deberías trasladarlo a la papelera.` (it's different from the typical FileVault issue where the package is not signed/notarised and one have to confirm opening in system preferences) @steve Because wanting to be sure that I get the right package? What's more, downloading is very slow...
I checked the other nightly but it has the same issue. (https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616 does not apply in this case neither)
https://wiki.documentfoundation.org/QA/Testing_Daily_Builds#Daily_builds_install_and_run_in_parallel_to_a_normal_release_version Quote (but it's even better to read the wiki page directly): " To run an installed macOS daily build, you either need to open it twice or run this command against the application in a terminal: xattr -d com.apple.quarantine /path/to/LibreOfficeDev.app " HTH.
Thanks ady. ad rem - the issue is still there.
Created attachment 186929 [details] libre.office.7.6.gray.png
Dear Wojtek, 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
With the latest version [1] the issue seems to be gone. [1] Version: 25.2.3.2 (AARCH64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 10; OS: macOS 15.5; UI render: default; VCL: osx Locale: pl-PL (es_PL.UTF-8); UI: en-US Calc: threaded