Application: baloo_file (0.1) KDE Platform Version: 4.13.0 Qt Version: 4.8.6 Operating System: Linux 3.13.0-24-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: - What I was doing when the application crashed: Starting the system after computer switch on, immediately after desktop motif appearance The crash can be reproduced every time. -- Backtrace: Application: Baloo File (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #5 std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= (this=this@entry=0xe22980, __x=...) at /usr/include/c++/4.8/bits/vector.tcc:161 #6 0x00007f8dc6fe9c7c in Xapian::Database::Database (this=0xe22978, other=...) at ../api/omdatabase.cc:82 #7 0x00007f8dc6ff3dfa in Xapian::Enquire::Internal::Internal (this=0xe22970, db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621 #8 0x00007f8dc6ff3fae in Xapian::Enquire::Enquire (this=0x7fff0b76bc30, databases=..., errorhandler=0x0) at ../api/omenquire.cc:874 #9 0x00000000004173e3 in Baloo::FileIndexingQueue::fillQueue (this=0xe1c750) at ../../../src/file/fileindexingqueue.cpp:50 #10 0x0000000000415c01 in Baloo::IndexingQueue::resume (this=0xe1c750) at ../../../src/file/indexingqueue.cpp:55 #11 0x0000000000415751 in Baloo::IndexScheduler::IndexScheduler (this=0xe1c670, db=<optimized out>, config=0x7fff0b76bf20, parent=<optimized out>) at ../../../src/file/indexscheduler.cpp:82 #12 0x000000000040f978 in Baloo::FileIndexer::FileIndexer (this=0x7fff0b76be70, db=0x7fff0b76bea0, config=0x7fff0b76bf20, parent=<optimized out>) at ../../../src/file/fileindexer.cpp:41 #13 0x00000000004090fa in main (argc=<optimized out>, argv=<optimized out>) at ../../../src/file/main.cpp:86 Reported using DrKonqi
Can you reproduce this crash if you run the baloo_file process from the terminal? If you can, could you please run it under valgrind? $ valgrind baloo_file *** This bug has been marked as a duplicate of bug 333772 ***