abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 36159 bytes cmdline: recoll component: recoll Attached file: coredump, 570671104 bytes crash_function: operator new executable: /usr/bin/recoll kernel: 2.6.35.14-106.fc14.i686.PAE package: recoll-1.16.1-2.fc14 rating: 4 reason: Process /usr/bin/recoll was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1347179868 uid: 500 How to reproduce ----- 1. updating the index of recoll 2. 3.
Created attachment 611168 [details] File: backtrace
Thanks for your report. You are running a old version of Fedora and recoll. There were several crash reports from recoll 1.16.1. These seems to have been fixed in recoll 1.17.3, this version in available Fedora 17, which is the recommended Fedora release at the moment. Please consider to upgrade your OS installation to this release.
recoll-1.18.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/recoll-1.18.1-1.fc16
recoll-1.18.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/recoll-1.18.1-1.fc18
recoll-1.18.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/recoll-1.18.1-1.fc17
Package recoll-1.18.1-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing recoll-1.18.1-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18539/recoll-1.18.1-1.fc16 then log in and leave karma (feedback).
recoll-1.18.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
recoll-1.18.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
recoll-1.18.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.