Ask Your Question

Bug 60769 is back in Build 410m0(Build:4) [closed]

asked 2013-07-26 22:40:31 +0200

DickWiley gravatar image

updated 2015-11-04 15:53:34 +0200

Alex Kemp gravatar image

When saving a file as .odt I get the error message: Error in writing sub-document content.xml. LibO quits, and the file cannot be recovered (it is apparently corrupt). It also appears to have trouble saving the file as .doc ( the saved file is very small and appears to contain garbage).

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by Alex Kemp
close date 2015-11-04 15:54:01.022612


What operating system are you using? Are you saving over a network? Does your document have comments?

oweng gravatar imageoweng ( 2013-07-27 10:29:35 +0200 )edit

Sorry, I thought that was in the message. Kubuntu (Ubuntu 12.04.2.LTS) Linux Kernel 3.2.0-49 x86-64, KDE 4.8.5(4.8.5), LibO Build ID: 410m0(Build: 4). I am not saving over a network and the document has no comments.

DickWiley gravatar imageDickWiley ( 2013-07-27 18:04:18 +0200 )edit

I removed and re-installed LibO and it seemed to work OK util I tried to save a large file (~2.1 Mb). Then I got the error: Error saving the document xx: Write Error. Error in writing sub-document styles.xml.

DickWiley gravatar imageDickWiley ( 2013-07-28 00:19:19 +0200 )edit

If you are not using comments then it is likely a different bug throwing the same error message. Bug fdo#60769 is specifically related to comments causing the problem, as are duplicates fdo#60997 and fdo#61033. Can you run a backtrace (`$ soffice --backtrace`) and attach the `gdb.log` to your question? That will help provide further detail about what is going on. This is a critical issue, so we may need to open a new bug.

oweng gravatar imageoweng ( 2013-07-28 01:58:19 +0200 )edit

I tried another test this morning and something different happened. I was attempting to save a file "Darwin's World" as a .odt file from Writer. The save appeared to be going normally, but then LibO went away, leaving the lock file in the directory, but the file itself was not there. I have the backtrace log but don't know how to attach it to this comment. I can also send the file I started with.

DickWiley gravatar imageDickWiley ( 2013-07-28 17:47:08 +0200 )edit

Either edit your original question and add the detail to the end or simply post an answer below with the detail. Your experience is really not sounding good. LO should not be behaving like that. Please post the new detail so we can raise a bug (if required) with the required detail. Thanks.

oweng gravatar imageoweng ( 2013-07-29 11:51:13 +0200 )edit

1 Answer

Sort by » oldest newest most voted

answered 2013-07-29 15:47:59 +0200

DickWiley gravatar image

updated 2013-07-30 03:09:26 +0200

oweng gravatar image

Here are the details: I was attempting to save a file "Darwin's World" as a .odt file from Writer. The save appeared to be going normally, but then LibO went away, leaving the lock file in the directory, but the file itself was not there. During the backtrace process, after the "log will be saved" message, LibO Writer came back up with a recovery message. I said recover and the recovery failed. I then got a message that the file was corrupt and could not be recovered. When I ended LibO the log save process completed with additional messages. The file I was trying to save is about 2.1 Mb in size.

dickwadm@dickwHP-laptop:~$ soffice --backtrace
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <<a href=""></a>>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<<a href="">>..</a>.
Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging symbols found)...done.
log will be saved as gdbtrace.log, this will take some time, patience...
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x1e002ae
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x1e002ae

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 ...
edit flag offensive delete link more


Thanks. I can't see anything obvious, but that probably does not mean much. I am worried by the inconsistent nature of the problems you are experiencing. You problem is going to have to be repeatable (usually a problem install, environment, configuration, or document) in order for others to verify the issue. Even so, all I can suggest is reporting the bug ( ), including your logs and files, and linking to fdo#60769 if you are still getting that error.

oweng gravatar imageoweng ( 2013-07-30 03:25:48 +0200 )edit

I was afraid of that. I get different errors at different times. I'm not at all sure what is going on, but it doesn't seem to be repeatable most of the time.

DickWiley gravatar imageDickWiley ( 2013-07-30 06:56:34 +0200 )edit

Check your hardware (memory and HDD mainly) and verify your install download using the provided checksums (the small *Info* link on the large green download button) to ensure everything is OK. If everything appears to check out OK, please do raise a bug. It may be that your OS install has problems, in which case a re-install may be in order.

oweng gravatar imageoweng ( 2013-07-30 07:43:26 +0200 )edit

Question Tools

1 follower


Asked: 2013-07-26 22:40:31 +0200

Seen: 259 times

Last updated: Jul 30 '13