Bug 81034 - CONFIGURATION: Extension update tries to lock update file
Summary: CONFIGURATION: Extension update tries to lock update file
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2014-07-08 08:32 UTC by Werner Donné
Modified: 2016-01-26 05:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Excerpt from the log that shows the LOCK request. (961 bytes, text/plain)
2014-07-08 08:32 UTC, Werner Donné

Note You need to log in before you can comment on or make changes to this bug.
Description Werner Donné 2014-07-08 08:32:58 UTC
Created attachment 102419 [details]
Excerpt from the log that shows the LOCK request.

Problem description: 

While updating extensions the user is asked to login when the ODFToEPub extension is going to be updated. This is because LibreOffice issues a WebDAV LOCK request for the extension update file, for which an anonymous user doesn't have the permission. An extension update file is read-only, so there is no reason to lock it.

This has occurred on Windows 7 and 8.1.

Steps to reproduce:
1. Install the ODFToEPub extension (http://www.pincette.biz/odftoepub/download.xhtml)
2. Do an extension update

Current behavior:

The user is requested to log in.

Expected behavior:

There should be no such request. The extension update file should be read, not locked.
Operating System: Windows 7
Version: release
Comment 1 Jean-Baptiste Faure 2014-07-23 18:46:34 UTC
No such problem with other extensions, especially with extensions from https://extensions.libreoffice.org. No such problem with Grammalecte extension which is on Dicollecte website and updated from there. So I guess the problem is on the ODFToEPub extension website.

Please, could you check if you have the same problem for other extensions?
Set status to NEEDINFO. Please, set it back to UNCONFIRMED once you have provided requested informations. 

Best regards. JBF
Comment 2 Werner Donné 2014-08-02 07:00:02 UTC
I suppose the extensions.libreoffice.org simply ignores the LOCK method. You check its access log to see if it receives such requests and what the status code is it returns.
Comment 3 Werner Donné 2014-11-03 08:47:02 UTC
Imagine a LOCK request would actually be honoured by the server. Subsequent LOCK requests by other users would then fail. It would mean users can update an extension only one at the time.
Comment 4 QA Administrators 2015-05-06 14:15:10 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 5 Jean-Baptiste Faure 2016-01-26 05:33:57 UTC
Tested again with LO No login request when I tried to update the extension.

Closing as WorksForMe. Feel free to reopen if you disagree.

Best regards. JBF