Created attachment 424695 [details]
Debug information generated by Openoffice when it crashed
Description of problem:
When trying to open a file COE_JUP_BuildProcedure.dot with a document template, Openoffice crashes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ooffice COE_JUP_BuildProcedure.dot
Crash message from Openoffice.
The document in an editor window.
The initial error message is
terminate called after throwing an instance of 'com::sun::star::lang::DisposedException'
Created attachment 424701 [details]
The document causing the crash
This is what I try to open when I get the crash. (The document is copyrighted by Jeppesen, but can be used freely for the purpose of investigating this bug.)
I fancy this as a duplicate of bug 566679. Very similar stack anyway.
i.e. my suspicion is that it's not directly connected to the .dot file, but to a corruption or different db4 format cache file in your ~/.openoffice.org* dir.
a) make sure OOo is shutdown
b) mv .openoffice.org backupconfig
and see if the .dot then opens up
if it does then you can
c) tar cjf backupconfig.tar.gz backupconfig
and attach it here for a look-see at the config
Created attachment 424736 [details]
Old configuration as requested
That seems like a correct assumption. After moving away my configuration I could open the document.
file ./3/user/uno_packages/cache/uno_packages.db ./3/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/registered_packages.db
./3/user/uno_packages/cache/uno_packages.db: Berkeley DB (Hash, version 9, native byte-order)
./3/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/registered_packages.db: Berkeley DB (Hash, version 9, native byte-order)
Indeed, exactly the same as bug 566679 those should be version 8 on RHEL-5, so they were possibly created by a different db4 somehow, the other time i saw that was a dual boot box with a shared home dir, same might happen over nfs maybe
*** This bug has been marked as a duplicate of bug 566679 ***
It could be a pollution from RHEL 6 in my case too. I have a test installation of RHEL 6 in a virtual machine. I'm not sure, but I may have tried Openoffice in it, using my ordinary home directory at the time.