Bug 115333 - Extension Manager update check doesn't show available updates or shows them only after repeated check
Summary: Extension Manager update check doesn't show available updates or shows them o...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
: 118709 120019 (view as bug list)
Depends on:
Blocks: Extension-Manager
  Show dependency treegraph
Reported: 2018-01-31 14:26 UTC by Dirk Munk
Modified: 2023-11-04 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Screen dumps of update attempts. (286.63 KB, image/png)
2018-05-18 11:43 UTC, Dirk Munk

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Munk 2018-01-31 14:26:21 UTC
Check for Updates button of the extensions manager doesn't work

Steps to Reproduce:
1.Open the extensions manager
2.Click on check for updates

Actual Results:  
no updates found

Expected Results:
quite a number of updates that are available

Reproducible: Always

User Profile Reset: No

Additional Info:
When I used the "check for updates" button in the extensions manager, I got no updates. However, when I checked the extensions library, there were many new versions!

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Buovjaga 2018-02-24 12:48:41 UTC
Did you do the same steps as in bug 60226?
Comment 2 Xisco Faulí 2018-03-27 09:48:41 UTC
(In reply to Buovjaga from comment #1)
> Did you do the same steps as in bug 60226?

Dear Dirk Munk,
Could you please answer the question above?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the question has been answered
Comment 3 Timur 2018-03-28 11:17:59 UTC
Report needs to be specific, with LO version and extension names and versions. 
You must take into account compatibility versions. 
And this is not simple to test because extensions comp. is not updated. 
Probably it's an issue for specific ext. developers.

https://extensions.libreoffice.org/extensions/geomap shows comp. up to 4.1 so it's expected update doesn't work. 

In https://extensions.libreoffice.org/extensions/texmaths-1 then update check sometimes doesn't work (you must click Show all updates and then I get: An error occurred: Extra content at the end of the document. Line: 21. Column: 1) and sometimes works (offers new version) - looks like after a repeated check attempt. 

https://extensions.libreoffice.org/extensions/read-text doesn't offer an update although there's one. 
https://extensions.libreoffice.org/extensions/writer2xhtml also doesn't offer an update (from version 1.4) although there's one (v1.6). 

I tested master 6.1+ and 5.4. I set to New although it's not clear why this happens. So further testing is welcome.
Comment 4 Dirk Munk 2018-05-18 11:43:49 UTC
Created attachment 142187 [details]
Screen dumps of update attempts.

This sequential series of screendumps will show you exactly what I do, and what the result is. Hope it helps.

I'm running Libreoffice 6.04 now, latest version of Windows 10, and I'm using IPv4 and IPv6.
Comment 5 Timur 2018-05-18 15:43:28 UTC
You have:
https://extensions.libreoffice.org/extensions/alternative-dialog-find-replace-for-writer - update works from 1.4 to 1.4.2. But new check gives "General Internet error". Not clear why there's an error when there's no update to 1.4.2.

https://extensions.libreoffice.org/extensions/languagetool -  doesn't offer an update from 3.9 although there's 4.1. Error: "Premature end of data in tag html line 2 Line: 1203"

Also in my example: 
https://extensions.libreoffice.org/extensions/read-text doesn't offer an update from 0.8.34 although there's 0.8.36.
Comment 6 Timur 2018-07-17 15:55:35 UTC
*** Bug 118709 has been marked as a duplicate of this bug. ***
Comment 7 Timur 2018-09-21 12:37:29 UTC
*** Bug 120019 has been marked as a duplicate of this bug. ***
Comment 8 gordon.lack 2019-04-22 10:53:23 UTC

I was suffering from this too.

My installations (two on Kubuntu, two on Windows10) had been "stuck" on LanguageTool 3.4 for a long time. Checking for updates never reported there being one. (This resulted in me having to install an Oracle Java8 on Kubuntu, as Open-JDK11 didn't work for it).

A few days ago I noticed (by actually going to the extension web-site) that LanguageTool had actually reached 4.5.1! Installing this version cured my Java incompatibility issues.
Comment 9 Lars Jødal 2020-11-20 10:28:24 UTC
I have the same problem, noted because the dictionaries do not update. Notably, the problems seems to be independent of the LO version. Perhaps the problem is not LO but some change in the repository?

Steps to reproduce:
1. Check the extension repository for a dictionary you have installed, e.g. for English: https://extensions.libreoffice.org/en/extensions/show/english-dictionaries
2. Note version of newest available version.
3. Open LO extension manager: Tools > Extension manager
4. Check that your installed version of the dictionary is NOT the newest one.
(4a. If is IS the newest version, then manually download and install an older version, replacing the newest version in your LO installation.)
5. Click "Check for Updates".

Actual results:
Extension Update dialogue informs: "No new updates are available."

Expected results:
Extension Update dialogue should show the updated versions of the dictionary (and other extensions), giving the user the possibility to update this way.

User profile reset: Yes

Tested with the following versions:
  3.3.0 (earliest LO release) (last 3.x release) (last 4.x release) (last 5.x release) (current "still" release) (current "fresh" release) (development version)
All had out-of-date dictionaries installed (i.e., newer releases available at https://extensions.libreoffice.org/ ), but all reported "No new updates are available" when checking as described above.

For completeness, here is information on my "fresh" install:
Version: (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win
Locale: da-DK (da_DK); UI: en-GB
Calc: threaded
Comment 10 Lars Jødal 2021-11-03 07:54:09 UTC
Some further thoughts on updates of the pre-installed extensions. In short, I am beginning to think whether this should be considered a bug or a feature.

Pre-installed extensions, like relevant dictionaries, come with the installation. As noted in this thread / bug report, updates to these extensions are not found by the automatic system, even if the user actively seeks for updates of extensions.

From one perspective (my own original), this is a bug: If there is a new version of e.g. a dictionary on the official extension site, the new version should be found, so the user can install it.

From another perspective, however, it may be considered a feature: An extension that is part of the installations package may be more thoroughly tested than an updated version that is found on the extension site, but which have not (yet) become part of the installation package. In that light, it may be considered preferential that the user should manually install such updates.

In any case, it seems that manually installed updates takes preference over extensions coming with the installation package. 
The advantage of this is that if a user has installed a specific version of any extension, updating LO to a new version will not change this specific version. 
The disadvantage is that if a user has once manually installed a new version of e.g. a dictionary, then this user will not get advantage of even newer versions coming with the general package. For the individual user, this can be solved by uninstalling the manually installed extension. If there is pre-installed version of that extension "behind" the manual install, then it will appear when the manual install is removed.

Summing up: The system not finding new versions of extensions found on the official extension web site can be surprising. But it may be argued that this is the best solution, and hopefully developers working with dictionaries and other pre-installed extensions will make new (and well-tested) versions part of the standard distribution.

So perhaps this bug should be closed as RESOLVED - NOTABUG? Or what do others think?
Comment 11 QA Administrators 2023-11-04 03:14:53 UTC
Dear Dirk Munk,

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