Bug 361868

Summary:	Baloo crashes every time i change an filename, or add a new file
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	boospy <linux>
Component:	Baloo File Daemon	Assignee:	Pinak Ahuja <pinak.ahuja>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	aspotashev, cullmann, pinak.ahuja
Priority:	NOR	Keywords:	drkonqi
Version:	5.18.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description boospy 2016-04-16 18:34:58 UTC

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-18-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Balooservice is stopped

- Custom settings of the application:
I set customfolders outside my home. Folder they are on an NFSshare. The share is permanently mounted in the FSTAB. Unix ACLs are used 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/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8ace888c0 (LWP 17346))]

Thread 2 (Thread 0x7ff763193700 (LWP 32311)):
[KCrash Handler]
#6  0x00007ff8ac0573c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x00007ff8ac073896 in Baloo::PostingCodec::decode(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00007ff8ac05f814 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x00007ff8ac0703c6 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007ff8ac068032 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x000000000041c8e0 in Baloo::NewFileIndexer::run() ()
#12 0x00007ff8ab986343 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ff8ab98984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ff8aa5ed6fa in start_thread (arg=0x7ff763193700) at pthread_create.c:333
#15 0x00007ff8aaf96b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ff8ace888c0 (LWP 17346)):
#0  0x00007ff8aaf869cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff8a819e6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff8a815ae04 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff8a815b2c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ff8a815b42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ff8abbc0a9b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007ff8abb67dea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ff8abb6fe8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x000000000041698c in main ()

Possible duplicates by query: bug 356445.

Reported using DrKonqi

Comment 1 boospy 2016-04-17 12:31:30 UTC

When i touched a file, here is the CMD output. Maybe it is helpfull:

KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/run/user/10001/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file path = /usr/bin pid = 29076
KCrash: Arguments: /usr/bin/baloo_file 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/10001/kdeinit5__0
QSocketNotifier: Invalid socket 4 and type 'Read', disabling...
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 7 and type 'Exception', disabling...

Comment 2 Christoph Cullmann 2016-09-11 13:40:29 UTC


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