Bug 1435859

Summary: [abrt] kf5-baloo-file: mdb_assert_fail(): baloo_file_extractor killed by SIGABRT
Product: [Fedora] Fedora Reporter: skierpage <info>
Component: kf5-balooAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: jgrulich, kde-sig, me, rdieter, rkudyba, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ce11c9dfe72bf575eabf0bc643f04befc06c3f20
Whiteboard: abrt_hash:68e96b63d1d873fb20f0ca7cf2de4a1fc02d5fa0;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:36:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description skierpage 2017-03-25 01:45:11 UTC
Description of problem:
I had rebooted after installing 37 Fedora 25 (KDE spin) updates.
Baloo indexing was running in the background when I got the report of kf5-baloo crash.
I'm not sure what file crashed it (is there a baloo log?)
I was resizing a partition on an external SD card (not indexed?)
and had downloaded a large ZIP file, 
Journalctl had some errors from baloo, here they are with adjacent errors:

Mar 24 18:26:27 fedlaptop baloo_file[1454]: QObject::connect: invalid null parameter
Mar 24 18:26:27 fedlaptop kdeinit5[1387]: QObject::connect: invalid null parameter
Mar 24 18:26:27 fedlaptop baloo_file[1454]: QObject::connect: invalid null parameter
Mar 24 18:26:27 fedlaptop kdeinit5[1387]: QObject::connect: invalid null parameter
Mar 24 18:26:27 fedlaptop plasmashell[1461]: QFileInfo::absolutePath: Constructed with empty filename

Version-Release number of selected component:
kf5-baloo-file-5.32.0-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/baloo_file_extractor
crash_function: mdb_assert_fail
executable:     /usr/bin/baloo_file_extractor
global_pid:     2870
kernel:         4.9.14-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 mdb_assert_fail at mdb.c:1536
 #6 mdb_page_dirty at mdb.c:2121
 #7 mdb_page_alloc at mdb.c:2302
 #8 mdb_page_touch at mdb.c:2421
 #9 mdb_cursor_touch at mdb.c:6469
 #10 mdb_cursor_put at mdb.c:6603
 #11 mdb_put at mdb.c:8964
 #12 Baloo::PostingDB::put at /usr/src/debug/baloo-5.32.0/src/engine/postingdb.cpp:78
 #13 Baloo::WriteTransaction::commit at /usr/src/debug/baloo-5.32.0/src/engine/writetransaction.cpp:289
 #14 Baloo::Transaction::commit at /usr/src/debug/baloo-5.32.0/src/engine/transaction.cpp:262

Potential duplicate: bug 1270372

Comment 1 skierpage 2017-03-25 01:45:19 UTC
Created attachment 1266314 [details]
File: backtrace

Comment 2 skierpage 2017-03-25 01:45:20 UTC
Created attachment 1266315 [details]
File: cgroup

Comment 3 skierpage 2017-03-25 01:45:21 UTC
Created attachment 1266316 [details]
File: core_backtrace

Comment 4 skierpage 2017-03-25 01:45:23 UTC
Created attachment 1266317 [details]
File: dso_list

Comment 5 skierpage 2017-03-25 01:45:24 UTC
Created attachment 1266318 [details]
File: environ

Comment 6 skierpage 2017-03-25 01:45:25 UTC
Created attachment 1266319 [details]
File: limits

Comment 7 skierpage 2017-03-25 01:45:27 UTC
Created attachment 1266320 [details]
File: maps

Comment 8 skierpage 2017-03-25 01:45:29 UTC
Created attachment 1266321 [details]
File: mountinfo

Comment 9 skierpage 2017-03-25 01:45:30 UTC
Created attachment 1266322 [details]
File: namespaces

Comment 10 skierpage 2017-03-25 01:45:32 UTC
Created attachment 1266323 [details]
File: open_fds

Comment 11 skierpage 2017-03-25 01:45:33 UTC
Created attachment 1266324 [details]
File: proc_pid_status

Comment 12 skierpage 2017-03-25 01:45:34 UTC
Created attachment 1266325 [details]
File: var_log_messages

Comment 13 skierpage 2017-03-26 22:22:22 UTC
FWIW, in journalctl I noticed a message about 50 minutes later:
"Mar 24 19:14:52 fedlaptop baloo_file[1454]: Database has corrupted entries baloo may misbehave, please recreate the DB by running $ baloo
ctl disable && balooctl enable". I've done so, no errors yet.

It great if baloo_file_extractor always reported the file it is working on when it has a problem.

Comment 14 RobbieTheK 2017-05-19 18:45:06 UTC
I'm also seeing these on Fedora 25 intermittently:
May 17 08:59:32 ourserver baloo_file_extractor: failed to get the current screen resources
May 17 08:59:33 ourserver baloo_file_extractor: QObject::connect: Cannot connect (null)::resumingFromIdle() to KIdleTime::_k_resumingFromIdle()
May 17 08:59:33 ourserver baloo_file_extractor: QObject::connect: Cannot connect (null)::timeoutReached(int) to KIdleTime::_k_timeoutReached(int)
May 17 08:59:33 ourserver baloo_file_extractor: QXcbConnection: XCB error: 172 (Unknown), sequence: 169, resource id: 179, major code: 149 (Unknown), minor code: 20
May 17 08:59:36 ourserver baloo_file_extractor: "/u/ourserver/user/Mail/RMAIL" id seems to have changed. Perhaps baloo was not running, and this file was deleted + re-created
May 17 09:01:02 ourserver baloo_file: QObject::connect: invalid null parameter

So I ran:
balooctl disable && balooctl enable
May 19 14:40:58 ourserver baloo_file: QStandardPaths: wrong ownership on runtime directory /run/user/xxxx, xxxxinstead of 0
May 19 14:40:58 ourserver baloo_file: Failed to register via dbus. Another instance is running

then again:
balooctl disable && balooctl enable
QStandardPaths: wrong ownership on runtime directory /run/user/xxxx, xxxx instead of 0
Disabling the File Indexer
QStandardPaths: wrong ownership on runtime directory /run/user/xxxx, xxxx instead of 0
Enabling the File Indexer

Comment 15 Fedora End Of Life 2017-11-16 14:51:20 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 16 Fedora End Of Life 2017-12-12 10:36:32 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.