Error saving the document xxx: Error creating object. Could not create backup copy.

English
#1

Error saving the document xxx: Error creating object. Could not create backup copy. I get this error after upgrading from LO6 to LO7. I get the error when trying to save any document located on a shared drive. I am running Linux Mint 19.3. When I search the archives I find a similar problem marked: Closed for the following reason the question is answered, right answer was accepted by Alex Kemp close date 2020-10-12 16:37:49.826910

All of my directory paths are correct and the lock file does not exist in the backup directory.

#2

on a shared drive

“Shared” from which type of service (NFS, SAMBA Server, Windows Server using native SMB/CIFS, or any cloud service using there own proprietary connections)

#3

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.

#4

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).
#5

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

#6

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

#7

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.

#8

So Windows Defender Firewall will recognise LO7 as being the same program as LO6?

#9

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

#10

//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=?

Unable to save document on mounted samba shares
#11

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.

#12

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).

#13

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.

#14

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?

#15

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. :wink:

#16

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?).

#17

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. :slight_smile:

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. :wink:

#18

Ok - got it.

#19

Accepted work around from Opaque. File locking disabled in from Advanced settings. This issue can be marked as closed. Thanks to all who responded.

#20

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

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.