unable to open downloaded LibreOffice 4.3.3. get following msg "LibreOffice" can;t be opened because the identity of developer cannot be confirmed. Google chrome downloaded this file at 10:49 AM from download.cnet.com. I tried several times downloading with the same result. I then downloaded 4.3.2.2 and it opens successfully.
unable to open downloaded LibreOffice 4.3.3. get following msg "LibreOffice" can't be opened because the identity of developer cannot be confirmed. Google chrome downloaded this file at 10:49 AM from download.cnet.com. Tried several times downloading with the same result. Then downloaded 4.3.2.2 and it opens successfully.
Larry: do you reproduce this if you download LO from official website, http://www.libreoffice.org/download/libreoffice-fresh/ ?
Since I updated description, I just put again the OSX version of the reporter, 10.9.5
Created attachment 109480 [details] Screenshot of dialog showing problem
This applies to version 4.3.4.1 (and happened also with 4.3.3.2). Both were downloaded directly from http://www.libreoffice.org/download. There is a work around, but the user experience is far from excellent
Thank you for your feedback. I put it at new given the screenshot. Alex: any idea?
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
(In reply to Julien Nabet from comment #6) > Thank you for your feedback. I put it at new given the screenshot. > > Alex: any idea? This is not a new problem. The workaround is either to turn off Gatekeeper momentarily before attempting to install LibreOffice, or else use the context menu on the app bundle and then "Open" to force Gatekeeper to allow the user an option to install despite the warning message. As Frank has said, there is a workaround, but it is not elegant (avoiding Gatekeeper). However, that situation can not change for as long as LibreOffice released by TDF can not sign and release an Apple-approved build, which is why Collabora provide signed builds instead via the AppStore. We are in the same situation as Scribus, or Inkscape, or any other number of opensource projects in this regard. Why Firefox or Thunderbird don't seem to have this problem is beyond my ken (or perhaps they do, and I just haven't noticed). I would love to be able to set this to CANTFIX, but will have to settle for WONTFIX.