Bug 137230 - Save a file to network storage trashes the content
Summary: Save a file to network storage trashes the content
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
6.4.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 137394 (view as bug list)
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2020-10-03 17:50 UTC by Uwe Altmann
Modified: 2023-11-12 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Original file (23.67 KB, application/vnd.oasis.opendocument.text)
2020-10-03 17:50 UTC, Uwe Altmann
Details
Result (trashed) file (43.46 KB, application/vnd.oasis.opendocument.text)
2020-10-03 17:53 UTC, Uwe Altmann
Details
uncorrupted file before saving on NAS (7.73 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-11-23 06:56 UTC, Thomas
Details
corrupted file after saving on NAS (11.74 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-11-23 06:57 UTC, Thomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Altmann 2020-10-03 17:50:48 UTC
Created attachment 166056 [details]
Original file

Environment: Ubuntu 20.04 (recent); LO 6.4.6 (recently for this Ubuntu version), NAS share on AVM Fritz!Box with Fritz!OS 7.20 (a popular router in Germany) using samba V2/3.

I' able to open files on the NAS directly from LO and edit them. Saving back directly (File > Save) to the NAS trashes the files content. 

Instead, saving locally and then copying the file via Ubuntu works as expected.
Using an older Version of Fritz! OS (which uses samba V1) works as expected.
Using another text editor on Ubuntu works like expected.
Using another OS (MacOS with LO 7.1 or 6.4.5) works like expected.

Drive is mounted in fstab with 
//192.168.10.1/fritz.nas/ /home/osboxes/Fritz cifs _netdev,auto,noserverino,users,user=???,password=???,uid=1000,gid=1000 0 0
Option "noserverino" is needed, otherwise accessing any file returns an error.
Comment 1 Uwe Altmann 2020-10-03 17:53:22 UTC
Created attachment 166057 [details]
Result (trashed) file
Comment 2 Thomas 2020-11-23 06:09:28 UTC
I can confirm this error, same happens with me. The NAS works flawless when accessing it from a Windows computer and Android smartphone. All other software works as expected when using the NAS (editing / saving files). 

Environment: LO 7.0.2.2
NAS share with AVM Fritz!OS 7.21 using Samba v2 / v3
Comment 3 Thomas 2020-11-23 06:56:52 UTC
Created attachment 167492 [details]
uncorrupted file before saving on NAS

uncorrupted file before saving on NAS
Comment 4 Thomas 2020-11-23 06:57:48 UTC
Created attachment 167493 [details]
corrupted file after saving on NAS

corrupted file after saving on NAS
Comment 5 Thomas 2020-11-24 06:39:34 UTC
mounting the NAS with the option "cache=none" seems to solve the problem (workaround).
Comment 6 Thomas 2020-11-24 06:42:05 UTC
*** Bug 137394 has been marked as a duplicate of this bug. ***
Comment 7 Justin L 2020-12-24 12:48:13 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2023-11-12 03:13:17 UTC
Dear Uwe Altmann,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug