Description of problem: I was looking within Dolphin (with panels on [F11]). So, I was simply looking at the files listed in Dolphin in the home directory. Version-Release number of selected component: kf5-baloo-file-5.14.0-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/baloo_file crash_function: mdb_assert_fail executable: /usr/bin/baloo_file global_pid: 4963 kernel: 4.1.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 mdb_assert_fail at mdb.c:1347 #6 mdb_page_dirty at mdb.c:1918 #7 mdb_page_alloc at mdb.c:2099 #8 mdb_page_touch at mdb.c:2217 #9 mdb_cursor_touch at mdb.c:5956 #10 mdb_cursor_put at mdb.c:6091 #11 mdb_put at mdb.c:8242 #12 Baloo::IdTreeDB::put at ../../../src/engine/idtreedb.cpp:74 #13 replace<Baloo::WriteTransaction::removeDocument(quint64)::<lambda(quint64)> > at ../../../src/engine/documenturldb.h:102 #14 del<Baloo::WriteTransaction::removeDocument(quint64)::<lambda(quint64)> > at ../../../src/engine/documenturldb.h:53
Created attachment 1081406 [details] File: backtrace
Created attachment 1081407 [details] File: cgroup
Created attachment 1081408 [details] File: core_backtrace
Created attachment 1081409 [details] File: dso_list
Created attachment 1081410 [details] File: environ
Created attachment 1081411 [details] File: limits
Created attachment 1081412 [details] File: maps
Created attachment 1081413 [details] File: mountinfo
Created attachment 1081414 [details] File: namespaces
Created attachment 1081415 [details] File: open_fds
Created attachment 1081416 [details] File: proc_pid_status
Created attachment 1081417 [details] File: var_log_messages
*** Bug 1357536 has been marked as a duplicate of this bug. ***
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.