Just installed LibreOffice 5.0.2.2 over 4.4. All went well except when I tried "Check for updates" nothing happened. I know it's a new release but I didn't even get "LibreOffice is up to date". Also, "Help" tells you how to configure automatic updates i.e. Tools>Options>LibreOffice>Online update. However, there is no "Online Update" showing in Options.
as far as I remember the update check starts working a week after the latest release is launched... Cloph can probably give a better answer.
Created attachment 119039 [details] LO 5.0.2.2 check for update dialog -- working OK in Windows Can't confirm. Dialog is working correctly on WIndows 10 Pro 64-bit with 5.0.2.1 loaded Version: 5.0.2.1 (x64) Build ID: 9a18d52abbdfbdc2ac9acebec2b92e7859eb73b7 Locale: en-US (en_US) Where Check for Updates gives "LibreOffice 5.0 is up to date" Of course that is not correct since it should offer the 5.0.2.2. But, then a download and install of 5.0.2.2 build. Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: en-US (en_US) Help -> Check for Updates opens the dialog and as expected gives the same message. Clip attached. @Cloph, does the website update "check.php" need a tweak for the 5.0.2 releases?
well - the answer is the same as always. Update-check will be enabled a few days after the release is available from the website. This is to catch feedback, esp. when there are larger changes that depend on the system configureation like for example the expanded OpenGL rendering in 5.0.2. I'll enable it when I'm back at my place this evening/night.
I have a 5.0.2.1 LibO installation and checking for updates is still not enabled to show 5.0.2.2
Created attachment 119139 [details] check for update for 5.0.2 in place signature strings are posted to the update check.php Thanks Cloph! # 5.0.2 '9a18d52abbdfbdc2ac9acebec2b92e7859eb73b7' => '5.0.2.1', '37b43f919e4de5eeaca9b9755ed688758a8251fe' => '5.0.2.2', # Final =-ref-= http://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update#n376
I am still getting no response when I click on Help>Check for updates.
read comment 3 this is intended behaviour LibO 5.0.3.2 was released on november 3rd so it's not time yet to get the udpdate notification I think that in a few days it will be enabled
(In reply to tommy27 from comment #7) > read comment 3 > this is intended behaviour > > LibO 5.0.3.2 was released on november 3rd so it's not time yet to get the > udpdate notification > I think that in a few days it will be enabled The point I am trying to make is that with 5.0.2.2 I get no response at all! 5.0.3.2 may well have been released and the update for it may well be enabled in the next few days but in the meantime why doesn't 5.0.2.2 at least tell me it is up-to-date or that no updates are available??
I have LibO 5.0.3.1 installed and today I see notification that 5.0.3.2 is available. please retest and tell if you still don't see notification from your 5.0.2.2 installation post a screenshot too if useful
@c.weyman, The 5.0.3 (.1 and .2) build IDs have been added to the check.php Web site configuration file--so unless the update is disabled (or missing) from your system--you should see the bubble window dialog. Functions correctly on Windows 10 Pro, dialog with "... is up to date" or "... is available" displays. Don't believe availability of the dialog is not dependent on --"auto" check for updates-- set during LO install, and dialog should always be available. So could be a different issue, but we'd need to know what OS and DE are you working in? =-ref-= http://opengrok.libreoffice.org/search?q=updatecheckui&project=core&defs=&refs=&path=&hist=
adding bug 95183 for those on Windows XP 32-bit
it is intentional that updates won't be made available using the update check right after release, but you're right, this time the delay was a tad too long - usually it should three or four days after the announcement (so release on Thursday, in update check on Sunday evening or Monday. So instead of the number of days delay, the Sunday/Monday rule was applied - sorry for that mismatch. So yes - if you don't see the update, please post the hash (commit-ID) that's visible in the about dialog
(In reply to Christian Lohmaier from comment #12) > it is intentional that updates won't be made available using the update > check right after release, but you're right, this time the delay was a tad > too long - usually it should three or four days after the announcement (so > release on Thursday, in update check on Sunday evening or Monday. > > So instead of the number of days delay, the Sunday/Monday rule was applied - > sorry for that mismatch. > > So yes - if you don't see the update, please post the hash (commit-ID) > that's visible in the about dialog Still no response to update request. In About LibreOffice this is showing: Version: 5.0.2.2 Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: en-GB (en_GB) Is this what you requested?
(In reply to tommy27 from comment #9) > I have LibO 5.0.3.1 installed and today I see notification that 5.0.3.2 is > available. > > please retest and tell if you still don't see notification from your 5.0.2.2 > installation > > post a screenshot too if useful There is nothing to show. Not even "Checking for updates failed"!
(In reply to c.weyman from comment #13) > > Still no response to update request. > > In About LibreOffice this is showing: > > Version: 5.0.2.2 > > Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe > Locale: en-GB (en_GB) > > Is this what you requested? Yes, but we really also need to know what operating system and if 32 or 64-bit build. Also if a Linux, which Desktop Environment
yes, that info is what I need - but I cannot reproduce. If I query the server with that commit-id, I get response that a new version is available. e.g.: $ HTTP_USER_AGENT='LibreOffice 5.0.2 (37b43f919e4de5eeaca9b9755ed688758a8251fe; Windows; X86_64; BundledLanguages=en-US af ar as ast be bg bn bo br brx bs ca ca-XV cs cy da de dgo dz el en-GB en-ZA eo es et eu fa fi fr ga gd gl gu he hi hr hu id is it ja ka kk km kn ko kok ks ku lb lo lt lv mai mk ml mn mni mr my nb ne nl nn nr nso oc om or pa-IN pl pt pt-BR ro ru rw sa-IN sat sd sh si sk sl sq sr ss st sv sw-TZ ta te tg th tn tr ts tt ug uk uz ve vi xh zh-CN zh-TW zu)' HTTP_ACCEPT_LANGUAGE=cs-CZ php ./check.php returns: <?xml version="1.0" encoding="utf-8"?> <inst:description xmlns:inst="http://update.libreoffice.org/description"> <inst:id>LibreOffice 5.0.3</inst:id> <inst:gitid>e5f16313668ac592c1bfb310f4390624e3dbfb75</inst:gitid> <inst:os>Windows</inst:os> <inst:arch>X86_64</inst:arch> <inst:version>5.0.3</inst:version> <inst:buildid>9999</inst:buildid> <inst:update type="text/html" src="http://www.libreoffice.org/download/libreoffice-fresh/?type=win-x86_64&lang=cs&version=5.0.3" /> </inst:description> so it replies that 5.0.3 is available and offers the corresponding download-link that then is displayed in the dialog. In any case: If a manually triggered check for update doesn't show anythign at all, then this is a different problem. #### Maybe the confusion is that it only checks automatically once per week? So please use Help|Check for updates to manually trigger the request.
(In reply to Christian Lohmaier from comment #16) > yes, that info is what I need - but I cannot reproduce. If I query the > server with that commit-id, I get response that a new version is available. > > e.g.: > $ HTTP_USER_AGENT='LibreOffice 5.0.2 > (37b43f919e4de5eeaca9b9755ed688758a8251fe; Windows; X86_64; > BundledLanguages=en-US af ar as ast be bg bn bo br brx bs ca ca-XV cs cy da > de dgo dz el en-GB en-ZA eo es et eu fa fi fr ga gd gl gu he hi hr hu id is > it ja ka kk km kn ko kok ks ku lb lo lt lv mai mk ml mn mni mr my nb ne nl > nn nr nso oc om or pa-IN pl pt pt-BR ro ru rw sa-IN sat sd sh si sk sl sq sr > ss st sv sw-TZ ta te tg th tn tr ts tt ug uk uz ve vi xh zh-CN zh-TW zu)' > HTTP_ACCEPT_LANGUAGE=cs-CZ php ./check.php > > returns: > > <?xml version="1.0" encoding="utf-8"?> > <inst:description xmlns:inst="http://update.libreoffice.org/description"> > <inst:id>LibreOffice 5.0.3</inst:id> > <inst:gitid>e5f16313668ac592c1bfb310f4390624e3dbfb75</inst:gitid> > <inst:os>Windows</inst:os> > <inst:arch>X86_64</inst:arch> > <inst:version>5.0.3</inst:version> > <inst:buildid>9999</inst:buildid> > <inst:update type="text/html" > src="http://www.libreoffice.org/download/libreoffice-fresh/?type=win- > x86_64&lang=cs&version=5.0.3" /> > </inst:description> > > so it replies that 5.0.3 is available and offers the corresponding > download-link that then is displayed in the dialog. > > In any case: If a manually triggered check for update doesn't show anythign > at all, then this is a different problem. > #### > Maybe the confusion is that it only checks automatically once per week? So > please use Help|Check for updates to manually trigger the request. I am already using the manual update option
(In reply to Christian Lohmaier from comment #16) > yes, that info is what I need - but I cannot reproduce. If I query the > server with that commit-id, I get response that a new version is available. > > e.g.: > $ HTTP_USER_AGENT='LibreOffice 5.0.2 > (37b43f919e4de5eeaca9b9755ed688758a8251fe; Windows; X86_64; > BundledLanguages=en-US af ar as ast be bg bn bo br brx bs ca ca-XV cs cy da > de dgo dz el en-GB en-ZA eo es et eu fa fi fr ga gd gl gu he hi hr hu id is > it ja ka kk km kn ko kok ks ku lb lo lt lv mai mk ml mn mni mr my nb ne nl > nn nr nso oc om or pa-IN pl pt pt-BR ro ru rw sa-IN sat sd sh si sk sl sq sr > ss st sv sw-TZ ta te tg th tn tr ts tt ug uk uz ve vi xh zh-CN zh-TW zu)' > HTTP_ACCEPT_LANGUAGE=cs-CZ php ./check.php > > returns: > > <?xml version="1.0" encoding="utf-8"?> > <inst:description xmlns:inst="http://update.libreoffice.org/description"> > <inst:id>LibreOffice 5.0.3</inst:id> > <inst:gitid>e5f16313668ac592c1bfb310f4390624e3dbfb75</inst:gitid> > <inst:os>Windows</inst:os> > <inst:arch>X86_64</inst:arch> > <inst:version>5.0.3</inst:version> > <inst:buildid>9999</inst:buildid> > <inst:update type="text/html" > src="http://www.libreoffice.org/download/libreoffice-fresh/?type=win- > x86_64&lang=cs&version=5.0.3" /> > </inst:description> > > so it replies that 5.0.3 is available and offers the corresponding > download-link that then is displayed in the dialog. > > In any case: If a manually triggered check for update doesn't show anythign > at all, then this is a different problem. > #### > Maybe the confusion is that it only checks automatically once per week? So > please use Help|Check for updates to manually trigger the request. Windows XP, SP3, 32-bit. I think I will do a complete uninstall of 5.0.2.2 and see how a fresh install of 5.0.3.X behaves.
(In reply to c.weyman from comment #18) > > Windows XP, SP3, 32-bit. > > I think I will do a complete uninstall of 5.0.2.2 and see how a fresh > install of 5.0.3.X behaves. Went to Add/Remove Programs and selected LO 5.0.2.2. Chose "Remove" option. Nothing. Task Manager reported "Not Responding". Had to end task. Tried "Repair" option. Same thing. Was going to use Revo Uninstaller but thought I would try the uninstall utility in Ccleaner. This seemed to work OK. I then did a search for all things LO and only a couple of empty folders in Application Data were found. Deleted these and downloaded and installed 5.0.3.2. Out of interest I did a manual "Check for updates" but was not surprised at no response because I now know it takes a few days for a new release to register. However, why can't a simple "no updates available" or "LO is up-to-date" be shown anyway? It doesn't seem right not to see any type of dialogue box when you click "Check for updates". Also, under Tools>Options I still cannot see any options for setting up an automatic update.
@c.weyman Thank you for *finally* identifying your OS as Windows XP SP3. There were two parallel issues here, the posting of build signatures to the update's landing page in LibreOffice's website infrastructure. That is a normal release cycle posting issue and as @cloph indicates has been resolved. Your issue, which yes was the opening issue here, duplicates the specific issue of bug 95183. However, going to close this out as a duplicate of tdf#95183, as that issue is specific to your situation--it is only affecting Windows XP 32-bit builds. And, this issue was rather muddled. *** This bug has been marked as a duplicate of bug 95183 ***