Have there been recent changes to component or extension registration,
as I'm seeing this in my master build of today, Linux 64bit :
instdir/program/soffice
Python exception: <class 'AttributeError'>: 'module' object has no
attribute 'writeRegistryInfo', traceback follows
/home/Development/libo/core/instdir/program/pythonloader.py:152 in
function writeRegistryInfo() [return mod.writeRegistryInfo(
self.ctx.ServiceManager, regKey )]
warn:desktop.deployment:25026:1:desktop/source/deployment/registry/dp_backend.cxx:683:
unexpected RuntimeException "<class 'AttributeError'>: 'module' object
has no attribute 'writeRegistryInfo', traceback follows
/home/Development/libo/core/instdir/program/pythonloader.py:152 in
function writeRegistryInfo() [return mod.writeRegistryInfo(
self.ctx.ServiceManager, regKey )]
"
warn:configmgr:25045:1:configmgr/source/xcuparser.cxx:173: bad set node
<prop> member in
"file:///home/Development/libo/core/instdir/program/../program/../user/extensions/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/lu5ro02d.tmp/Addons.xcu"
warn:configmgr:25045:1:configmgr/source/xcuparser.cxx:173: bad set node
<prop> member in
"file:///home/Development/libo/core/instdir/program/../program/../user/extensions/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/lu5ro02d.tmp/Addons.xcu"
Alex
Context
- registry and extension problems on master 4.3 Linux 64bit · Alex Thurgood
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.