abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc file:///home/rvm/Desktop/eRomania2/adresare_IP_management.ods component: openoffice.org crash_function: _gcry_ath_mutex_lock executable: /usr/lib64/openoffice.org3/program/scalc.bin kernel: 2.6.35.9-64.fc14.x86_64 package: openoffice.org-calc-1:3.3.0-17.2.fc14 rating: 3 reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1291914791 uid: 500 How to reproduce ----- 1. 2. 3. just like that
Created attachment 467803 [details] File: backtrace
"Just like that". Is hardly a "way to reproduce". This is probably loading something over http, maybe two different threads. Root cause is that cups inits gcrypt before anything else does, and inits is as non-thread safe.
Related to rhbz#637738. I guess I could extend that and try and wrap ne_simple_propfind in our "protect neon from multiple threads" mutex, which is a bit of a bodge, but should make this harder to happen. If I had a reproducer for this I could be sure I've this squashed.
Fix for this specific crash will be included >= 3.3.0-17.3.fc14
openoffice.org-3.3.0-18.1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-18.1.fc14
*** Bug 663780 has been marked as a duplicate of this bug. ***
openoffice.org-3.3.0-18.1.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-18.1.fc14
openoffice.org-3.3.0-18.2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-18.2.fc14
openoffice.org-3.3.0-18.2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.