Bug 391652 - Error when starting KDE
Summary: Error when starting KDE
Status: RESOLVED FIXED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.18.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
: 354342 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-03-10 07:20 UTC by Ilpo Kantonen
Modified: 2018-11-26 18:16 UTC (History)
3 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 Ilpo Kantonen 2018-03-10 07:20:45 UTC
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-116-generic i686
Distribution: Ubuntu 16.04.4 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I started KDE. When desktop appeared my monitor then appeared also error message too.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb38de800 (LWP 2738))]

Thread 2 (Thread 0xb3572b40 (LWP 3252)):
[KCrash Handler]
#7  0xb5cb71fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0
#8  0xb75262c2 in Baloo::Transaction::Transaction(Baloo::Database const&, Baloo::Transaction::TransactionType) () from /usr/lib/i386-linux-gnu/libKF5BalooEngine.so.5
#9  0xb75263e0 in Baloo::Transaction::Transaction(Baloo::Database*, Baloo::Transaction::TransactionType) () from /usr/lib/i386-linux-gnu/libKF5BalooEngine.so.5
#10 0x0806228f in Baloo::ModifiedFileIndexer::run() ()
#11 0xb7032be1 in QThreadPoolThread::run (this=0x8742d70) at thread/qthreadpool.cpp:93
#12 0xb703643b in QThreadPrivate::start (arg=0x8742d70) at thread/qthread_unix.cpp:331
#13 0xb6450295 in start_thread (arg=0xb3572b40) at pthread_create.c:333
#14 0xb6d0e0ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 1 (Thread 0xb38de800 (LWP 2738)):
#0  0xb77b9c31 in __kernel_vsyscall ()
#1  0xb6cd3496 in __getdents64 (fd=3, buf=buf@entry=0x876c26c "\206\vB", nbytes=32768) at ../sysdeps/unix/sysv/linux/getdents.c:160
#2  0xb6cd384c in __readdir64_r (dirp=0x876c250, entry=0x8779668, result=0x8779280) at ../sysdeps/posix/readdir_r.c:63
#3  0xb71a4356 in QFileSystemIterator::advance (this=0x8779278, fileEntry=..., metaData=...) at io/qfilesystemiterator_unix.cpp:106
#4  0xb71203a4 in QDirIteratorPrivate::advance (this=0x873a090) at io/qdiriterator.cpp:246
#5  0xb7120c01 in QDirIteratorPrivate::QDirIteratorPrivate (this=0x873a090, entry=..., nameFilters=..., filters=..., flags=..., resolveEngine=true) at io/qdiriterator.cpp:169
#6  0xb712139f in QDirIterator::QDirIterator (this=0x8629e18, path=..., filters=..., flags=...) at io/qdiriterator.cpp:422
#7  0x08068ee8 in Baloo::FilteredDirIterator::next() ()
#8  0x080764ee in KInotify::Private::_k_addWatches() ()
#9  0x08073a27 in ?? ()
#10 0xb723a270 in QMetaCallEvent::placeMetaCall (this=0x87785d8, object=0x865b088) at kernel/qobject.cpp:486
#11 0xb723e093 in QObject::event (this=0x865b088, e=0x87785d8) at kernel/qobject.cpp:1239
#12 0xb720d4ac in QCoreApplicationPrivate::notify_helper (this=0x861de18, receiver=0x865b088, event=0x87785d8) at kernel/qcoreapplication.cpp:1093
#13 0xb720d64d in QCoreApplication::notify (event=0x87785d8, receiver=0x865b088, this=0xbfe685dc) at kernel/qcoreapplication.cpp:1038
#14 QCoreApplication::notifyInternal (this=0xbfe685dc, receiver=0x865b088, event=0x87785d8) at kernel/qcoreapplication.cpp:965
#15 0xb720fd4f in QCoreApplication::sendEvent (event=0x87785d8, receiver=<optimized out>) at kernel/qcoreapplication.h:224
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x861de80) at kernel/qcoreapplication.cpp:1593
#17 0xb7210237 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1451
#18 0xb7265553 in postEventSourceDispatch (s=0x861e898) at kernel/qeventdispatcher_glib.cpp:271
#19 0xb5733ee9 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#20 0xb5734189 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0xb5734254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#22 0xb7265943 in QEventDispatcherGlib::processEvents (this=0x861dcc0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#23 0xb720a7a3 in QEventLoop::processEvents (this=0xbfe68558, flags=...) at kernel/qeventloop.cpp:128
#24 0xb720abfa in QEventLoop::exec (this=0xbfe68558, flags=...) at kernel/qeventloop.cpp:204
#25 0xb72131d5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#26 0x0805aa60 in main ()

Reported using DrKonqi
Comment 1 Dominik Haumann 2018-04-14 01:45:12 UTC
*** Bug 387104 has been marked as a duplicate of this bug. ***
Comment 2 Dominik Haumann 2018-04-14 01:45:47 UTC
*** Bug 354342 has been marked as a duplicate of this bug. ***
Comment 3 Ilpo Kantonen 2018-08-19 05:09:37 UTC
I updated my Kubuntu from 16.04.5 to 18.04. The baloo doesn't send any error messages anymore.
Comment 4 Nate Graham 2018-11-26 18:16:40 UTC
Thanks, let's call this closed since we haven't gotten any duplicates with recent versions.