I have searched Bugzilla and haven't found anything that comes close to
the issue I am experiencing. So before I start destroying & rebuilding
my extensive profile and maybe filing a new bug, I thought I would ask here.
I have 35 extensions (including 2 special dictionaries) installed.
Roughly 12 of them call oLibContainer.LoadLibrary(LibName) which
terminates with a "BASIC runtime error. Type:
com.star.container.NoSuchElementException" error. See:
http://www.mediafire.com/view/1ddd9fd2gkwa4ie/BRT_Error.png This screen
capture is just an example of the error from the "Alternative searching
1.4" extension.
Now the really weird thing is that if I keep LO (any module) open and
reinstall those same extensions they work perfectly, until the next time
I start LO.
This started happening when I first moved up to 4.3.0 and continues
through to 4.3.3 on a Win 7 Ult-x64 box. I am not so much looking for a
fix or work-around, more to find out if anyone else has experienced
anything like this.
TIA
Dave (miserably looking forward to rebuilding his precious profile) Barton
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Extensions Basic Runtime Error · Dave Barton
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.