[Bug 1157380] New: baloo_file coredumps on system start, every time.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380 Bug ID: 1157380 Summary: baloo_file coredumps on system start, every time. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: carlos.e.r@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 824611 --> http://bugzilla.opensuse.org/attachment.cgi?id=824611&action=edit gdb output I get this on the log: <1.7> 2019-11-18 15:52:38 Telcontar drkonqi 5475 - - Sending SIGCONT to process <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 9 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 5 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 12 and type 'Exception', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 10 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 11 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 14 and type 'Read', disabling... <3.6> 2019-11-18 15:52:39 Telcontar systemd 1 - - Created slice system-systemd\x2dcoredump.slice. <3.6> 2019-11-18 15:52:39 Telcontar systemd 1 - - Started Process Core Dump (PID 5567/UID 0). <1.2> 2019-11-18 15:52:39 Telcontar systemd-coredump 5568 - - Process 5230 (baloo_file) of user 1000 dumped core.#012#012Stack trace of thread 5464:#012#0 0x00007f2d07ea7160 __GI_raise (libc.so.6)#012#1 0x00007f2d09c4d2f7 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)#012#2 0x00007f2d07ea71e0 __restore_rt (libc.so.6)#012#3 0x00007f2d095413fb _ZN5Baloo12IdFilenameDB3getEy (libKF5BalooEngine.so.5)#012#4 0x00007f2d0953ad1f _ZNK5Baloo13DocumentUrlDB3getEy (libKF5BalooEngine.so.5)#012#5 0x00007f2d0954b734 _ZNK5Baloo11Transaction11documentUrlEy (libKF5BalooEngine.so.5)#012#6 0x00005565d084e71e n/a (baloo_file)#012#7 0x00007f2d089a1e22 n/a (libQt5Core.so.5)#012#8 0x00007f2d089a4ced n/a (libQt5Core.so.5)#012#9 0x00007f2d05d9e569 start_thread (libpthread.so.0)#012#10 0x00007f2d07f699ef __clone (libc.so.6)#012#012Stack trace of thread 5462:#012#0 0x00007f2d07f5f19b __GI___poll (libc.so.6)#012#1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0)#012#2 0x00007f2d0431a2 bc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)#012#4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)#012#5 0x00007f2d0899fdaa _ZN7QThread4execEv (libQt5Core.so.5)#012#6 0x00007f2d097729e5 n/a (libQt5DBus.so.5)#012#7 0x00007f2d089a4ced n/a (libQt5Core.so.5)#012#8 0x00007f2d05d9e569 start_thread (libpthread.so.0)#012#9 0x00007f2d07f699ef __clone (libc.so.6)#012#012Stack trace of thread 5230:#012#0 0x00007f2d07f5f19b __GI___poll (libc.so.6)#012#1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0)#012#2 0x00007f2d0431a2bc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)#012#4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)#012#5 0x00007f2 d08b8a9b4 _ZN16QCoreApplication4execEv (libQt5Core.so..5)#012#6 0x00005565d084213c n/a (baloo_file)#012#7 0x00007f2d07e91f8a __libc_start_main (libc.so.6)#012#8 0x00005565d08423aa n/a (baloo_file) Telcontar:~ # coredumpctl TIME PID UID GID SIG COREFILE EXE Mon 2019-11-18 15:52:39 CET 5230 1000 100 11 present /usr/bin/baloo_file Telcontar:~ # Telcontar:~ # coredumpctl info 5230 PID: 5230 (baloo_file) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Mon 2019-11-18 15:52:39 CET (2 days ago) Command Line: baloo_file Executable: /usr/bin/baloo_file Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (cer) Boot ID: 4735561df4ff4f7fa3d362c971e8de0d Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.baloo_file.1000.4735561df4ff4f7fa3d362c971e8de0d.5230.1574088759000000.lz4 Message: Process 5230 (baloo_file) of user 1000 dumped core. Stack trace of thread 5464: #0 0x00007f2d07ea7160 __GI_raise (libc.so.6) Telcontar:~ # Telcontar:~ # coredumpctl dump 5230 > coredumpof5230_baloo_file PID: 5230 (baloo_file) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Mon 2019-11-18 15:52:39 CET (2 days ago) Command Line: baloo_file Executable: /usr/bin/baloo_file Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (cer) Boot ID: 4735561df4ff4f7fa3d362c971e8de0d Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.baloo_file.1000.4735561df4ff4f7fa3d362c971e8de0d.5230.1574088759000000.lz4 Message: Process 5230 (baloo_file) of user 1000 dumped core. Stack trace of thread 5464: #0 0x00007f2d07ea7160 __GI_raise (libc.so.6) #1 0x00007f2d09c4d2f7 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x00007f2d07ea71e0 __restore_rt (libc.so.6) #3 0x00007f2d095413fb _ZN5Baloo12IdFilenameDB3getEy (libKF5BalooEngine.so.5) #4 0x00007f2d0953ad1f _ZNK5Baloo13DocumentUrlDB3getEy (libKF5BalooEngine.so.5) #5 0x00007f2d0954b734 _ZNK5Baloo11Transaction11documentUrlEy (libKF5BalooEngine.so.5) #6 0x00005565d084e71e n/a (baloo_file) #7 0x00007f2d089a1e22 n/a (libQt5Core.so.5) #8 0x00007f2d089a4ced n/a (libQt5Core.so.5) #9 0x00007f2d05d9e569 start_thread (libpthread.so.0) #10 0x00007f2d07f699ef __clone (libc.so.6) Stack trace of thread 5462: #0 0x00007f2d07f5f19b __GI___poll (libc.so.6) #1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0) #2 0x00007f2d0431a2bc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f2d0899fdaa _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f2d097729e5 n/a (libQt5DBus.so.5) #7 0x00007f2d089a4ced n/a (libQt5Core.so.5) #8 0x00007f2d05d9e569 start_thread (libpthread.so.0) #9 0x00007f2d07f699ef __clone (libc.so.6) Stack trace of thread 5230: #0 0x00007f2d07f5f19b __GI___poll (libc.so.6) #1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0) #2 0x00007f2d0431a2bc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f2d08b8a9b4 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #6 0x00005565d084213c n/a (baloo_file) #7 0x00007f2d07e91f8a __libc_start_main (libc.so.6) #8 0x00005565d08423aa n/a (baloo_file) Telcontar:~ # (I'll upload coredumpof5230_baloo_file if you request it) zypper install baloo5-file-debuginfo-5.55.0-lp151.2.2.x86_64 ... The following 2 NEW packages are going to be installed: baloo5-debugsource baloo5-file-debuginfo ... zypper install kfilemetadata5-debuginfo-5.55.0-lp151.1.1.x86_64 libKF5BalooEngine5-debuginfo-5.55.0-lp151.2.2.x86_64 libKF5ConfigCore5-debuginfo-5.55.0-lp151.2.5.1.x86_64 libKF5CoreAddons5-debuginfo-5.55.0-lp151.1.2.x86_64 libKF5Crash5-debuginfo-5.55.0-lp151.1.1.x86_64 libKF5I18n5-debuginfo-5.55.0-lp151.1.1.x86_64 libKF5Solid5-debuginfo-5.55.0-lp151.1.2.x86_64 libKF5WindowSystem5-debuginfo-5.55.0-lp151.1.1.x86_64 libQt5Core5-debuginfo-5.9.7-lp151.3.1.x86_64 libQt5DBus5-debuginfo-5.9.7-lp151.3.1.x86_64 libQt5Gui5-debuginfo-5.9.7-lp151.3.1.x86_64 libQt5Widgets5-debuginfo-5.9.7-lp151.3.1.x86_64 libQt5X11Extras5-debuginfo-5.9.7-lp151.1.1.x86_64 libQt5Xml5-debuginfo-5.9.7-lp151.3.1.x86_64 libdbus-1-3-debuginfo-1.12.2-lp151.4.3.1.x86_64 libdouble-conversion1-debuginfo-2.0.1-lp151.2.3.x86_64 libgraphite2-3-debuginfo-1.3.11-lp151.3.3.x86_64 liblmdb-0_9_17-debuginfo-0.9.17-lp151.4.3.1.x86_64 liblz4-1-debuginfo-1.8.0-lp151.3.3.1.x86_64 libsystemd0-debuginfo-234-lp151.26.4.1.x86_64 libtag1-debuginfo-1.11.1-lp151.4.4.x86_64 libxcb-keysyms1-debuginfo-0.4.0-lp151.2.2.x86_64 ... The following 38 NEW packages are going to be installed: dbus-1-debugsource double-conversion-debugsource graphite2-debugsource kconfig-debugsource kcoreaddons-debugsource kcrash-debugsource kfilemetadata5-debuginfo kfilemetadata5-debugsource ki18n-debugsource kwindowsystem-debugsource libKF5BalooEngine5-debuginfo libKF5ConfigCore5-debuginfo libKF5CoreAddons5-debuginfo libKF5Crash5-debuginfo libKF5I18n5-debuginfo libKF5Solid5-debuginfo libKF5WindowSystem5-debuginfo libQt5Core5-debuginfo libQt5DBus5-debuginfo libQt5Gui5-debuginfo libQt5Widgets5-debuginfo libQt5X11Extras5-debuginfo libQt5Xml5-debuginfo libdbus-1-3-debuginfo libdouble-conversion1-debuginfo libgraphite2-3-debuginfo liblmdb-0_9_17-debuginfo liblz4-1-debuginfo libqt5-qtbase-debugsource libqt5-qtx11extras-debugsource libsystemd0-debuginfo libtag1-debuginfo libxcb-keysyms1-debuginfo lmdb-debugsource lz4-debugsource solid-debugsource taglib-debugsource xcb-util-keysyms-debugsource ... 38 new packages to install. zypper install libharfbuzz0-debuginfo-1.7.5-lp151.2.3.x86_64 ... The following 2 NEW packages are going to be installed: harfbuzz-debugsource libharfbuzz0-debuginfo Telcontar:~ # coredumpctl gdb 5230 ... bt full --> attached as file -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c1
James Knott
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c2
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c4
Carlos Robinson
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c5
--- Comment #5 from Carlos Robinson
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c6
--- Comment #6 from Wolfgang Bauer
After install and restart (init 3, init 5), I get:
<1.4> 2020-01-13 11:22:49 Telcontar baloo_file 14328 - - Failed to create database, removing corrupted database. <1.4> 2020-01-13 11:22:49 Telcontar baloo_file 14328 - - Failed to create database after deleting corrupted one. But it doesn't crash anymore, right?
The crash was due to database corruption, the patch should (hopefully) fix the crash. (although, AIUI it might also help to avoid the database getting corrupted in the first place) I have no idea at the moment why it complains that it "Failed to create database after deleting corrupted one" though... But that's rather a secondary problem, I'd say.
I started nautilus, then search. I don't know if this uses baloo or something else, it does not say. Did a search, worked. No, GNOME (and nautilus therefore) uses tracker for file indexing/searching.
baloo is KDE's file indexer and would e.g. be used by dolphin (or the Plasma desktop). "balooctl status" should show the current status of the file index.
I do not see how to restart baloo indexing. On the start menu I type "baloo", get no related command "balooctl purge" should delete the database and force a reindexing, or "balooctl disable" followed by "balooctl enable".
Or delete ~/.local/share/baloo/, that should also have fixed the crash in the first place (but I wanted to know if the patch helps...). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c7
--- Comment #7 from Carlos Robinson
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c8
--- Comment #8 from Wolfgang Bauer
cer@Telcontar:~> balooctl purge Usage: balooctl [options] command status enable disable start stop restart suspend resume check index clear config monitor indexSize Yeah, that command was added in a later version. (I'm having the latest one installed here)
I noticed meanwhile that the patch ("Baloo engine: treat every non-success code as a failure") apparently caused several regressions though, that got fixed later on. E.g.: https://cgit.kde.org/baloo.git/commit/?id=7fc627bf0b5998a858ca1f7f525d9e8ef0... https://cgit.kde.org/baloo.git/commit/?id=57b9e32ff6c815e48826f92b24db22659a... Maybe one of them would fix your new problem. Although, I meanwhile wonder if it's too risky to submit a maintenance update... Leap 15.2 will have a newer version anyway, that contains all those fixes. As I wrote, deleting ~/.local/share/baloo/ should "heal" all problems of the original version. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c9
--- Comment #9 from Wolfgang Bauer
org.kde.baloo.engine: dbis is invalid Baloo Index could not be opened This certainly looks like it would be fixed by https://cgit.kde.org/baloo.git/commit/?id=57b9e32ff6c815e48826f92b24db22659a... .
I'll build a new package with that patch added. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c10
--- Comment #10 from James Knott
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c11
--- Comment #11 from Wolfgang Bauer
"But it doesn't crash anymore, right?"
I still see it regularly.
With the new testing package that I offered? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c12
--- Comment #12 from Wolfgang Bauer
org.kde.baloo.engine: dbis is invalid Baloo Index could not be opened This certainly looks like it would be fixed by https://cgit.kde.org/baloo.git/commit/ ?id=57b9e32ff6c815e48826f92b24db22659ab34782 .
I'll build a new package with that patch added.
Please try the new version from https://download.opensuse.org/repositories/home:/wolfi323:/branches:/OBS_Mai... . The other mentioned follow-up fix is not really relevant as we don't build the "experimental" code anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c13
--- Comment #13 from James Knott
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c14
--- Comment #14 from Wolfgang Bauer
No. I looked at that package and decided not to install it. Put it in a package that I can install with Yast and I'll install it. You can add the URLs given in comment#2 as repo in YaST. Then switch all available packages to that repo. (e.g. "Switch system packages to the versions in this repo" in YaST->Software Management)
But if you still are on Leap 15.0, your feedback won't be relevant anymore, as 15.0 is EOL since about 2 months and therefore no longer gets any updates. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c15
--- Comment #15 from James Knott
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c16
--- Comment #16 from Wolfgang Bauer
I'm on 15.1 on one computer and 15.0 on another.
Well, I did create testing packages for 15.1 *and* 15.0, see comment#2. Feel free to test on both versions (or not), I just won't be able to submit an update for Leap 15.0 anymore, only 15.1... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c18
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c20
--- Comment #20 from Wolfgang Bauer
cer@Telcontar:~> Failed to create database, removing corrupted database. Failed to create database after deleting corrupted one. ^C
(did not exit in hours) balooctl did exit immediately, that's why you see a prompt in the first line. The warnings come from the started background process (baloo_file, the file indexer), and were printed after balooctl exited and you got a new prompt.
The warnings go to the shell (and not the journal) in this case, as it was actually started from the shell (indirectly). If you'd have just pressed Return/Enter, you'd have gotten a new prompt as well, the ^C was a noop in this case... ;-) A general remark: It is of course possible to disable the baloo file indexer completely with the mentioned "balooctl disable" or Plasma's systemsettings->Desktop Search, or even uninstall baloo5-file. The indexer will then not be started at all on login. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com