Created attachment 102310 [details] Comparisson screenshot If you install extensions through unpacking them to ..\share\extensions\.. (to make them available to all users) they won't work if an extension folder name contains spaces. It will load toolbars, menu entries, etc., but won't load it's code (represented in *.xba files) and won't work at all. Nothing happens when you press the button of an extension or it's menu entry and you can't find it even when customizing menu or toolbar (usually extensions are represented in "my macros" when doing that). Also, version 4.3.x.x won't start at all giving you a failure error. But if you rename the folder in a "proper way" (and delete user data so extension will be re-initialized) it will work perfectly. Version 4.2.4.2 did not have this bug.
Reproduced. Unpacked this http://extensions.libreoffice.org/extension-center/copy-only-visible-cells to C:\Program Files (x86)\LibreOfficeDev 4\share\extensions\copy visi cells\ When I launch Calc, LibO crashes with Fatal error, bad allocation. After removing the extension folder, had to delete user profile to get back to normal. In Ubuntu, LibO refused to run and I got this in the debug output when the folder was present: warn:legacy.osl:4017:5:desktop/source/deployment/dp_persmap.cxx:138: OSL_ASSERT: ('A' <= c) && (c <= 'F') warn:legacy.osl:4017:5:desktop/source/deployment/dp_persmap.cxx:138: OSL_ASSERT: ('A' <= c) && (c <= 'F') warn:legacy.osl:4017:5:desktop/source/deployment/manager/dp_activepackages.cxx:82: OSL_ASSERT: i1 >= 0 terminate called after throwing an instance of 'com::sun::star::deployment::DeploymentException' Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08 Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+ Build ID: 3cf226622a3d8c09d655034dbcc81695f1662b87 TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-15_23:24:22
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.