Installing LO 3.4.2 and a long list of add-ons (+90) had few problems than
several prior OO installs. The Extension Manager GUI stability is greatly
improved. No crashes! Yea!
Problems encountered were largely due to the EM installing (or attempting to
install) defective packages, primarily ".zips". Some only vaguely resembled
an OXT package. IMO at a minimum a package that cannot be uninstalled with
standard tools, i.e.: unopkg. should be rejected.
It seems that the presence of bogus packages in the cache prevented
persistent completion of component registration. Repeatedly, start-up
(QuickStart) and first document opening were painfully slow. Each process
consuming IO in the high tens of megabytes.
Changing the JRE used to 6.21 produce a geometric run-time reduction.
Apparently, removing offending extensions has allowed registration
processing to be completed and saved.
There has been a significant and stable reduction in start-up time and IO.
Opening documents after the first is fast. Subjectively much better than OO.
The platform is XP SP3 running on legacy hardware: P4 - 2 MHz, 1 GB 266MHz
DDR, PCI 133.
No errors were reported from several invocations of "unopkg validate" (at
different points in the above process).
The command "unopkg reinstall --shared -v" produced the following message:
"ERROR: cannot get file url from system path:
-env:INIFILENAME=vnd.sun.star.pathname:c:\Software\Office\Libre\v3\program\redirect.ini
Exception details:
(com.sun.star.uno.RuntimeException) { { Message = "cannot get file url from
system path:
-env:INIFILENAME=vnd.sun.star.pathname:c:\\Software\\Office\\Libre\\v3\\program\\redirect.ini",
Context = (com.sun.star.uno.XInterface) @0 } }"
redirect.ini has on entry: URE_BOOTSTRAP=${ORIGIN}/fundamental.ini
fundamental.ini does not have a URE_BOOTSTRAP entry. None was found in any
.ini file examined.
LanguageTool-1.4 was uninstalled. It was generating a runtime exception
about not finding a start class, locales directory not found, it couldn't
write a record because it could find saxon9-dom.jar and was reporting the
use of JRE version 17 (not installed on the system). The exception continued
after saxon9-dom.jar was added to the system class path and to LO Java
options for jre-6.21.
Do any of the issues above require corrective action? If so what needs to
done and/or where should I look for answers?
david
--
View this message in context:
http://nabble.documentfoundation.org/minor-install-config-issues-tp3247894p3247894.html
Sent from the Users mailing list archive at Nabble.com.
--
For unsubscribe instructions e-mail to: [email protected]
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
