https://bugs.documentfoundation.org/show_bug.cgi?id=159526

            Bug ID: 159526
           Summary: Always create backup copy problem
           Product: LibreOffice
           Version: 24.2.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
This is a new issue, it wasn't happen with 7.6.4 release.
With the option "Always create a backup copy" enabled, and if the .ods file is
in a smb share, I can't save the file.

Error message as per below:

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

Copied the file to a local folder to test, and I can save it, the problem only
happens if the file is in a smb share.

Noticed that if I mount the share using the mount option "nobrl", it solves the
issue.

I tried to change the path to the backup folder to a local folder, the same
problem happens.
Also tried to "Place backup in the same folder as document", but the same
problem happens.

Found that libreoffice creates a .bak file with 0 bytes during these attempts.

Also:
Tried to launch in Libreoffice in safe mode, didn't help.
Tried to launch using English language (LANG=C libreoffice), but didn't help.


Steps to Reproduce:
1. With the option "Always create a backup copy" enabled
2. Open a .ods file in a SMB share
3. Try to save the file

Actual Results:
Error saving the document filename:
Error creating object.
Could not create a backup copy.

Expected Results:
Expected it to save the file as usual.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Using EndeavourOS OS, system is up to date.
DE: Gnome

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: 420(Build:3)
CPU threads: 8; OS: Linux 6.7; UI render: default; VCL: gtk3
Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR
24.2.0-1
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to