Summary: | crash on start / duplicate component registration issue ... | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Michael Meeks <michael.meeks> |
Component: | Libreoffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | medium | CC: | jbfaure, LibreOffice, sbergman |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | (target:3.6.0) | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 43489, 44446 | ||
Attachments: |
~/.config/libreoffice/3
DeploymentException |
Description
Michael Meeks
2012-07-03 03:21:53 UTC
Created attachment 63757 [details]
~/.config/libreoffice/3
I guess we badly need some migration regression tests with odd / canned setups that people can have :-)
removing the profile makes it work; but I fear this is in 3.6 as well ... (In reply to comment #0) > I was amazed tracing the exceptions through here that we go looking for trouble > (and creating directories) in ~/.ure - why ? and /etc/opt/ure/ and other > apparently unhinged locations ;-) Originates from making URE standalone, cf. ure/source/README. UserInstallation's user/extensions/bundled/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/backenddb.xml contains information about bundled extensions that still use active component registration. When an extension is switched from active to passive component registration, it is important that its version is bumped. (Otherwise, LO's extension mgr logic would not detect that it needs to regenerate per-user extension information at start up, which could lead to old, active-registration data for an extension's component co-existing with new, passive-registration data, which in turn could lead to the "duplicate <implementation name" exception at start up.) The pdfimport extension had been changed to passive component registration (but erroneously without bumping its version), and later on its version has been bumped (from 1.0.5 to 1.0.6) with <http://cgit.freedesktop.org/libreoffice/core/commit/?id=de562138eabd3ee3ecab28e5d1348a3fee7301e0> "Bump extension versions after changing to passive registration." If your existing UserInstallation has ever been produced/modified by some "interim" developer build (instead of an "official" build, where it is known that none of them can lead to these inconsistencies), it can have become inconsistent to a point where only manually removing the UserInstallation's user/extensions/bundled directory can fix this, see <http://lists.freedesktop.org/archives/libreoffice/2012-April/030728.html> "Weird runtime error." However, this should not happen to ordinary end users (who only ever installed "official" builds). For the record, we indeed appear to be safe with regard to all combinations of having a single extension installed both bundled and per-user (which could potentially lead to such duplicate implementation name exceptions). On a recent LO master build (that includes at least mysql-connector-ooo.oxt and pdfimporter.oxt as bundled extensions): $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/mysql-connector-ooo.oxt # 1.0.1, using active registration; accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN # manually change solver/unxlngx6/bin/mysql-connector-ooo.oxt:description.xml <version> to 1.0.0 $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/mysql-connector-ooo.oxt # accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN # manually change solver/unxlngx6/bin/mysql-connector-ooo.oxt:description.xml <version> to 1.0.2 $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/mysql-connector-ooo.oxt # accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/pdfimport.oxt # 1.0.6, using passive registration; accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN # manually change solver/unxlngx6/bin/pdfimport.oxt:description.xml <version> to 1.0.5 $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/pdfimport.oxt # accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN # manually change solver/unxlngx6/bin/pdfimport.oxt:description.xml <version> to 1.0.7 $ solver/unxlngx6/installation/opt/program/soffice solver/unxlngx6/bin/pdfimport.oxt # accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... $ rm -rf ~/.config/libreoffice/ $ mv solver/unxlngx6/installation/opt/share/extensions solver/unxlngx6/installation/opt/share/extensions-HIDDEN $ solver/unxlngx6/installation/opt/program/soffice ~/lo3.4/pdfimport.oxt # 1.0.5, still using active registration; accept to install per-user $ mv solver/unxlngx6/installation/opt/share/extensions-HIDDEN solver/unxlngx6/installation/opt/share/extensions $ touch solver/unxlngx6/installation/opt/share/extensions $ solver/unxlngx6/installation/opt/program/soffice ... Exited with code '81' oosplash: re-start with all params ! ... great ! thanks for that Stephan :-) Created attachment 64299 [details]
DeploymentException
a UNO Exception from git/solver/unxlngi6.pro/installation/opt/program/../share/extensions/script-provider-for-python/components.rdb
István: this should have been fixed in RC1 (I believe) - are you still seeing the issue there with your profile ? (In reply to comment #9) > István: this should have been fixed in RC1 (I believe) - are you still seeing > the issue there with your profile ? I was discussing István's problem with him on IRC and he had no other easy way to make available his UserInstallation than to add it to this issue. Quoting #libreoffice-dev: "sberg> pista, your ~/.config/libreoffice/3/user information about bundled extensions has somehow become inconsistent, and I would *love* to assume that it is 'merely' due to the specific repo snapshots you happened to create builds from, see the last paragraph of <https://bugs.freedesktop.org/show_bug.cgi?id=51685#c5>" (In reply to comment #6) > For the record, we indeed appear to be safe with regard to all combinations of > having a single extension installed both bundled and per-user (which could > potentially lead to such duplicate implementation name exceptions). On a > recent LO master build (that includes at least mysql-connector-ooo.oxt and > pdfimporter.oxt as bundled extensions): ...and that experiment, it turns out, was useless, as I used a "make dev-install" build w/o share/prereg/bundled, see <https://bugs.freedesktop.org/show_bug.cgi?id=51252#c35>. @Stephan, @Michael: Please check my assumption concerning target and correct it if necessary. We need correct target information for automatically generated lists for release notes (Remaining Problems ...) (In reply to comment #12) > Please check my assumption concerning target and correct it if necessary. I think we can still consider this specific issue fixed with target:3.6.0. For the regressions caused by the overall fixing in this area see issue 53006, esp. <https://bugs.freedesktop.org/show_bug.cgi?id=53006#c14>. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.