Hi, While updating extensions, the download progress bar in extension update window immediately goes 100%, in the background it downloads, but it does not show the progress of the download. For testing, you can try it out with the newly 2.3 update of LanguageTool. This is reproducible in OS X, have no idea about the other OSs. This was reproducible from the first LO version, therefore setting version to 3.3.0.
Can you please provide also the newest version you tested with?
Reproducible with 4.1.2.3.
@Emir San what about 4.2.x?
@tommy27, Still reproducible with 4.2.x.
would you please attach an old .oxt package so I can install it and try to update on a newer version trying to reproduce that issue?
Here are old versions of the LanguageTool extension: https://www.languagetool.org/download/ installed 2.5 under LO 4.3.0.4 OSX 10.9.4 Check for updates in extension manager find 2.6 update click "install" progress bar is at 100% immediately. Confirmed, NEW
wow the longer I look at this, the more confusing it actually is. sitting in front of a full progress bar while nothing happens, update is not finished only cancle update is possible is *very* irritation. raising importance to "normal" from minor.
** 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.0.5 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-09-03
Created attachment 123955 [details] screen capture
Hello everyone, I confirm the Extension Manager application freezes and no longer responds. But this can sometimes work, I change picture 1.6.4 install once, not grammalectre example. A report that disabling OpenCL, or Java changes nothing. libreoffice 5.1.2.1
Actually the progress bar works, but not the way you think it does. It shows the status of the whole update progress of all extensions, not the download status of an individual extension. So if you have only one extension to update, you immediately see it as 100%.
Could you please check the current behavior?
Current behaviour is affected by bug 99784
*** Bug 113206 has been marked as a duplicate of this bug. ***
(In reply to Muhammet Kara from comment #11) > Actually the progress bar works, but not the way you think it does. It shows > the status of the whole update progress of all extensions, not the download > status of an individual extension. So if you have only one extension to > update, you immediately see it as 100%. Hi Muhammet, Probably a RESOLVED NOTABUG?
Either I do not understand, or it is utterly unclear how it is meant to work. > It shows > the status of the whole update progress of all extensions, not the download > status of an individual extension. So, if you have only one extension, the whole update progress of all extensions should be the same as the update progress of that extension, shouldn't it? However, > if you have only one extension to update, you immediately see it as 100%. Why? Until you have not downloaded it, the extension is not updated. How can the progress be 100% even before the download has begun? I suspect that the logic you imply is that if you have 2 extensions to update, the application shows the bar at 50% as soon as the download of the first extension starts and at 100% as soon as the download of the second extension starts. To me, this is just confusing to the user. There are many problems 1) If the downloads are carried out in parallel, then even with 2 extensions to update the bar goes immediately to 100%. 2) Even if the two downloads are serialized, the behavior seems wrong. The bar should jump to 50% when the first extension update is installed (that is has /finished/ download) and to 100% when the second extension has /finished/ installing too. 3) Even better, the bar should track the first download, progressively growing to 50% while the first extension downloads and installs ant then progressively growing to 100% as the second extension downloads and installs. Please, do not close as RESOLVED, NOTABUG, because even if the progress bar does what it was meant to do, what it was meant to do is not consistent with what users expect from a /progress/ bar. If it cannot be fixed easily, I strongly suggesting removing the confusing bar altogether and leaving just a visual indication that the user has to wait.
Adding Heiko for UX input.
The progress bar is pointless when it has only one or two states (50%/100%). We should remove it and just show the hourglass cursor. Of course the better solution is to take the total bytes to download plus the time to install into account and have a real progress bar. But even better is to not bother the user with technical details and just inform after the upgrade has been done. By the way, the extension management could be improved on more aspects: https://design.blog.documentfoundation.org/2016/11/11/additions-to-libreoffice/
> The progress bar is pointless when it has only one or two states (50%/100%). Even worse than that. It has states that are reached /before/ the slow phase of a long-lasting action is completed rather than /after/ it, as it would be expected. > We should remove it and just show the hourglass cursor Agreed, until a better solution can be implemented. > Of course the better solution is to take the total bytes to download plus the time to install into account and have a real progress bar. Agreed. Probably the total bytes to download would be more than enough. > But even better is to not bother the user with technical details and just inform after the upgrade has been done. The issue here is that there are some extensions that are really quite large. E.g. LanguageTool is 76 MB. On a slow connection their download can take several minutes. Hence, some form of visual feedback that something is going on is really needed.
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
There were changes, this should be retested with current LO.
Dear Emir Sarı, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug