Red Hat Bugzilla – Bug 989483
[abrt] recoll-1.19.4-2.fc19: deallocate: Process /usr/bin/recollindex was killed by signal 11 (SIGSEGV)
Last modified: 2013-11-23 23:04:35 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (8 frames)
#1 deallocate at /usr/include/c++/4.8.1/ext/new_allocator.h:110
#2 _M_deallocate at /usr/include/c++/4.8.1/bits/stl_bvector.h:479
#3 std::vector<bool, std::allocator<bool> >::_M_fill_insert at /usr/include/c++/4.8.1/bits/vector.tcc:726
#4 insert at /usr/include/c++/4.8.1/bits/stl_bvector.h:889
#5 resize at /usr/include/c++/4.8.1/bits/stl_bvector.h:923
#6 Rcl::Db::open at ../rcldb/rcldb.cpp:689
#7 ConfIndexer::createStemmingDatabases at ../index/indexer.cpp:287
#8 ConfIndexer::index at ../index/indexer.cpp:147
Potential duplicate: bug 979371
Created attachment 779758 [details]
Created attachment 779759 [details]
Created attachment 779760 [details]
Created attachment 779761 [details]
Created attachment 779762 [details]
Created attachment 779763 [details]
Created attachment 779764 [details]
Created attachment 779765 [details]
Created attachment 779766 [details]
Created attachment 779767 [details]
recoll-1.19.8-1.fc19 has been submitted as an update for Fedora 19.
recoll-1.19.8-1.fc20 has been submitted as an update for Fedora 20.
recoll-1.19.8-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing recoll-1.19.8-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
recoll-1.19.9-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
recoll-1.19.9-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
recoll-1.19.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.