Bug 360024 - Application 'baloo_file' crashing
Summary: Application 'baloo_file' crashing
Status: RESOLVED DUPLICATE of bug 354705
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.19.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-03-03 13:05 UTC by Yaroslav Sidlovsky
Modified: 2016-09-11 19:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yaroslav Sidlovsky 2016-03-03 13:05:47 UTC
Application: baloo_file (5.19.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.3-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
I see this crash message every time after logging in to the KDE,
or when executing commands "balooctl start; balooctl check" in the console.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
84	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f245f4748c0 (LWP 9529))]

Thread 2 (Thread 0x7f230baa0700 (LWP 9588)):
[KCrash Handler]
#6  0x00007f245e2f684b in Baloo::IdFilenameDB::get(unsigned long long) (this=this@entry=0x7f230ba9fa30, docId=docId@entry=67554084604872722) at /usr/src/debug/baloo-5.19.0/src/engine/idfilenamedb.cpp:96
#7  0x00007f245e2f00a7 in Baloo::DocumentUrlDB::get(unsigned long long) const (this=this@entry=0x7f230ba9fab0, docId=docId@entry=67554084604872722) at /usr/src/debug/baloo-5.19.0/src/engine/documenturldb.cpp:144
#8  0x00007f245e3070a1 in Baloo::Transaction::documentUrl(unsigned long long) const (this=this@entry=0x7f230ba9fb70, id=id@entry=67554084604872722) at /usr/src/debug/baloo-5.19.0/src/engine/transaction.cpp:104
#9  0x0000557c1d93e41e in Baloo::UnindexedFileIndexer::run() (this=0x557c1e611dd0) at /usr/src/debug/baloo-5.19.0/src/file/unindexedfileindexer.cpp:64
#10 0x00007f245da15ed3 in QThreadPoolThread::run() (this=0x557c1e611ce0) at thread/qthreadpool.cpp:93
#11 0x00007f245da193de in QThreadPrivate::start(void*) (arg=0x557c1e611ce0) at thread/qthread_unix.cpp:331
#12 0x00007f245b6ea60a in start_thread (arg=0x7f230baa0700) at pthread_create.c:334
#13 0x00007f245cc07a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f245f4748c0 (LWP 9529)):
#0  0x00007f245cbf7bcd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f2457db1390 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7ffcd1d6e380, __fd=<optimized out>) at /usr/include/bits/unistd.h:44
#2  0x00007f2457db1390 in g_wakeup_acknowledge (wakeup=0x557c1dd80330) at gwakeup.c:210
#3  0x00007f2457d6dc64 in g_main_context_check (context=context@entry=0x557c1dd96d60, max_priority=2147483647, fds=fds@entry=0x557c1ddb69e0, n_fds=n_fds@entry=7) at gmain.c:3632
#4  0x00007f2457d6e110 in g_main_context_iterate (context=context@entry=0x557c1dd96d60, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3837
#5  0x00007f2457d6e27c in g_main_context_iteration (context=0x557c1dd96d60, may_block=may_block@entry=1) at gmain.c:3901
#6  0x00007f245dc50ecb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x557c1dd96ec0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x00007f245dbf7eca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffcd1d6e580, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x00007f245dbfffac in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229
#9  0x0000557c1d93186c in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/baloo-5.19.0/src/file/main.cpp:88

Possible duplicates by query: bug 354705, bug 352245.

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-11 19:37:10 UTC

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