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

            Bug ID: 416197
           Summary: Baloo crash at boottup
           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: missaki...@gmail.com
  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.36-default x86_64
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
- What I was doing when the application crashed:
Baloo crashes every time I boot up my computer.
This has been going on for months now

The crash can be reproduced every time.

-- 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 0x7f9e5b259900 (LWP 1860))]

Thread 3 (Thread 0x7f5e4bdfe700 (LWP 2845)):
[KCrash Handler]
#6  Baloo::IdFilenameDB::get (this=this@entry=0x7f5e4bdfd9f0, docId=<optimized
out>, docId@entry=40550581537867780) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/idfilenamedb.cpp:96
#7  0x00007f9e5a237d1f in Baloo::DocumentUrlDB::get
(this=this@entry=0x7f5e4bdfda70, docId=docId@entry=40550581537867780) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/documenturldb.cpp:134
#8  0x00007f9e5a248734 in Baloo::Transaction::documentUrl
(this=this@entry=0x7f5e4bdfdb20, id=id@entry=40550581537867780) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/transaction.cpp:104
#9  0x0000557733cdd71e in Baloo::UnindexedFileIndexer::run
(this=0x557735f3b330) at
/usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/unindexedfileindexer.cpp:62
#10 0x00007f9e5969ee22 in QThreadPoolThread::run (this=0x557735f16d90) at
thread/qthreadpool.cpp:99
#11 0x00007f9e596a1ced in QThreadPrivate::start (arg=0x557735f16d90) at
thread/qthread_unix.cpp:368
#12 0x00007f9e56a9b569 in start_thread () from /lib64/libpthread.so.0
#13 0x00007f9e58c669ef in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f9e50853700 (LWP 1898)):
#0  0x00007f9e58c5c19b in poll () from /lib64/libc.so.6
#1  0x00007f9e550171a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f9e550172bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007f9e598d996b in QEventDispatcherGlib::processEvents
(this=0x7f9e4c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007f9e5987e90a in QEventLoop::exec (this=this@entry=0x7f9e50852c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007f9e5969cdaa in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:515
#6  0x00007f9e5a46f9e5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007f9e596a1ced in QThreadPrivate::start (arg=0x7f9e5a6e2d60) at
thread/qthread_unix.cpp:368
#8  0x00007f9e56a9b569 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f9e58c669ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f9e5b259900 (LWP 1860)):
#0  0x00007f9e58c5c19b in poll () from /lib64/libc.so.6
#1  0x00007f9e550171a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f9e550172bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007f9e598d996b in QEventDispatcherGlib::processEvents
(this=0x557735e58d80, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007f9e5987e90a in QEventLoop::exec (this=this@entry=0x7ffc631f2210,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007f9e598879b4 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1297
#6  0x0000557733cd113c 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 1860) detached]

Possible duplicates by query: bug 411842, bug 410097, bug 406378, bug 406317,
bug 406064.

Reported using DrKonqi

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

Reply via email to