Save file as .doc fails [closed]

asked 2013-08-25 07:21:55 +0200

DickWiley gravatar image

updated 2015-10-04 22:13:38 +0200

Alex Kemp gravatar image

I encountered the following problem with Libre Office.

  1. Opened file x.odt file without problem
  2. Saved the file as x.doc
  3. Closed the file
  4. Attempted to open the file x.doc and received the following message:

Version Incompatability. Incorrect file version.

Libre Office Version:, Build ID: 410m0(Build:4)

System running Kubuntu (Ubuntu 12.04 LTS): OS Version: 3.2.0-51-generic KDE SC Version: 4.8.5(4.8.5)

Processor: Intel Celeron 900 @ 2.20Ghz

Memory: 3 Gb

Exiting and restarting Libre Office did not change the result.

This is what gdbtrace.log shows:

warning: Currently logging to gdbtrace.log.  Turn the logging off and on to make the new setting effective.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".
[New Thread 0x7fffe1a20700 (LWP 3025)]
[New Thread 0x7fffd5fc1700 (LWP 3026)]
[New Thread 0x7fffd57c0700 (LWP 3027)]
[New Thread 0x7fffcffff700 (LWP 3028)]
[New Thread 0x7fffcf1cc700 (LWP 3031)]
[Thread 0x7fffcf1cc700 (LWP 3031) exited]
[Thread 0x7fffd5fc1700 (LWP 3026) exited]
[New Thread 0x7fffd5fc1700 (LWP 3032)]
[Thread 0x7fffd5fc1700 (LWP 3032) exited]
[New Thread 0x7fffd5fc1700 (LWP 3033)]
[Thread 0x7fffd5fc1700 (LWP 3033) exited]
[New Thread 0x7fffd5fc1700 (LWP 3034)]

Program received signal SIGINT, Interrupt.
0x00007ffff3d8c313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
87  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
#0  0x00007ffff3d8c313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fffe07d9072 in ?? () from /usr/lib/libreoffice/program/
#2  0x00007ffff2039036 in ?? () from /lib/x86_64-linux-gnu/
#3  0x00007ffff2039164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/
#4  0x00007fffdf1ef3bf in QEventDispatcherGlib::processEvents (this=0x622b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007fffde5ead5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#6  0x00007fffe07d9e5a in ?? () from /usr/lib/libreoffice/program/
#7  0x00007ffff68b8301 in Application::Yield(bool) () from /usr/lib/libreoffice/program/
#8  0x00007ffff68b83b7 in Application::Execute() () from /usr/lib/libreoffice/program/
#9  0x00007ffff5c10d71 in ?? () from /usr/lib/libreoffice/program/
#10 0x00007ffff68bf7b1 in ?? () from /usr/lib/libreoffice/program/
#11 0x00007ffff68bf7d2 in SVMain() () from /usr/lib/libreoffice/program/
#12 0x00007ffff5c3e085 in soffice_main () from /usr/lib/libreoffice/program/
#13 0x000000000040067b in ?? ()
#14 0x00007ffff3cc576d in __libc_start_main (main=0x400670, argc=2, ubp_av=0x7fffffffe0f8, init=<optimized out ...
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by Alex Kemp
close date 2015-10-04 22:13:53.650391


Are you saving locally or over a network? If over a network, what kind of share are you saving to? Try saving locally (if you are not already doing so) to confirm the problem. Also, what type of content does the file contain? You may have found a bug, but an example file will be required to allow others to reproduce the problem. Can you link to an example file?

oweng gravatar imageoweng ( 2013-08-25 09:45:44 +0200 )edit

I am saving locally to a USB stick.

DickWiley gravatar imageDickWiley ( 2013-08-25 14:55:41 +0200 )edit

I just edited another file and when I tried to save it as a .odt I got: Error saving the document ~: General Error. General input/output error. And the file is trashed (went from 240.0 KiB to 4.0 KiB. LibreOffice 4.1 The file ~.odt is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. etc. Looking at the first part of the file (00 to ff), the header is corrupt. It looks OK thru byte 54 but is garbage after that. How do I sent longer messages? Via answer?

DickWiley gravatar imageDickWiley ( 2013-08-25 17:09:53 +0200 )edit

The file contains text only. Unfortunately the file is rather large. I will try to reproduce the problem with a smaller file.

DickWiley gravatar imageDickWiley ( 2013-08-25 18:25:24 +0200 )edit

Avoid saving directly to USB sticks. They are known to have problems in general. They are designed for data portability rather than as a HDD replacement. GNU/Linux in particular has recently revealed a problem with the polling of USB devices. Try repeating the problem by saving to the local HDD. A large file could have a lot of different content (markup) in it, one small element of which may be the problem.

oweng gravatar imageoweng ( 2013-08-26 02:04:59 +0200 )edit

I was just able to reproduce the problem with a smaller file. I have it all zipped up ,including the gdbtrace.log, the files involved (including hex dumps of up to 8193 bytes), and an explanation of what I did. It is about 335 KiB. It works for LibO on WinXP Media Center Edition (included). How do I get this to you? I will try what you suggest and see how that works.

DickWiley gravatar imageDickWiley ( 2013-08-26 03:48:37 +0200 )edit

I tried saving to the HDD and got the same error message, except that the file is much larger (651 KiB rather that 1.5 KiB). I have added both the .doc file and a hex dump of the first 8192 bytes to the zip file. It is now about 374 KiB. I am wondering if I should just upgrade LibO on this system to 4.1 (a mild pain but doable).

DickWiley gravatar imageDickWiley ( 2013-08-26 04:11:17 +0200 )edit

You can either edit your question to include a link to the files or post the link in a comment here. Thanks for performing the tests. If the file is being reduced dramatically in size then this is a corruption / data lost issue, and thus very serious. Bug fdo#61410 may be related. Please post a link to your file for others to test.

oweng gravatar imageoweng ( 2013-08-26 05:55:55 +0200 )edit

The zip file is at The text file Save file as doc problem.txt - explains the steps I took and has some of the information about the results. All dumps are hex/ASCII.

DickWiley gravatar imageDickWiley ( 2013-08-26 17:22:13 +0200 )edit

Thanks for providing the examples. I am not sure what is going on. I can't replicate the DOC corruption here under GNU/Linux with either v3.5.7.2 or v4.1.0.4, however my saved DOC files are ~652-653KB (i.e., about the same size as your corrupt HDD version) rather than your working 4-1Win example of ~138KB. All I can suggest you do is raise a bug and include the example files and traces.

oweng gravatar imageoweng ( 2013-08-29 02:13:08 +0200 )edit