https://bugs.documentfoundation.org/show_bug.cgi?id=160215
Bug ID: 160215
Summary: Saving to smb share with activated backup not possible
Product: LibreOffice
Version: 7.6.5.2 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
Description:
If the option "Always create backup copy" is activated, saving to an smb share
fails.
Steps to Reproduce:
1. create a new document, whether Writer, Calc, Impress, Draw
2. saving to smb share for the first time is possible
3. saving again fails as soon as the option "Always create backup copy" is
activated.
Actual Results:
A file .odt.bak is created in the folder
`/home/$USER/.config/libreoffice/4/user/backup`, but with size 0. Saving from
the local drive or an nfs share is possible as normal.
A new file can be saved, but saving it again fails with the following message:
"Error saving document [document name]:
Error creating object.
could not create backup copy."
Expected Results:
Save the bakup file bei using smb shares.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Some information about the environment, which I have tested:
Manjaro 23.1.3
libreoffice-fresh 24.2.0-2
libreoffice-fresh-de 24.2.0-1
samba 4.19.5-1
manjaro-settings-samba 20220924-1
cifs-utils 7.0-3
Kernel: x86_64 Linux 6.6.19-1-MANJARO
Arch Linux
libreoffice-fresh-de 24.2.1-1
libreoffice-fresh 24.2.1-3
samba 4.19.5-1
cifs-utils 7.0-3
Kernel: x86_64 Linux 6.7.9-arch1-1
Kali Linux 2024.1
libreoffice 4:24.2.0-1
samba 2:4.19.5+dfsg-1
cifs-utils 2:7.0-2
Kernel: x86_64 Linux 6.6.9-amd64
Also testet with Manjaro:
libreoffice-still 7.6.5-1
libreoffice-still-de 7.6.5-1
By using the version 7.6.5 and resetting the profile, there is the default
setting for the option "Always create backup copy" is inactive, so there are no
probolems. But if this option is activated, there are same problem as in
version 24.1.x
I've only tested on x86_64 hardware
--
You are receiving this mail because:
You are the assignee for the bug.
