Bug 337199

Summary:	Agent crash - BalooIndexingAgent::createIndexers
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Sebastian Stein <seb.kde>
Component:	Indexer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	chrigi_1, david.malashonok, dcorrea78, dvratil, lutz, mailinglist, matthewcarter17, thilo, tommaso.frazzetto, vbspam
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi

Description Sebastian Stein 2014-07-07 18:09:06 UTC

Application: akonadi_baloo_indexer (4.13)
KDE Platform Version: 4.13.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-30-generic x86_64
Distribution: Ubuntu 14.04 LTS

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

Currently, when my system boots and after sign-in, I always get this crash and the crash report manager shows up. I'm not using akonadi / desktop search, so I have forbidden it to index my home directory. However, I've not uninstalled anything or done any other kind of hacks.

I'm using KUbuntu 14.04.

The crash can be reproduced every time.

-- Backtrace:
Application:  (akonadi_baloo_indexer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00000000000f4240 in ?? ()
#7  0x000000000040c44c in BalooIndexingAgent::createIndexers (this=this@entry=0xa4cb40) at ../../../../src/pim/agent/agent.cpp:213
#8  0x000000000040dad2 in BalooIndexingAgent::BalooIndexingAgent (this=0xa4cb40, id=...) at ../../../../src/pim/agent/agent.cpp:94
#9  0x000000000040fe2a in Akonadi::AgentBase::init<BalooIndexingAgent> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/agentbase.h:446
#10 0x00007fe59dc9aec5 in __libc_start_main (main=0x409e70 <main(int, char**)>, argc=3, argv=0x7fff7793b758, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff7793b748) at libc-start.c:287
#11 0x0000000000409f04 in _start ()

Reported using DrKonqi

Comment 1 tommaso.frazzetto 2014-08-22 08:00:12 UTC

Application: baloo_file (0.1)
KDE Platform Version: 4.14.0
Qt Version: 4.8.6
Operating System: Linux 3.16.1-031601-generic i686
Distribution: Ubuntu 14.04.1 LTS

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

When desktop starts appears a dialog with crash informations about balooo indexer service.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0xb6831a04 in std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= (this=this@entry=0x8e0ea80, __x=...) at /usr/include/c++/4.8/bits/vector.tcc:161
#7  0xb68309fb in Xapian::Database::Database (this=0x8e0ea7c, other=...) at ../api/omdatabase.cc:82
#8  0xb683b9c2 in Xapian::Enquire::Internal::Internal (this=0x8e0ea78, db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621
#9  0xb683bbc7 in Xapian::Enquire::Enquire (this=0xbf8a5920, databases=..., errorhandler=0x0) at ../api/omenquire.cc:874
#10 0x0805e184 in Baloo::FileIndexingQueue::fillQueue (this=0x8df1d90) at ../../../src/file/fileindexingqueue.cpp:56
#11 0x0805c810 in Baloo::IndexingQueue::resume (this=0x8df1d90) at ../../../src/file/indexingqueue.cpp:56
#12 0x0805c2c6 in Baloo::IndexScheduler::IndexScheduler (this=0x8dfa108, db=0xbf8a5aa0, config=0xbf8a5ad8, parent=0xbf8a5a8c) at ../../../src/file/indexscheduler.cpp:82
#13 0x08056150 in Baloo::FileIndexer::FileIndexer (this=0xbf8a5a8c, db=0xbf8a5aa0, config=0xbf8a5ad8, parent=0xbf8a5a7c) at ../../../src/file/fileindexer.cpp:41
#14 0x0804f0d9 in main (argc=1, argv=0xbf8a5bc4) at ../../../src/file/main.cpp:86

Possible duplicates by query: bug 334831, bug 334229.

Segnala a https://bugs.kde.org/

Comment 2 Vishesh Handa 2014-09-09 13:18:36 UTC

*** Bug 337339 has been marked as a duplicate of this bug. ***

Comment 3 Vishesh Handa 2014-09-09 13:18:51 UTC

*** Bug 338609 has been marked as a duplicate of this bug. ***

Comment 4 Vishesh Handa 2014-09-09 13:20:40 UTC

*** Bug 336287 has been marked as a duplicate of this bug. ***

Comment 5 David Malashonok 2015-05-03 13:45:12 UTC

Created attachment 92390 [details]
New crash information added by DrKonqi

baloo_file (0.1) on KDE Platform 4.14.6 using Qt 4.8.6

- What I was doing when the application crashed:

I was booting up KDE and got a crash report.

-- Backtrace (Reduced):
#5  0x00007fd42cf81d0a in std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator=(std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > > const&) () at /usr/lib64/libxapian.so.22
#6  0x00007fd42cf80dbc in Xapian::Database::Database(Xapian::Database const&) () at /usr/lib64/libxapian.so.22
#7  0x00007fd42cf89dea in Xapian::Enquire::Internal::Internal(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#8  0x00007fd42cf89f9e in Xapian::Enquire::Enquire(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#9  0x0000000000417ea3 in _start ()

Comment 6 lutz 2016-07-03 13:10:05 UTC

Created attachment 99825 [details]
New crash information added by DrKonqi

baloo_file (0.1) on KDE Platform 4.14.2 using Qt 4.8.6

- Unusual behavior I noticed:
I'm using mint 17.3
Since about a week I get this segv-error after booting the system.

-- Backtrace (Reduced):
#5  std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= (this=this@entry=0x228bc90, __x=<error reading variable: Cannot access memory at address 0x10>) at /usr/include/c++/4.8/bits/vector.tcc:161
#6  0x00007f6f238fac7c in Xapian::Database::Database (this=0x228bc88, other=...) at ../api/omdatabase.cc:82
#7  0x00007f6f23904dfa in Xapian::Enquire::Internal::Internal (this=0x228bc80, db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621
#8  0x00007f6f23904fae in Xapian::Enquire::Enquire (this=0x7ffe1d982430, databases=..., errorhandler=0x0) at ../api/omenquire.cc:874
#9  0x00000000004174d3 in Baloo::FileIndexingQueue::fillQueue (this=0x227d3d0) at ../../../src/file/fileindexingqueue.cpp:56

Comment 7 ░▒▓█│【Walkman】│█▓▒░ 2017-06-21 13:34:49 UTC

Created attachment 106217 [details]
New crash information added by DrKonqi

baloo_file (0.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

Rebooted and logged into KDE desktop.
> cat /var/log/installer/media-info
Linux Mint 17.2 "Rafaela" - Release amd64 20150723
> lsb_release -d
Description:    Linux Mint 17.3 Rosa
> uname -r
3.19.0-32-generic
> plasma-desktop --version
Qt: 4.8.6
KDE Development Platform: 4.14.2
Plasma Desktop Shell: 4.11.11

-- Backtrace (Reduced):
#6  std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator= (this=this@entry=0x22b7330, __x=<error reading variable: Cannot access memory at address 0x10>) at /usr/include/c++/4.8/bits/vector.tcc:161
#7  0x00007f4f6ea61c7c in Xapian::Database::Database (this=0x22b7328, other=...) at ../api/omdatabase.cc:82
#8  0x00007f4f6ea6bdfa in Xapian::Enquire::Internal::Internal (this=0x22b7320, db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621
#9  0x00007f4f6ea6bfae in Xapian::Enquire::Enquire (this=0x7fff7ea3d120, databases=..., errorhandler=0x0) at ../api/omenquire.cc:874
#10 0x00000000004174d3 in Baloo::FileIndexingQueue::fillQueue (this=0x2270610) at ../../../src/file/fileindexingqueue.cpp:56

Comment 8 ░▒▓█│【Walkman】│█▓▒░ 2017-06-21 13:36:41 UTC

Comment on attachment 106217 [details]
New crash information added by DrKonqi

Forget to mention, happens every time I login.

Comment 9 Christoph Feck 2018-01-27 01:14:14 UTC

The 'akonadi_baloo_indexer' is part of the KDEPIM 4 packages that is no longer maintained. Please ask in a forum of your distribution how to uninstall all KDEPIM 4 packages and only use KDEPIM 5 packages.