libreoffice writer crashes after clicking on formula SIGSEGV

[thake]

Libreoffice writer crashes after clicking repeatingly on formulas. Unfortunately I can't tell how to exactly reproduce the issue, as it feels non deterministic for me.

The following steps are the basic steps to be able to reproduce it:
1. Open the attached ODF-Document
2. Insert a new Formula at the end of the document (e.g. "ABC")
3. Leave the formula editor by clicking in the text
4. Perform the following steps until it crashes
    - Double / Multiple click on an already existing formula (not the created formula)
    - Click in the text to leave the formula editor
5. libreoffice writer crashes with a core dump (SIGSEGV)

I'm very sorry that I can't give a more deterministic way to reproduce the issue. I will add a strace of the bug. If you need any more information, please don't hesitate to ask.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libreoffice 1:3.6.2~rc2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Tue Apr 16 09:14:36 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-05 (41 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[penalvch (penalvch)]

thake, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-dbg uno-libs3-dbg ure-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and it does nothing, you may be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/LibreOfficeBugWrangling when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs