https://bugs.kde.org/show_bug.cgi?id=410503

            Bug ID: 410503
           Summary: Baloo crashes during boot/kde start
           Product: frameworks-baloo
           Version: 5.55.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: Baloo File Daemon
          Assignee: stefan.bru...@rwth-aachen.de
          Reporter: a14r...@att.net
  Target Milestone: ---

Application: baloo_file (5.55.0)

Qt Version: 5.9.7
Frameworks Version: 5.55.0
Operating System: Linux 4.12.14-lp151.28.10-default x86_64
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
I rebooted the computer, and the message appeared in the plasma toolbar, so I
clicked on it and got the backtrace.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe3bb9a9900 (LWP 1976))]

Thread 3 (Thread 0x7fa3abfff700 (LWP 2185)):
[KCrash Handler]
#6  0x00007fe3ba995b8d in Baloo::DocumentTimeDB::get
(this=this@entry=0x7fa3abffe9b0, docId=<optimized out>,
docId@entry=38326406953830407) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/documenttimedb.cpp:89
#7  0x00007fe3ba9a98b3 in Baloo::WriteTransaction::replaceDocument
(this=0x7fa3a4004da0, doc=..., operations=...) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/writetransaction.cpp:222
#8  0x00007fe3ba9a3bb9 in Baloo::Transaction::replaceDocument
(this=this@entry=0x7fa3abffeb20, doc=..., operations=...) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/transaction.cpp:261
#9  0x0000561be45abe75 in Baloo::UnindexedFileIndexer::run
(this=0x561be64e96b0) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/unindexedfileindexer.cpp:66
#10 0x00007fe3b9df9e22 in QThreadPoolThread::run (this=0x561be653af10) at
thread/qthreadpool.cpp:99
#11 0x00007fe3b9dfcced in QThreadPrivate::start (arg=0x561be653af10) at
thread/qthread_unix.cpp:368
#12 0x00007fe3b71f6569 in start_thread () from /lib64/libpthread.so.0
#13 0x00007fe3b93c19ef in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe3b0d96700 (LWP 1986)):
#0  0x00007fe3b93b719b in poll () from /lib64/libc.so.6
#1  0x00007fe3b57721a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe3b57722bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007fe3ba03496b in QEventDispatcherGlib::processEvents
(this=0x7fe3ac000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fe3b9fd990a in QEventLoop::exec (this=this@entry=0x7fe3b0d95c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fe3b9df7daa in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:515
#6  0x00007fe3babca9e5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007fe3b9dfcced in QThreadPrivate::start (arg=0x7fe3bae3dd60) at
thread/qthread_unix.cpp:368
#8  0x00007fe3b71f6569 in start_thread () from /lib64/libpthread.so.0
#9  0x00007fe3b93c19ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe3bb9a9900 (LWP 1976)):
#0  0x00007fe3b93b719b in poll () from /lib64/libc.so.6
#1  0x00007fe3b57721a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe3b57722bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007fe3ba03496b in QEventDispatcherGlib::processEvents
(this=0x561be648a750, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fe3b9fd990a in QEventLoop::exec (this=this@entry=0x7ffea5573460,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fe3b9fe29b4 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1297
#6  0x0000561be45a113c in main (argc=<optimized out>, argv=<optimized out>) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/main.cpp:104
[Inferior 1 (process 1976) detached]

The reporter indicates this bug may be a duplicate of or related to bug 397644.

Possible duplicates by query: bug 408810.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to