Summary: | BASIC: LibreOffice app uses some nonstandard to launch itself on OS X | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | mircea |
Component: | BASIC | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | sbergman |
Version: | 4.1.4.2 release | ||
Hardware: | Other | ||
OS: | Mac OS X (All) | ||
Whiteboard: | BSA | ||
i915 platform: | i915 features: |
Description
mircea
2014-01-24 10:11:24 UTC
No idea what (if any) the requirements for the executable's name in FOO.app/Contents/MacOS/ are (I guess that's handled by some info.plist anyway), but for historic and backwards-compatibility reasons the relevant executable is named LibreOffice.app/Contents/MacOS/soffice (and starting it via "open LibreOffice.app" or Finder click on LibreOffice.app does work, so whatever is necessary to set this up seems to be done). You are right. I've checked for the binary and it's still there. I don't know what Parallels Desktop is looking for when scanning recursively throughout the Applications folder. All i can say is that all other apps seem to pass the test with flying colors and parallels desktop then creates a small executable inside the vm. You can ise this file to "open with" and select it. When you do this, the vm file is opened in the mac app you chose. I filed a support request with parallels desktop support team maybe they can shine some light as to why neither LibreOffice nor OpenOffice work while all other apps do. Will get back to you with their response. PS. Compared info.plist from Libreoffice with an info.plist from pages and numbers or another app. Main fields are there but a lot of other one are missing. I got the following mail from Mircea: > Ok. I have news on the subject. Their second level support and developers seem to be aware of the issues and planning a fix. Other apps are affected as well, including native mac apps. > > Libreoffice is off the hook. No bug here. Thus I'm now closing this as Not our bug. Please feel free to reopen this bug if you find out that we do have a bug related to this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.