I shared a Windows 10 folder and mount it with samba. This has worked without issue for many years. It has not worked in LO7 was installed. Thank you.
I shared a Windows 10 folder and mount it with samba.
Do you mean you mount it with “mount -t cifs” (samba is the server providing shares to other systems; not the client mounting from servers)?
Anyway: Did you already try what happens, if you run in LibreOffice **Safe Mode** (`Help -> Restart in Safe Mode`) and perform a test? If that works, you may face a corrupted LibreOffice user profile, which should be reset to factory settings (could be also done via `Help -> Restart in Safe Mode` and selecting the proper options in the appearing dialog).
The same error occurs when running in safe mode.
fstab contains the following entry:
//192.168.1.76/x /mnt/share/dsktp01/x cifs credentials=/root/.smbcred,uid=bill,gid=bill 0 0
Is the problem with the Windows 10 computer? Probably Defender Firewall, the second item in Windows Defender Firewall page of thegeekpage appears to address this. Cheers, Al
The problem occurs on a machine running Linux Mint 19.3. The network drive is hosted by a Windows 10 Pro computer. There have been no recent changes to the firewall. The only recent change is upgrading LO6 to LO7 on the Linux machine.
So Windows Defender Firewall will recognise LO7 as being the same program as LO6?
Here is a similar situation to yours where Defender controlled access blocked another windows computer.
Try these steps to turn off the Control Folder Access on the Windows computer and see if it fixes the issue. If it does then you know where the issue lies.
-
Select Start > Settings .
-
Choose Update & security > Windows
Defender. -
Select Open Windows Defender Security
Center. -
Select Virus & threat protection, and
then choose Virus & threat protection
settings. -
Under Controlled folder access, turn
it on or off.
Let me know how it goes
//192.168.1.76/x /mnt/share/dsktp01/x cifs credentials=/root/.smbcred,uid=bill,gid=bill 0 0
That looks pretty good , but it doesn’t force a SMB/CIFS version. What does mount | grep "//192.168.1.76/x" tell about vers=?
Opaque
//192.168.1.76/x on /mnt/share/dsktp01/x type cifs (rw,relatime,vers=3.1.1, …
IMHO this almost has to be a quirk in LO7. All other applications continue to have seamless access to the drive.
IMHO this almost has to be a quirk in LO7
May be, but almost no application known to me is using hidden lock files (i.e. .~lock<filename>#) and there were plenty of updates to Windows 10 recently. So I’d suggest to disable file locking (for testing purposes) to find the real cause (Gonna try to setup a test on my environment, though I generally use a different setup Windows getting CIFS shares from Linux, and this is no problem with version 7).
Al, thank you for your research. Since I am behind a physical firewall and the Domain is controlled by a Linux server, Windows Defender is configured as a private network. Essentially WD is turned off. This is confirmed when I check the security settings I see: “Private Network No Action Needed”.
MHO this almost has to be a quirk in LO7. All other applications continue to have seamless access to the drive.
Ok - finished my test and it works form me using Mint 20 and LibreOffice Version 7.0.3 (regardless of using Ubuntu’s PPA version or the one from libreoffice.org (TDF version). Also no problem using LibreOffice version 7.0.3 (TDF) on openSUSE 15.2.
> Could not create backup copy
What is the path setting of Tools -> Options -> LibreOffice -> Paths -> Type: Backups?
Is there a problem on the path defined for the backups?
Thank you for your persistence. After disabling file locking, I can save to the drive. Since I am retired and basically the only one using the network, I will employ this work around. BTW, there is no issue with the paths. I am running LO 7.0.3.1. When I get around to upgrading to Mint 20 I will enable and retest. I don’t expect that to happen for a while. 
After disabling file locking, I can save to the drive.
This means something must have changed on Windows not allowing to create hidden files (no longer?).
bill@nb7:~$ cd /mnt/share/dsktp01/x
bill@nb7:/mnt/share/dsktp01/x$ vi .b.txt
bill@nb7:/mnt/share/dsktp01/x$ rm .b.txt
bill@nb7:/mnt/share/dsktp01/x$ cd
bill@nb7:~$ vi /mnt/share/dsktp01/x/.b.txt
bill@nb7:~$ rm /mnt/share/dsktp01/x/.b.txt
There is no issue creating hidden files on the shared drive. 
I noted the behavior immediately after installing LO7, no Windows Updates had been applied. The issue was not present with L06 five minutes before upgrading to LO7. Don’t think I can blame Windoze this time.
Ok - got it.
Accepted work around from Opaque. File locking disabled in from Advanced settings. This issue can be marked as closed. Thanks to all who responded.
I too suffered from this bug and finally found a workaround mentioned in this 11 years old German blog article:
After adding nobrl to the /etc/fstab cifs mount, I was finally able to save libreoffice file to cifs mounted shares again. Without disabling libreoffice’s file locking completely.
2 Likes
Yep, this was the solution for me also. I kept getting “Error creating object. Could not create backup copy.” when trying to save changes to LibreOffice “*.ods” documents on my company’s Unix server, while working at my Manjaro Linux workstation. No fixes I tried worked until I found your “add nobrl to the /etc/fstab cifs mount” suggestion; that worked! According to one web page I just looked at, “nobrl” means “prevents sending byte range lock requests to the server”. That’s gibberish to me (might as well say “prevents hypervalination of the verticulated encabulator” for all the meaning it conveys to me), but hey, it works, so I suppose I shouldn’t knock it.
Windows 10, LO24.8.3.2 Experienced a corrupted file in Writer, and after that could not save existing files in Writer or Calc, although I could open new files and save them. I got this error message:
Error saving the document (File Name)
Error creating object.
Could not create backup copy
Did a factory reset in Safe Mode and it worked.