abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault component: openoffice.org crash_function: __cxxabiv1::__cxa_pure_virtual executable: /usr/lib/openoffice.org3/program/soffice.bin kernel: 2.6.35.9-64.fc14.i686 package: openoffice.org-brand-1:3.3.0-17.2.fc14 rating: 4 reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1292230676 uid: 501 How to reproduce ----- 1. Opened a docx file 2. Open office splash screen shows 3. OO crashes
Created attachment 468322 [details] File: backtrace
Could you attach the crashing docx file here?
pure virtual. Really nasty. Would be very good if we could get the doc to reproduce this. Feel free to reopen this if you can provide something that reproduces this crash for us.
Since I am not the legal owner of the document I sent it directly to David instead of attaching it in Bugzilla. So probably should be reopened.
I'm getting a crash opening it, right, but it's the infamous atomic_exchange_and_add one (bug 659394), not this one. I don't rule out that they have both the same cause, though.
So you get some form of reproducible crash, that's good anyway. I'll pass this over to you then
probable fix checked in, will be in openoffice.org-3.3.0-19.2.fc14
openoffice.org-3.3.0-19.2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-19.2.fc14
openoffice.org-3.3.0-19.2.fc14 has been pushed to the Fedora 14 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 openoffice.org'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-19.2.fc14
openoffice.org-3.3.0-19.2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.