Description of problem: While re-starting, after a huge updating of my Fedora18 Version-Release number of selected component: recoll-1.19.4-2.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/recollindex -w 60 -m crash_function: std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_erase executable: /usr/bin/recollindex kernel: 3.9.11-200.fc18.i686.PAE runlevel: N 5 uid: 1000 xsession_errors: :3:recollindex.cpp:371:recollindex: starting up Truncated backtrace: Thread no. 1 (10 frames) #0 std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_erase at /usr/include/c++/4.7.2/bits/stl_tree.h:1082 #5 ~_Rb_tree at /usr/include/c++/4.7.2/bits/stl_tree.h:646 #6 ~map at /usr/include/c++/4.7.2/bits/stl_map.h:90 #7 ~pair at /usr/include/c++/4.7.2/bits/stl_pair.h:88 #8 destroy at /usr/include/c++/4.7.2/ext/new_allocator.h:123 #9 _M_destroy_node at /usr/include/c++/4.7.2/bits/stl_tree.h:394 #10 std::_Rb_tree<std::string, std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > >, std::_Select1st<std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > > >, std::less<std::string>, std::allocator<std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > > > >::_M_erase at /usr/include/c++/4.7.2/bits/stl_tree.h:1084 #12 ~_Rb_tree at /usr/include/c++/4.7.2/bits/stl_tree.h:646 #13 ~map at /usr/include/c++/4.7.2/bits/stl_map.h:90 #14 ~ConfSimple at ../utils/conftree.h:143
Created attachment 785108 [details] File: backtrace
Created attachment 785109 [details] File: cgroup
Created attachment 785110 [details] File: core_backtrace
Created attachment 785111 [details] File: dso_list
Created attachment 785112 [details] File: environ
Created attachment 785113 [details] File: limits
Created attachment 785114 [details] File: maps
Created attachment 785115 [details] File: open_fds
Created attachment 785116 [details] File: proc_pid_status
Created attachment 785118 [details] File: var_log_messages
Thanks for your report, are able to reproduce? Or was this just a single crash after update?
recoll-1.19.8-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc19
recoll-1.19.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc20
recoll-1.19.8-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc18
Package recoll-1.19.8-1.fc20: * 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: https://admin.fedoraproject.org/updates/FEDORA-2013-20750/recoll-1.19.8-1.fc20 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.