Bug 78070

is this bug document specific or does it happen with any document?

I don't see this issue under Win7x64 using 4.2.3.3

The Problem occured using Libre Office on Ubuntu 14.04, we do not know, if it will occur on win7-Machines.

sorry, i forgot to answer the main question....  :-(

The problem occurs with any document we used.
It also seems only to happen, when doc-files are saved.
I just tried to reproduce the problem with odt-files, but it did not occur.
I

Not reproducible for me with version 4.2.5.0.0+ under Ubuntu 14.04 x86-64.
Not reproducible with Ubuntu version 4.2.3.3 under Ubuntu 14.04 x86-64.

Best regards. JBF

@Cornelius Arendt  
please upload a simple test file where you see the bug with easy steps to reproduce.

Created attachment 98215 [details]
example for a doc-file that can not be saved

Whatever i change in this file can not be saved without the former mentioned error message.

NetzspeicherCorny is a NAS.
------------------------------
Fehler beim Speichern des Dokumentes The problem 2:
Allgemeiner Ein-/Ausgabefehler beim Zugriff auf /home/corny/NetzspeicherCorny/Finanzielles/Steuer/2013/The problem 2.doc.
------------------------------------

I was convinced, that the problem occured even if I saved the file in other places (e.g. local machine). But now i can not reproduce the error when saving on local machine, but it always occures when saving to my NAS.
May the NAS itself be the problem?
If so, i have to apologize! You are definately not "my personal hardware error team". I promise to systematically test any possible reason before i consume your time again.

Now I will check, if possible, if the error is on the NAS.
The NAS runs on a debian linux (as far as i know).
Perhaps there is a "selftest"-function.

This case is closed, there is evidence, that LibreOffice is not the source of the problem.

P.S.
I use ubuntu since 09.04 and i was always pleased with it. This is great Software. Before LibreOffice occured, i used openoffice even on the Windows machines (from the children and the neighbours). Today its all LibreOffice.
You all do a very good work. Thanks a lot fos this.

Did you try to save your file without space in its name? For example The_problem_2.doc instead of The problem 2.doc ?

Best regards. JBF

Thanks for this idea (the space). I did copy my file (by Nautilus) to file The_Problem_2.doc, but same results with libre office came up.
I even tried it with the file (The_Problem_2.doc) in the root of that NAS-drive.
The NAS-Drives name is written without space. The drive is called corny and mounted in ...\corny\NetzspeicherCorny. All in all no space left, but still the same thing occurs.
Other applications like gnome commander, gimp etc are not reporting problems while writing to the same directory (on the NAS drive). All of their files are perfectly Ok.
The Libre Office for Windows (dowloaded and installed yesterday) is able to write the file (The_Problem_2.doc and (The Problem 2.doc) to the NAS.

I am puzzled... :-(

The windows i tested libre office on, was a windows 7 machine (from my neighbours).

(In reply to comment #6)
> Created attachment 98215 [details]
> example for a doc-file that can not be saved
> 
> Whatever i change in this file can not be saved without the former mentioned
> error message.
> 

I can edit and save that .doc file with no issue with LibO 4.2.3.3 under Win7x64.
maybe issue is Linux specific.

Created attachment 98228 [details]
another odt-document that produces error, when saved as doc-file

Document created on other machine. When converted to doc-file (by libre office) the error occurs.

Created attachment 98230 [details]
corrupted doc-file

Hello
this is the ciorrupted doc-file mentioned above.

I am using ubuntu 14.04 with libreoffice 4.2.3.3 => error.
I tried libre office on win7 => no errors.

I made several tests, now i am sure:
It happens when
1. a odt-file was created and saved. 
2. Libre office closed.
3. open document by doubleclick from nautilus or gnome commander
4. change something in te document.
5. Save as doc-file. sometimes still no error. sometimes error.
6. change something again.
7. Save => now the error occurs definitally.

I send you a document (xanten.odt), that i just got by E-Mail from a friend.
It is a text about the city xanten in germany (it does not matter).
I saved it as doc-file and got the error message immediatly.
Although Libre office wrote an doc-file but this is corrupted!
The containment of the file xanten.doc beginns with the lines between the "zero-Lines".

00000000000000000000000000000000000000
��#ࡱ#�################;###��	#################A
##################����########�#######################################	###
#######

0000000000000000000000000000000000000

I append the corrupted file to.

Messages were in wrong order.

1. cretae odt-file (xanten.odt).
2. save as doc-file (xanten.doc).
=> error.
Both files appended above.

I tried directly create as doc-file. => No error in any case.

Ok I change again summary notes to better reflect the actual bug scenario.

anyway I still see no issue with your new test files under Win7x64

the .odt can be edited and saved with no error or corruption in .doc format.

anyway the corrupted .doc you uploaded looks corrupted on my PC as well

Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


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


Warm Regards,
QA Team

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO