This error message means that the mentioned files are missing or corrupted in your user profile. Copy a correct version from C:\Program Files\LibreOffice 3.5\presets\basic\Standard\ to C:\Documents and Settings\Administrator\Application Data\LibreOffice\3\user\basic\Standard\.

<https://bugzilla.redhat.com/show_bug.cgi?id=748232> "missing BASIC library dialogs on startup" and <https://issues.apache.org/ooo/show_bug.cgi?id=59890> "[meta] Error loading basic of document" indicate that there apparently /are/ scenarios that lead to this symptom---though it is unclear what happens exactly.

While copying clean versions of files into the user profile can be a workaround, it would be better to find the root cause of this problem.

I have such error on Linux too https://bugzilla.redhat.com/show_bug.cgi?id=748232

And it is 100% reproduced.

*** Bug 64434 has been marked as a duplicate of this bug. ***

*** Bug 48509 has been marked as a duplicate of this bug. ***

*** Bug 90981 has been marked as a duplicate of this bug. ***

*** Bug 93652 has been marked as a duplicate of this bug. ***

Someone reported symptoms like this today in #libreoffice-qa, so I assume the bug still exists.

I had the same problem. In my case the error message occurs, if in one of the xcd-files (share/registry) or the registrymodifications.xcu in the user profile, the property ooSetupInstCompleted is set to true, although it is not complete. Then some files in the user profile are missing.

<oor:component-data oor:name="Setup" oor:package="org.openoffice">
   <node oor:name="Office">
       <prop oor:name="ooSetupInstCompleted" oor:type="xs:boolean">
	  <value>false</value>
       </prop>
   </node>
</oor:component-data>

(In reply to Malte O from comment #10)
> I had the same problem. In my case the error message occurs, if in one of
> the xcd-files (share/registry) or the registrymodifications.xcu in the user
> profile, the property ooSetupInstCompleted is set to true, although it is
> not complete.

Did you actually find ooSetupInstCompleted being set to true in one of the xcd files (in contrast to being set in registrymodifications.xcu)?

(In reply to Malte O from comment #10)
> I had the same problem. In my case the error message occurs, if in one of
> the xcd-files (share/registry) or the registrymodifications.xcu in the user
> profile, the property ooSetupInstCompleted is set to true, although it is
> not complete. Then some files in the user profile are missing.

How do you know that installation is not yet completed?  How did you install LO?  What abnormal behavior did you observe/what failures happened?  Which files exactly are missing from the user profile?

(In reply to Stephan Bergmann from comment #11) 
> Did you actually find ooSetupInstCompleted being set to true in one of the
> xcd files (in contrast to being set in registrymodifications.xcu)?

No, I didn't find it. I recognized it by trying to customize the office (I wrote an additional xcd-File). And if I install the office and set ooSetupInstCompleted to true before starting the first time, the error message appears, when opening a document.


(In reply to Stephan Bergmann from comment #12) 
> How do you know that installation is not yet completed?  How did you install
> LO?  What abnormal behavior did you observe/what failures happened?  Which
> files exactly are missing from the user profile?

In an additional xcd-File I added "ooSetupInstCompleted" with true (with <dependency file="main" /> in the added xcd-File). Apart from that, I didn't change anything. I install the office in the normal way and after that copy the additional xcd-File into the "share/registry" folder for my own customizing. By starting office the first time the user profile only has the folders "extensions", "uno_packages" and the file "registrymodifiacations.xcu". The "basic" folder and some other folders (for example "autocorr", "autotext", "config", "database"...) are missing. So if I click to open a document, the error message appears, because the basic files are the first files, that are missing, I think.

(In reply to Malte O from comment #13)
> No, I didn't find it. I recognized it by trying to customize the office (I
> wrote an additional xcd-File). And if I install the office and set
> ooSetupInstCompleted to true before starting the first time, the error
> message appears, when opening a document.

So what you're claiming is that the symptoms of the original problem (comment 0) are caused by ooSetupInstCompleted being set to true (in registrymodifications.xcu) despite not all of the UserInstallation tree having been populated properly?  That may well be true.  However, the question still remains why that happened to the original poster (and to those who filed duplicate bugs).

From my duplicate bug report, bug 90981.

Loaded up any libreoffice module/app, i get the following dialog error.

Error loading BASIC of document file:///home/jay/.config/libreofficedev/4_5/user/basic/Standard/script.xlb/:
General Error.
General input/output error.

Looked into the /home/jay/.config/libreofficedev/4_5/user/basic/Standard/ folder and it was empty and if i cleared my profile, the error disappeared.

*** Bug 59216 has been marked as a duplicate of this bug. ***

Since this issue can be quite annoying, and there are plenty of dupes, let's bump the priority.

(In reply to Aron Budea from comment #19)
> Since this issue can be quite annoying, and there are plenty of dupes, let's
> bump the priority.

is it still reproducible in a master build ? How can it be reproduced ?

(In reply to Xisco Faulí from comment #20)
> is it still reproducible in a master build ? How can it be reproduced ?
The result is very easy to reproduce, delete your <user profile>/basic/Standard/script.xlb , and start Writer. What deletes/truncates the file isn't known, possibly a crash at the wrong time, so that may be extremely hard to reproduce, and while it'd be great to fix, the likelihood of that is slim.

This is where this bug crosses into bug 44128 territory, ie. LO should regenerate the default files, and not throw an error (but should still notify the user, since something bad happened before, and the slim chance of figuring out what had gone wrong should still be kept).

Dear sam,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug