Bug 195134

Summary:	WebDAV-Kioslave: File locking not working
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Pascal Mages <pascal>
Component:	WebDAV	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	adawit, kdelibs-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Pascal Mages 2009-06-03 20:07:36 UTC

Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Ubuntu Packages

I started using WebDAV recently. It has been working easily and well with one exception. When I open a file on a WebDAV resource via Dolphin it is not locked on the server. This will probably end in a parallel editing with data loss.
I assume (I don't really know what I'm taking about here), that the WebDAV implementation (it's a kioslave, right?) fails to lock the file. It's definitely not on the server side as a friend of using Vista locks the files correctly. The file actually seems to be downloaded locally before it's opened to be edited (in my case with OpenOffice).
I also tried to use the integrated OpenOffice WebDAV client, too. There I got a message that because of not fully implemented protocoll, the needs to be downloaded to a temporary, local folder. The KDE and OpenOffice WebDAV clients are two different things, I assume.
If I can provide more information, just let me know. I would be glad to help fix this.

Comment 1 momo 2010-06-18 07:10:23 UTC

Hi,

i have the same problem. Does anybody has an answer?

Comment 2 Dawit Alemayehu 2011-10-23 08:11:11 UTC

The actual code needed to lock the files is implemented in the webdav ioslave.  However since there is no easy ready-to-use API on the client side, the applications such as kate that should lock the resource do not do it. I guess I will put this on my long TODO list.

Comment 3 Dawit Alemayehu 2011-10-23 08:11:34 UTC

*** Bug 242322 has been marked as a duplicate of this bug. ***

Comment 4 Justin Zobel 2022-11-30 05:28:33 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2022-12-15 05:13:00 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2022-12-30 05:23:44 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!