abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 41080 bytes cmdline: /usr/lib/openoffice.org3/program/sdraw.bin -draw file:///home/yuryd/Documents/Novels/Personal_Novels/Galaxy_Child/Draft1/Book1/TheDinner.odg component: openoffice.org Attached file: coredump, 92758016 bytes crash_function: String::Assign executable: /usr/lib/openoffice.org3/program/sdraw.bin kernel: 2.6.35.11-83.fc14.i686 package: openoffice.org-draw-1:3.3.0-20.2.fc14 rating: 4 reason: Process /usr/lib/openoffice.org3/program/sdraw.bin was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1302557720 uid: 500 How to reproduce ----- 1. Open I drawing I made earlier, it crashed almost immediately upon opening, but didn't fully display the window. 2. 3.
Created attachment 491358 [details] File: backtrace
Not the typical thing to happen. Can you attach the document you were opening when this happened ?
aStr = pDocShell->GetMedium()->GetName(); maybe we can take it that there was no medium, hence the explosion
lets try that in >= 3.3.0-20.6 if we do another update for f14
libreoffice-3.3.2.2-7.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/libreoffice-3.3.2.2-7.fc15
Package libreoffice-3.3.2.2-7.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreoffice-3.3.2.2-7.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/libreoffice-3.3.2.2-7.fc15 then log in and leave karma (feedback).
libreoffice-3.3.2.2-7.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
openoffice.org-3.3.0-20.6.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-20.6.fc14
openoffice.org-3.3.0-20.6.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.