soffice.bin crashed with SIGSEGV in g_timeout_dispatch()

[Ante Karamatić]

I have ODT document that includes spreadsheet object from LO Calc. Editing spreadsheet works fine. But once done, if one clicks outside of the object, Writer crashes.

(an ugly) Workaround is to do the changes in the spreadsheet, save the document and then exit back to text document. Writer will crash, but changes will be saved.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libreoffice-core 1:3.6.1~rc2-1ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CheckboxSubmission: dfc057e825a9177f1e0355d98003b324
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Thu Sep 27 09:27:14 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110914)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer
[removed doc path and name] --splash-pipe=6
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/libvclplug_gtklo.so
 ?? () from /usr/lib/libreoffice/program/libvclplug_gtklo.so
 g_timeout_dispatch (source=source@entry=0x3398890, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.33.14/./glib/gmain.c:4026
 g_main_dispatch (context=0x193cf40) at /build/buildd/glib2.0-2.33.14/./glib/gmain.c:2715
 g_main_context_dispatch (context=context@entry=0x193cf40) at /build/buildd/glib2.0-2.33.14/./glib/gmain.c:3219
Title: soffice.bin crashed with SIGSEGV in g_timeout_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-09-21 (5 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

[Ante Karamatić (ivoks)]

This document can be used to reproduce the problem

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1048156, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.