https://bugs.freedesktop.org/show_bug.cgi?id=56544
--- Comment #8 from iveand <[email protected]> --- Maxim: thanks for the help. I did some more testing today. 3-way tests: - 1 Linux client connected to samba share via CIFS connection in fstab - 1 Linux client connected via "smb://" (gvfs) - 1 Windows XP client connected to samba share. I re-setup my samba test share, and now the file locking is working *as expected* in all regards to the "gvfs" connection. The locking is working correctly on the CIFS connection as well, but when the Windows client has a LO file open, and then attempt to open on the CIFS client, instead of the "nice error message" saying it is already opened, would I like to open read only? I instead get a "general input/output error" and the file can't be opened at all. This isn't great, but at least it will not result in multiple users editing the same file. Regarding "other file types", exclude this from the conversation for now. This is not related to LibreOffice and I may not be understanding some samba things correctly. In summary, for Ubuntu gvfs connections (12.04.3) I see *no problems* with LO's file locking methods. For cifs connections, I see a slight annoyance in the error message not displaying correctly, but I believe this to be samba related. Not sure why the gvfs connections weren't locking correctly a few days ago, but from my testing this bug seems *resolved*. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
