Bug 455434 - (SIGABRT) Baloo crashes on login
Summary: (SIGABRT) Baloo crashes on login
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.94.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-16 18:37 UTC by postix
Modified: 2023-05-17 16:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-06-16 18:37:50 UTC
SUMMARY

```
Thread 4 (Thread 0x7f90e9e77640 (LWP 2073)):
warning: Section `.reg-xstate/2073' in core file too small.
#0  0x00007f90ef0f73a1 in pselect () from /lib64/libc.so.6
#1  0x00007f90ed997b2f in ?? () from /lib64/libusbmuxd-2.0.so.6
#2  0x00007f90ed9987c3 in ?? () from /lib64/libusbmuxd-2.0.so.6
#3  0x00007f90ef077777 in start_thread () from /lib64/libc.so.6
#4  0x00007f90ef101c10 in clone3 () from /lib64/libc.so.6

Thread 3 (Thread 0x7f90e9624640 (LWP 2479)):
warning: Section `.reg-xstate/2479' in core file too small.
#0  0x00007f90ef0f45ef in poll () from /lib64/libc.so.6
#1  0x00007f90efc00108 in poll (__timeout=1000, __nfds=1, __fds=0x7f90e9621620) at /usr/include/bits/poll2.h:39
#2  pollDrKonqiSocket (sockfd=3, pid=3105) at /usr/src/debug/kcrash-5.94.0-1.1.x86_64/src/kcrash.cpp:865
#3  KCrash::startProcess (argv=argv@entry=0x7f90e9621758, waitAndExit=waitAndExit@entry=true, argc=<optimized out>) at /usr/src/debug/kcrash-5.94.0-1.1.x86_64/src/kcrash.cpp:727
#4  0x00007f90efc00d18 in KCrash::defaultCrashHandler (sig=6) at /usr/src/debug/kcrash-5.94.0-1.1.x86_64/src/kcrash.cpp:623
#5  <signal handler called>
#6  0x00007f90ef0796bc in __pthread_kill_implementation () from /lib64/libc.so.6
#7  0x00007f90ef0266f6 in raise () from /lib64/libc.so.6
#8  0x00007f90ef00f814 in abort () from /lib64/libc.so.6
#9  0x00007f90ee4d0263 in ?? ()
#10 0x00007f90ee4c27f5 in ?? () from /lib64/liblmdb-0.9.29.so
#11 0x00007f90ee4cd4e6 in ?? () from /lib64/liblmdb-0.9.29.so
#12 0x00007f90ee4c494b in ?? () from /lib64/liblmdb-0.9.29.so
#13 0x00007f90ee4c66dc in ?? () from /lib64/liblmdb-0.9.29.so
#14 0x00007f90ee4ca709 in mdb_cursor_del () from /lib64/liblmdb-0.9.29.so
#15 0x00007f90ee4cbf34 in ?? () from /lib64/liblmdb-0.9.29.so
#16 0x00007f90efae5459 in Baloo::MTimeDB::del(unsigned int, unsigned long long) () from /lib64/libKF5BalooEngine.so.5
#17 0x00007f90efaf62e0 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /lib64/libKF5BalooEngine.so.5
#18 0x0000557c3a753571 in ?? ()
#19 0x00007f90ef60c081 in QThreadPoolThread::run (this=0x557c3c114e50) at thread/qthreadpool.cpp:100
#20 0x00007f90ef608eed in QThreadPrivate::start (arg=0x557c3c114e50) at thread/qthread_unix.cpp:331
#21 0x00007f90ef077777 in start_thread () from /lib64/libc.so.6
#22 0x00007f90ef101c10 in clone3 () from /lib64/libc.so.6

Thread 2 (Thread 0x7f90ec94f940 (LWP 2064)):
warning: Section `.reg-xstate/2064' in core file too small.
#0  0x00007f90ef0f45ef in poll () from /lib64/libc.so.6
#1  0x00007f90edc471c6 in g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x557c3baf6f30, timeout=<optimized out>, context=0x557c3bad5400) at ../glib/gmain.c:4516
#2  g_main_context_iterate (context=context@entry=0x557c3bad5400, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4206
#3  0x00007f90edc472ec in g_main_context_iteration (context=0x557c3bad5400, may_block=1) at ../glib/gmain.c:4276
#4  0x00007f90ef8475a6 in QEventDispatcherGlib::processEvents (this=0x557c3bad4a80, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x00007f90ef7ee3fb in QEventLoop::exec (this=this@entry=0x7ffc849fa940, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#6  0x00007f90ef7f6566 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x0000557c3a7402d8 in ?? ()
#8  0x00007f90ef0105b0 in __libc_start_call_main () from /lib64/libc.so.6
#9  0x00007f90ef010679 in __libc_start_main_impl () from /lib64/libc.so.6
#10 0x0000557c3a740755 in ?? ()

Thread 1 (Thread 0x7f90ea97a640 (LWP 2072)):
#0  0x00007f90ef0796bc in __pthread_kill_implementation () from /lib64/libc.so.6
#1  0x00007f90ef0266f6 in raise () from /lib64/libc.so.6
#2  0x00007f90efc00d7e in KCrash::defaultCrashHandler (sig=6) at /usr/src/debug/kcrash-5.94.0-1.1.x86_64/src/kcrash.cpp:633
#3  <signal handler called>
#4  0x00007f90ef0796bc in __pthread_kill_implementation () from /lib64/libc.so.6
#5  0x00007f90ef0266f6 in raise () from /lib64/libc.so.6
#6  <signal handler called>
#7  0x00007f90ef0f45ef in poll () from /lib64/libc.so.6
#8  0x00007f90edc471c6 in g_main_context_poll (priority=<optimized out>, n_fds=3, fds=0x7f90e40029e0, timeout=<optimized out>, context=0x7f90e4000c30) at ../glib/gmain.c:4516
#9  g_main_context_iterate (context=context@entry=0x7f90e4000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4206
#10 0x00007f90edc472ec in g_main_context_iteration (context=0x7f90e4000c30, may_block=1) at ../glib/gmain.c:4276
#11 0x00007f90ef8475a6 in QEventDispatcherGlib::processEvents (this=0x7f90e4000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#12 0x00007f90ef7ee3fb in QEventLoop::exec (this=this@entry=0x7f90ea979b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#13 0x00007f90ef607cf7 in QThread::exec (this=this@entry=0x7f90efb94060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#14 0x00007f90efb1b267 in QDBusConnectionManager::run (this=0x7f90efb94060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179
#15 0x00007f90ef608eed in QThreadPrivate::start (arg=0x7f90efb94060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:331
#16 0x00007f90ef077777 in start_thread () from /lib64/libc.so.6
#17 0x00007f90ef101c10 in clone3 () from /lib64/libc.so.6
```

Unfortunately some debug symbols are missing.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 tagwerk19 2022-06-18 08:49:56 UTC
(In reply to postix from comment #0)
> SOFTWARE/OS VERSIONS
> Operating System: openSUSE Tumbleweed 20220613
Not related directly to the crash - but are you using Tumbleweed with BTRFS (with multiple subvols)?

Have a look at:
    https://bugs.kde.org/show_bug.cgi?id=402154#c12
and check whether you are seeing the "Device" number changing. This will overload baloo and maybe stress it to the point it fails.
Comment 2 postix 2022-06-20 18:25:35 UTC
(In reply to tagwerk19 from comment #1)
> Not related directly to the crash - but are you using Tumbleweed with BTRFS
> (with multiple subvols)?

Yes and yes.

> Have a look at:
>     https://bugs.kde.org/show_bug.cgi?id=402154#c12
> and check whether you are seeing the "Device" number changing. This will
> overload baloo and maybe stress it to the point it fails.

I tried it and it says:  

stat testfile.txt: `Devices: 0/44`
balooshow -x testfile.txt: 44

That looks fine to me.
Comment 3 tagwerk19 2022-06-21 07:22:37 UTC
(In reply to postix from comment #2)
> stat testfile.txt: `Devices: 0/44`
> balooshow -x testfile.txt: 44
Next time you reboot, have another look.

You can also see what:
    baloosearch -i filename:testfile.txt
gives you, this would be the "DocID" and filename. It would show you if Baloo had seen the file several times (with different device numbers)



I found the BTRFS mounts reappearing with different "minor" device numbers (
Comment 4 postix 2022-06-21 09:22:58 UTC
> I found the BTRFS mounts reappearing with different "minor" device numbers (
Right, after rebooting, the device number has changed from `44`  to `43`:

```
$ stat testfile.txt
File: testfile.txt
Devices: 0/43     Inode: 16577140    Links: 1
```

```
$ balooshow -x testfile.txt
fcf2740000002b 43 16577140 testfile.txt: No index information found
```
Comment 5 tagwerk19 2022-06-21 10:36:18 UTC
(In reply to postix from comment #4)
> Right, after rebooting, the device number has changed from `44`  to `43`...
You should see
    baloosearch -i filename:testfile.txt
giving results for the file when it was indexed on the "44" and the "43" Minor Devices...

... I am admittedly being sloppy with the "Minor Device Number" description, it is more properly described here:
    https://bugs.kde.org/show_bug.cgi?id=402154#c44
Comment 6 postix 2023-04-10 15:53:21 UTC
Haven't seen this again.