Application: baloo_file (5.13.0) Qt Version: 5.5.0 Operating System: Linux 4.1.7-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: After entering the desktop this happened everytime. I had ever suffered the situation that this daemeon occupied 100% CPU usage, but I deleted all files associated with baloo under my home directory. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f831c407840 (LWP 1784))] Thread 2 (Thread 0x7f830647d700 (LWP 1786)): #0 0x00007f831873d2fd in poll () at /lib64/libc.so.6 #1 0x00007f8313443182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f8313444c77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f8308e46999 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f831955d54e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f83181f6555 in start_thread () at /lib64/libpthread.so.0 #6 0x00007f8318748b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f831c407840 (LWP 1784)): [KCrash Handler] #5 0x00007f83192b6f04 in mdb_reader_check () at /lib64/liblmdb.so.0.0.0 #6 0x00007f8319e23e24 in Baloo::Database::open(Baloo::Database::OpenMode) () at /lib64/libKF5BalooEngine.so.5 #7 0x000000000041397d in main () Possible duplicates by query: bug 352875. Reported using DrKonqi
confirmed dup of bug #352875 *** This bug has been marked as a duplicate of bug 352875 ***