Description: MacOS langauge pack DMGs for LO 6.3.0.0beta2 open with wrong window background, but only if MacOS LO 6.3.0.0beta2 application installer DMG is mounted. If 6.3.0.0beta2 application installer DMG is not mounted, language pack installer correctly displays with plain background. Steps to Reproduce: 1. Download MacOS LO 6.3.0.0beta2 application installer here: https://dev-builds.libreoffice.org/pre-releases/mac/x86_64/LibreOfficeDev_6.3.0.0.beta2_MacOS_x86-64.dmg 2. Download a language pack for LO 6.3.0.0 beta2 from https://dev-builds.libreoffice.org/pre-releases/mac/x86_64/?C=N&O=A 3. Double-click on the LO 6.3.0.0beta2 installer DMG to mount it. 4. Double-click on the LO 6.3.0.0beta2 language pack. Actual Results: For at least these three language packs: LibreOfficeDev_6.3.0.0.beta2_MacOS_x86-64_langpack_de.dmg LibreOfficeDev_6.3.0.0.beta2_MacOS_x86-64_langpack_en-ZA.dmg LibreOfficeDev_6.3.0.0.beta2_MacOS_x86-64_langpack_en-GB.dmg ... the resulting window has a background with a borad green arrow on it. This looks to be the background image for the main Mac LO installer, where the application should be dragged to the Applications folder. However, the Language Pack should instead be installed by double-clicking on the "Language Pack" file (which is present, and can be double-clicked - hence this is a minor bug with an easy work-around). Expected Results: Window should have plain white background. This is what happens if the language pack DMG is double-clicked when the main installer DMG is not mounted. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 152374 [details] Buggy LO language pack window Buggy LO language pack window
In case it makes a difference, I'm running MacOS 10.11.6. Bug not observed with any previous LO version installed on this Mac under this OS.
Bug NOT present in: Version: 6.3.0.1 Build ID: 41ac97386aba908b6db860cfb4cfe2da871886ae CPU threads: 4; OS: Mac OS X 10.11.6; UI render: default; VCL: osx; Locale: en-GB (en.UTF-8); UI-Language: en-US Calc: threaded ... running under Mac OS 10.11.6. So it looks as though this bug in 6.3.0.0 beta2 has been fixed in LO 6.3.0.1 (LO 6.3 Release Candidate 1). I don't know exactly which commit fixed this, so changing status to RESOLVED WORKSFORME.