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
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Is duplicate of 114708 *** This bug has been marked as a duplicate of bug 114708 ***
bugs of documents and files are reshaped for the fitness for the elements for all humans. The turns of the bugs and https://www.bestdissertations.com/phd-dissertation-writing.php or the file for all programs for the terms. The true value is judged for the identification of the bugs from the document for the users.
Bugs of documents and files are reshaped for the fitness of the elements for all humans. https://www.nspgov.in/ for NSP Help
(In reply to Rob Snelders from comment #4) > Is duplicate of 114708 This is highly unlikely (or in fact, completely impossible), that this bug (reported for non-Python extensions) is a dupe of bug 114708 (or bug 150982). It may be fixed independently, though.
Separate, and still reproducible.
https://gerrit.libreoffice.org/c/core/+/194066
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5028a5f7564b8a2d8df626feb1a6a85ee8a65db3 tdf#80959: fix percent character escaping in dp_misc::(en|de)codeString It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-25-8": https://git.libreoffice.org/core/commit/fd7facf439be9e0f0e464205343c13cb5a68268f tdf#80959: fix percent character escaping in dp_misc::(en|de)codeString It will be available in 25.8.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.