abrt version: 1.1.14
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc file:///home/lbrenta/.evolution/cache/tmp/evolution-lbrenta-wUZko2/fecha_DDJJ_por_envios_mulat.xls
reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
Created attachment 476402 [details]
*** Bug 633633 has been marked as a duplicate of this bug. ***
What were you doing when the crash happened?
#3 has a this of 0, #4 has a dereference of mpBase followed later on with a check to see if mpBase is NULL.
Could hazard a band-aid fix based on that.
bandaid will be in >= 3.2.0-12.36 if we do another update for F-13
libreoffice-188.8.131.52-1.fc15 has been submitted as an update for Fedora 15.
libreoffice-184.108.40.206-1.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update libreoffice'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/libreoffice-220.127.116.11-1.fc15
*** Bug 680128 has been marked as a duplicate of this bug. ***
*** Bug 680240 has been marked as a duplicate of this bug. ***
Strangely large number of test recently. This "fix" here is only a local bandaid to the immediate place it crashes, is anyone able to provide a sure-fire route to reproduce this crash in order to get a real fix ?
*** Bug 680957 has been marked as a duplicate of this bug. ***
* should fix your issue,
* was pushed to the Fedora 15 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-18.104.22.168-3.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
libreoffice-22.214.171.124-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.