Apache OpenOffice (AOO) Bugzilla – Issue 124426
Pop-up errors when open various files on Mac
Last modified: 2017-05-20 10:35:07 UTC
Reported by Michael Rutherford (Thanks!): I'm using the AOO 4.1 Beta on my Mac (OS X 10.9.2) and just wanted you to know that I'm seeing a number of pop-up errors when I open various files. Please note that once I click on "OK" for each of these errors, the file is opened and I can edit successfully. I can provide details as necessary. Confirmed by Clarence Guo (Thanks!): Yes, I can confirm this problem on my MAC 10.9.0 with the latest snapshot build 1573601. But I cannot reproduce the problem on the same OS with build 1566593. So it seems a regression defect happened in the very recent days.
To take action on this issue it is needed to know the following: - Which pop-up errors are shown? - Which files need to be opened to trigger the pop-up errors? Thanks in advance. Otherwise, the issue is similar to a report like "there is a bug".
When open a odt, it reports "General Error", when open a ods, it reports "Not all attributes could be read"
(In reply to Clarence GUO from comment #2) > When open a odt, it reports "General Error", when open a ods, it reports > "Not all attributes could be read" Does it happen with every document?
(In reply to Oliver-Rainer Wittmann from comment #3) > (In reply to Clarence GUO from comment #2) > > When open a odt, it reports "General Error", when open a ods, it reports > > "Not all attributes could be read" > > Does it happen with every document? It happens with every odt and ods document I open. It also happens every time I open a new odt document. I does not happen when I open any other type new document.
I tested it on my MacOS system 10.9.2 as well and was not able to reproduce the described behaviour. Use env - macOs 10.9.2, English locale - AOO 4.1 beta rev. 1573601 Test: - opended several odt, ods, odp files As long as it is not clear reproducable it is no showstopper
Yep, same build here. The files that I see these pop-up errors on were all exclusively created under AOO 4.0.1, so I tried to create new files using the BETA code. At creation time, on both the ODT and ODS file, I received the previously noted errors. In addition, when I attempted to save the newly created ODT file, I received this error: Error saving the document testfilecreatedunder4.1beta: General Error As with the other errors, there was no functional problem...the file saved OK and I was able to reopen it (albeit with the previously mentioned pop-up). Is there a log file that can be looked at that might give us further clues? Could this be an "upgrade" issue? The AOO 4.0.1 application still exists on this system (and can open these new files, as well as all others with no noted error pop-ups).
Can anyone please attach a minimal bugdoc that reliably shows the problem with AOO 4.1.0 Beta?
Is the "bugdoc" something that I can provide? What is it and where can I find it?
(In reply to Michael Rutherford from comment #8) > Is the "bugdoc" something that I can provide? What is it and where can I > find it? Any file that exhibits that reported problem is fine. The smaller the better and with small I mean the least amount of content (e.g. only one page, one paragraph, one line) where the problem still shows when AOO 401 Beta is loading it. E.g. start from a normal doc that shows the problem and remove as much content as possible before the problem disappears.
Created attachment 82862 [details] ODT file exhibiting error on open
Created attachment 82863 [details] ODS file exhibiting error on open
I just attached two files that show the exhibit the error when opening.
@jsc: libunordf.dylib is not loaded because /opt/local/lib/libxml2.2.dylib is not available. libunordf.dylib has a dependency on libraptor.1.dylib which claims to require - /opt/local/lib/libxml2.2.dylib - /opt/local/lib/libz.1.dylib - /opt/local/lib/liblzma.5.dylib - /opt/local/lib/libiconv.2.dylib which are not available on a regular system. On a "normal" system the AOO-builtin libraptor.1.dylib requires - /usr/lib/libxml2.2.dylib - /usr/lib/libz.1.dylib - /usr/lib/libSystem.B.dylib - /usr/lib/libicucore.A.dylib which are available on plain OSX installations. That the problem only shows up for newer documents is caused by ScXMLImportWrapper::Import() checking for RDF metadata in ODF>=1.2 files and that fails because libraptor as RDF support library is not available.
Created attachment 82866 [details] fixed libraptor.1.dylib library I invite everyone who can reproduce the problem to replace libraptor.1.dylib in the AOO410Beta installation by the attached file and check again.
Yep, updated libraptor.1.dylib solved the issue for me.
mmh, ok that sounds reasonable and it seems that a change in my environment caused this problem. A conflict with libs installed via macports that are typically installed under /opt/local/... I will check my env ...
I have cleaned up my env and now the system libxml is used, will be solved for the final.
a good reminder to be careful with macports
no code change necessary. The problem was introduced by a local change in the build env on the machine where the release is build. This problem is solved now. A new test build will be provided later.
grant showstopper flag as reminder for verification of the next available build
*** Issue 124491 has been marked as a duplicate of this issue. ***
*** Issue 124490 has been marked as a duplicate of this issue. ***
No longer needmoreinfo
*** Issue 124563 has been marked as a duplicate of this issue. ***
*** Issue 124566 has been marked as a duplicate of this issue. ***
Verified with the AOO410 release candidate binaries.
This bug is back on RC3 AOO410m17(Build:9763) - Rev. 1586584 2014-04-11 08:56:06 (Fri, 11 Apr 2014) blacks-Mac-Pro:~ black$ otool -L ~/OpenOffice.app/Contents/MacOS/libraptor.1.dylib /Users/black/OpenOffice.app/Contents/MacOS/libraptor.1.dylib: @__________________________________________________OOO/libraptor.1.dylib (compatibility version 3.0.0, current version 3.0.0) /opt/local/lib/libxml2.2.dylib (compatibility version 12.0.0, current version 12.1.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8) /opt/local/lib/liblzma.5.dylib (compatibility version 6.0.0, current version 6.5.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0) /opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0)
it seems that my env has again changed slightly, will be fixed in the next build, thanks for reporting.
*** Issue 124738 has been marked as a duplicate of this issue. ***