Problem description: <http://extensions.libreoffice.org/extension-center/mri-uno-object-inspection-tool/releases/1.1.4/mri-1-1-4.oxt> is some junk HTML content misleadingly named with an ".oxt" extension. Stephan described this problem in another bug: https://bugzilla.redhat.com/show_bug.cgi?id=966796. Steps to reproduce: 1. Download extension 3. Try to install extension. Current behavior: Installs blank extension that does nothing. Expected behavior: The extension shall be successfuly installed. (As with previous version 1.1.2). Operating System: All Version: 4.0.4.2 release
Pzemek: http://extensions.services.openoffice.org/fr/node/201/releases shows there's an 1.2.0 version but indeed, http://extensions.libreoffice.org/extension-center/mri-uno-object-inspection-tool shows only 1.1.2 Andreas: thought you might be interested in this tracker, if I'm wrong, sorry for the noise.
Thanks Julien. Przemek (In reply to comment #1) > Pzemek: http://extensions.services.openoffice.org/fr/node/201/releases shows > there's an 1.2.0 version but indeed, > http://extensions.libreoffice.org/extension-center/mri-uno-object-inspection- > tool shows only 1.1.2 > > Andreas: thought you might be interested in this tracker, if I'm wrong, > sorry for the noise.
version 1.2 of the extension installs fine, thus * adjusting title * setting to NEW. The working version of the extension in question (1.2.0) can be found here: http://extensions.services.openoffice.org/fr/node/201/releases LO Extension page lists 1.1.4 as latest release: http://extensions.libreoffice.org/extension-center/mri-uno-object-inspection-tool I can't log-in on the extension page. Also it's totally unclear how to mark extensions as broken on the extension page. This leads to the general issue that the extension management currently in total is rather flakey. Hope we can come up with a good way of dealing with this and showing very clearly to the user, which extensions do and which don't work or are in need of an update. But that would be another bug in itself I guess.
** 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 (4.4.1 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
** 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.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.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-20170522
This extension has been released on 2013-07-17, then after this bug has been reported. Both versions 1.1.2 and 1.1.4 are not empty and are real archives. They do not install on LO 5.4 (error message), but it is expected because they are said compatible with LO 3.3, 3.4 and 3.5; nothing about LO 4.x and 5.x. Seeing that an upload has been done on the extensions website after the bug report, I guess this bug is fixed. The extension works or not on current LO versions is another story. Best regards. JBF