Bug 396973 - Baloo crashes on login
Summary: Baloo crashes on login
Status: RESOLVED DUPLICATE of bug 367480
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.45.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-07-30 00:29 UTC by kde-bugs
Modified: 2018-10-12 23:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.20 KB, text/plain)
2018-08-02 14:07 UTC, Georges Sancosme
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde-bugs 2018-07-30 00:29:48 UTC
Application: baloo_file (5.45.0)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.7-default x86_64
Distribution: "openSUSE Leap 15.0"

-- Information about the crash:
- What I was doing when the application crashed:
When logging into a KDE session, Baloo crashes immediately.

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 0x7fc51788e100 (LWP 3313))]

Thread 3 (Thread 0x7f8507fff700 (LWP 3389)):
[KCrash Handler]
#6  0x00007fc5152553c4 in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6
#7  0x00007fc516890a93 in memcpy (__len=2055, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f8507ffe8f7, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007fc516881f64 in Baloo::PostingDB::get (this=this@entry=0x7f8507ffe9e0, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fc51688e180 in Baloo::WriteTransaction::commit (this=0x7f85000311f0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007fc5168874c2 in Baloo::Transaction::commit (this=this@entry=0x7f8507ffeaf0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
#12 0x00005626e6ed8577 in Baloo::ModifiedFileIndexer::run (this=0x5626e7a113f0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/modifiedfileindexer.cpp:103
#13 0x00007fc515cf4372 in QThreadPoolThread::run (this=0x5626e7aa5cf0) at thread/qthreadpool.cpp:99
#14 0x00007fc515cf70ce in QThreadPrivate::start (arg=0x5626e7aa5cf0) at thread/qthread_unix.cpp:368
#15 0x00007fc514302559 in start_thread () from /lib64/libpthread.so.0
#16 0x00007fc5152ab82f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc50cfad700 (LWP 3323)):
#0  0x00007fc5152a108b in poll () from /lib64/libc.so.6
#1  0x00007fc51198a109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fc51198a21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fc515f1ac0b in QEventDispatcherGlib::processEvents (this=0x7fc508000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fc515ec309a in QEventLoop::exec (this=this@entry=0x7fc50cfacca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fc515cf24da in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515
#6  0x00007fc517137985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007fc515cf70ce in QThreadPrivate::start (arg=0x7fc5173a7d60) at thread/qthread_unix.cpp:368
#8  0x00007fc514302559 in start_thread () from /lib64/libpthread.so.0
#9  0x00007fc5152ab82f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc51788e100 (LWP 3313)):
#0  0x00007fc5152a108b in poll () from /lib64/libc.so.6
#1  0x00007fc51198a109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fc51198a21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fc515f1ac0b in QEventDispatcherGlib::processEvents (this=0x5626e7a04d60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fc515ec309a in QEventLoop::exec (this=this@entry=0x7ffdd52de7d0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fc515ecb9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289
#6  0x00005626e6ece21c in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/main.cpp:104

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

Possible duplicates by query: bug 396323, bug 396218, bug 395996, bug 394404, bug 392701.

Reported using DrKonqi
Comment 1 Georges Sancosme 2018-08-02 14:07:30 UTC
Created attachment 114269 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:
Starting Plasma5 session. The session startup takes more time to finish, leaving during almost 20s the screen with just the kde splash screen

-- Backtrace (Reduced):
#7  0x00007f38e70e6a93 in memcpy (__len=148022352, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fff0352e527, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007f38e70d7f64 in Baloo::PostingDB::get (this=this@entry=0x7fff0352e610, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007f38e70e4180 in Baloo::WriteTransaction::commit (this=0x55f108e101f0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007f38e70dd4c2 in Baloo::Transaction::commit (this=this@entry=0x7fff0352e6c0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
Comment 2 Christoph Feck 2018-08-17 21:03:15 UTC

*** This bug has been marked as a duplicate of bug 396323 ***
Comment 3 Nate Graham 2018-10-12 23:01:09 UTC

*** This bug has been marked as a duplicate of bug 394404 ***
Comment 4 Nate Graham 2018-10-12 23:03:30 UTC

*** This bug has been marked as a duplicate of bug 357206 ***
Comment 5 Nate Graham 2018-10-12 23:10:37 UTC

*** This bug has been marked as a duplicate of bug 367480 ***