You need to remove the directory that holds the user configuration files (I don't recall what this
is called on Win machines) and let it rebuild when you start LO. Unfortunately you will need to
rebuild any customizations you have created previously. I believe this was a bug or regression
between the final beta and first release candidate, but hasn't recurred since.
Paul
----- Original Message -----
From: "Trever Adams" <trever.adams@gmail.com>
To: users@libreoffice.org
Sent: Tuesday, January 25, 2011 7:41:20 PM
Subject: [libreoffice-users] Fatal errors on start in Vista/7 64bit
At first I thought this was an MSI install error. I have removed the
packages and installed via setup. Every time I start I get the
following:
LibreOffice 3.3 - Fatal Error
The application cannot be started
[context="user"] caught unexpected exception!
Sometimes user is "bundled."
I am afraid that this keeps me from testing and recommending
LibreOffice at this time.
Is this a known error.?
Thank you,
Trever Adams
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [libreoffice-users] Fatal errors on start in Vista/7 64bit · pkaplan1
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.