Description of problem: Version-Release number of selected component: baloo-file-4.14.1-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/baloo_file --nocrashhandler crash_function: std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= executable: /usr/bin/baloo_file kernel: 3.16.3-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1035 Truncated backtrace: Thread no. 1 (8 frames) #0 std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= at /usr/include/c++/4.8.3/bits/vector.tcc:161 #1 Xapian::Database::Database at api/omdatabase.cc:82 #2 Xapian::Enquire::Internal::Internal at api/omenquire.cc:621 #3 Xapian::Enquire::Enquire at api/omenquire.cc:874 #4 Baloo::FileIndexingQueue::fillQueue at /usr/src/debug/baloo-4.14.1/src/file/fileindexingqueue.cpp:56 #5 Baloo::IndexingQueue::resume at /usr/src/debug/baloo-4.14.1/src/file/indexingqueue.cpp:56 #6 Baloo::IndexScheduler::IndexScheduler at /usr/src/debug/baloo-4.14.1/src/file/indexscheduler.cpp:82 #7 Baloo::FileIndexer::FileIndexer at /usr/src/debug/baloo-4.14.1/src/file/fileindexer.cpp:41
Created attachment 945082 [details] File: backtrace
Created attachment 945083 [details] File: cgroup
Created attachment 945084 [details] File: core_backtrace
Created attachment 945085 [details] File: dso_list
Created attachment 945086 [details] File: environ
Created attachment 945087 [details] File: exploitable
Created attachment 945088 [details] File: limits
Created attachment 945089 [details] File: maps
Created attachment 945090 [details] File: open_fds
Created attachment 945091 [details] File: proc_pid_status
Created attachment 945092 [details] File: var_log_messages
This is happening on every login on one of our machines. NFS home directory.
*** Bug 1176338 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.