Application: baloo_file_extractor (5.40.0) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.13.16-302.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: - What I was doing when the application crashed: Just after logging in after fedora boots up. Error happening after fedora boot ups/logins in Ver 26 and 27. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9cbba41900 (LWP 1483))] Thread 3 (Thread 0x7f9c9d629700 (LWP 1761)): #0 0x00007f9cb7fbc8bb in poll () from /lib64/libc.so.6 #1 0x00007f9cb3266ed9 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x00007f9cb3266fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007f9cb8e2735b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #4 0x00007f9cb8dd50ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007f9cb8c268ba in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x00007f9cba5ef479 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x00007f9cb8c2ab92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x00007f9cb6e9b609 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f9cb7fc8e6f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f9ca6d37700 (LWP 1649)): #0 0x00007f9cb7fbc8bb in poll () from /lib64/libc.so.6 #1 0x00007f9cb2beffe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x00007f9cb2bf1dda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x00007f9ca98d5a49 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x00007f9cb8c2ab92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x00007f9cb6e9b609 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f9cb7fc8e6f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f9cbba41900 (LWP 1483)): [KCrash Handler] #6 0x00007f9cb7ee669b in raise () from /lib64/libc.so.6 #7 0x00007f9cb7ee83b1 in abort () from /lib64/libc.so.6 #8 0x00007f9cba3d4b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f9cba3c9b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f9cba3cad8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f9cba3caff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f9cba3ccc24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 #13 0x00007f9cba3cfdbe in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0 #14 0x00007f9cba3d292b in mdb_put () from /lib64/liblmdb.so.0.0.0 #15 0x00007f9cbac935fc in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /lib64/libKF5BalooEngine.so.5 #16 0x00007f9cbac9f7d0 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #17 0x00007f9cbac98c62 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #18 0x0000560b7677fabc in Baloo::App::processNextFile() () #19 0x00007f9cb8e0b044 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #20 0x00007f9cb8dff8cb in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x00007f9cb9a3f6ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x00007f9cb9a46ef4 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x00007f9cb8dd6367 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x00007f9cb8e2666b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #25 0x00007f9cb8e26f39 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #26 0x00007f9cb3266bb7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x00007f9cb3266f60 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #28 0x00007f9cb3266fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x00007f9cb8e2733f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #30 0x00007f9cb8dd50ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #31 0x00007f9cb8ddd744 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #32 0x0000560b7677ea1f in main () Possible duplicates by query: bug 385187. Reported using DrKonqi
Created attachment 109378 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Happens after booting up laptop and logging in (both in Fedora 26 & 27). -- Backtrace (Reduced): #8 0x00007fecb51bdb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007fecb51b2b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007fecb51b3d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007fecb51b3ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007fecb51b5c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109392 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: login just after boot-up in Fedora 26 & 27. Have noticed that laptop load increases and system speed decreases substantially (fan increases as well) later when trying to manage & delete files that have been moved to Trash. -- Backtrace (Reduced): #8 0x00007fe30d7deb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007fe30d7d3b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007fe30d7d4d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007fe30d7d4ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007fe30d7d6c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109418 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Happens right after powering up and logging into my laptop. - Unusual behavior I noticed: When I try to restart this process the fan (and maybe the hard drive) begin running at noticably higher revs, and my laptop gets much warmer than normal operation under light processing loads. -- Backtrace (Reduced): #8 0x00007f2f6cc41b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f2f6cc36b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f2f6cc37d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f2f6cc37ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f2f6cc39c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109442 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Happens after powering up and logging into Fedora 26 & 27 on HP Envy dv7 laptop. After attempting restart of app load on system increases significantly & laptop starts heating up. -- Backtrace (Reduced): #8 0x00007feedc6b0b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007feedc6a5b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007feedc6a6d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007feedc6a8c74 in mdb_page_new () from /lib64/liblmdb.so.0.0.0 #12 0x00007feedc6a9079 in mdb_node_add () from /lib64/liblmdb.so.0.0.0
Created attachment 109482 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Just after power-up and logging in to Fedora 26 and 27. - Unusual behavior I noticed: When trying to restart app, fan & drive load increases substantially, and laptop (HP Envy dv7) heats up substantially. -- Backtrace (Reduced): #8 0x00007fea497d2b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007fea497c7b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007fea497c8d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007fea497c8ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007fea497cac24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109497 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Logging in after powering up laptop - Unusual behavior I noticed: Laptop fan and hard drive loads spike after trying to resart app, and temperature spikes on laptop soon afterward. -- Backtrace (Reduced): #8 0x00007f1c722dbb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f1c722d0b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f1c722d1d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f1c722d1ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f1c722d3c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109535 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: After powering up HP ENVY dv7 laptop and logging into Fedora 26 and 27. - Unusual behavior I noticed: When managing/deleting files in desktop Trash app, laptop fan & diskdrive increase speeds substantially & internal laptop temperature spikes to very hot, unusual levels. -- Backtrace (Reduced): #8 0x00007facde9abb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007facde9a0b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007facde9a1d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007facde9a1ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007facde9a3c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109545 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Logging in after powering up in Fedora 26 & 27 - Unusual behavior I noticed: After trying to delete files from desktop Trash app, laptop heats up substantially and Fedora performance slows down very noticiably. -- Backtrace (Reduced): #8 0x00007f8ad791bb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f8ad7910b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f8ad7911d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f8ad7913c74 in mdb_page_new () from /lib64/liblmdb.so.0.0.0 #12 0x00007f8ad7914079 in mdb_node_add () from /lib64/liblmdb.so.0.0.0
Created attachment 109582 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Happens right after powering up and logging into HP ENVY dv7 laptop in Fedora 26 and 27 - Unusual behavior I noticed: After using desktop Trash app, laptop load and temperature spikes abnormally & performance slows down substantially. -- Backtrace (Reduced): #8 0x00007f7bde3f3b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f7bde3e8b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f7bde3e9d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f7bde3e9ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f7bde3ebc24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109595 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: After powering up and logging into HP ENVY dv7 laptop - Unusual behavior I noticed: After bug is detected, system load has tendency to increase, fan speeds up, and temperature spikes abnormally at times when managing desktop Trash app. -- Backtrace (Reduced): #8 0x00007f72019fcb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f72019f1b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f72019f2d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f72019f2ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f72019f4c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 109606 [details] New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Powering up & logging into Fedora 26 & 27 laptop. Using an HP ENVY dv7 laptop. This app crash very consistently recurring at power-up/login. Have looked at trace & not sure, maybe Fedora could recommend to us removing and re-installing libraries related to this app/crash? -- Backtrace (Reduced): #8 0x00007f5e0abfbb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f5e0abf0b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f5e0abf1d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f5e0abf3c74 in mdb_page_new () from /lib64/liblmdb.so.0.0.0 #12 0x00007f5e0abf4079 in mdb_node_add () from /lib64/liblmdb.so.0.0.0
Please stop adding the same backtrace every day.
Created attachment 109620 [details] attachment-10897-0.html Hi Christoph, Will stop. Wanted to show that this bug has repeatable consistency - at least until and up to the time that someone can get around to working up a fix for it. Martin On Mon, Jan 1, 2018 at 1:03 PM, Christoph Feck <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=387672 > > --- Comment #12 from Christoph Feck <cfeck@kde.org> --- > Please stop adding the same backtrace every day. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
Created attachment 111115 [details] New crash information added by DrKonqi baloo_file_extractor (5.38.0) using Qt 5.9.2 happens after logging in -- Backtrace (Reduced): #8 0x00007fc3fd8d2b42 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007fc3fd8c7b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007fc3fd8c8d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007fc3fd8c8ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007fc3fd8cac24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 111496 [details] New crash information added by DrKonqi baloo_file_extractor (5.44.0) using Qt 5.9.4 - What I was doing when the application crashed: The system was starting, jus turning on the laptop -- Backtrace (Reduced): #8 0x00007f3d76761b22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f3d76756b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f3d76757d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f3d76757ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f3d76759c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 112858 [details] New crash information added by DrKonqi baloo_file_extractor (5.44.0) using Qt 5.9.4 - What I was doing when the application crashed: Login for the first time after boot. Fedora 27 with kde installed via "dnf install @kde-desktop". It happens every single time without exception. -- Backtrace (Reduced): #8 0x00007fd5dd8d7bf2 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007fd5dd8ccb85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007fd5dd8cddab in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007fd5dd8ce039 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007fd5dd8cfc64 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
*** Bug 394918 has been marked as a duplicate of this bug. ***
Created attachment 113167 [details] New crash information added by DrKonqi baloo_file_extractor (5.46.0) using Qt 5.9.4 - What I was doing when the application crashed: Start Fedora 27 from a cold boot. I restart the application, baloo process starts using 30% of cpu and not stopping until a new reboot. -- Backtrace (Reduced): #8 0x00007f8f0b8c3bf2 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f8f0b8b8b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f8f0b8b9dab in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f8f0b8ba039 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f8f0b8bbc64 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 113479 [details] New crash information added by DrKonqi baloo_file_extractor (5.47.0) using Qt 5.9.4 - What I was doing when the application crashed: Just starting fedora 27, kernel 4.16.15-200 -- Backtrace (Reduced): #8 0x00007f288a39fbf2 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f288a394b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f288a395dab in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f288a396039 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f288a397c64 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
Created attachment 113493 [details] New crash information added by DrKonqi baloo_file (5.47.0) using Qt 5.10.1 - What I was doing when the application crashed: On FC28 - latest as of 2018-06-21 - I logged into my machine. I'm behind a corporate proxy - which is when the crash started happening. -- Backtrace (Reduced): #8 0x00007f26b7557c62 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f26b754cb95 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f26b754de36 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f26b754e06b in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f26b754e708 in mdb_page_search () from /lib64/liblmdb.so.0.0.0
The crash happened with Fedora 27 and didn't stop happening after an upgrade to Fedora 28.
Small update and a workaround: calling `find $HOME -name \*baloo* | xargs rm -fr` (or similar) solved the issue (at least for now). I seems to work again after I had to kill KDE once because it would hang while trying to log-out (`sudo systemctl restart sddm` in a separate console). Hope this helps others.
Created attachment 113659 [details] attachment-13136-0.html Have had same issue for awhile. Found the following suggestion that solved problem: Baloo is currently disabled. To enable, please run "balooctl enable" After running "balooctl enable" problem hasn't recurred (am up to fc28 now). ref: https://bbs.archlinux.org/viewtopic.php?id=193169 On Sat, Jun 30, 2018 at 3:22 AM, Eric L. <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=387672 > > Eric L. <ewl+kde@lavar.de> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Status|UNCONFIRMED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #22 from Eric L. <ewl+kde@lavar.de> --- > Small update and a workaround: calling `find $HOME -name \*baloo* | xargs > rm > -fr` (or similar) solved the issue (at least for now). I seems to work > again > after I had to kill KDE once because it would hang while trying to log-out > (`sudo systemctl restart sddm` in a separate console). Hope this helps > others. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug.
*** Bug 396778 has been marked as a duplicate of this bug. ***
*** Bug 396801 has been marked as a duplicate of this bug. ***
I upgraded to Fedora 28 and still had the same issue. While reading comment 23, I noticed that I had baloo running but had a strange behavior when checking it status. balooctl status wasn't finishing and needed to CTRL-C. $ balooctl status Baloo File Indexer is running ^C Stopping baloo with balooctl stop and checking the status, was still showing as running. I rerun the balooctl stop, shutdown and started the computer. Then started baloo with balooctl start and I had a normal output, showing that the index as started and displaying the remaining files to index. After several shutdown/reboots, I'm no longer seeing the error on initial login.
My experience with Baloo is that it has virtually no sane error handling or database recovery mechanism. See the bug I ultimately reported yesterday: https://bugs.kde.org/show_bug.cgi?id=397255 Try deleting and rebuilding the baloo database. Preferably while logged out of KDE/Xorg, run: rm -f ~/.local/share/baloo/index* And then re-launch KDE. Adding 'only basic indexing=true' to ~/.config/baloofilerc may mitigate further issues. Once the baloo database gets corrupt once, my experience is it never recovers and needs to be rebuilt from scratch.
*** Bug 399391 has been marked as a duplicate of this bug. ***
*** Bug 399407 has been marked as a duplicate of this bug. ***
*** Bug 399492 has been marked as a duplicate of this bug. ***
Fixed in lmdb upstream and openSUSE lmdb RPMs, see 389848 for details. Please ask Fedora LMDB maintainers to cherry-pick the fix. *** This bug has been marked as a duplicate of bug 389848 ***