Bug 336287 - launch kmail, baloo crashes
Summary: launch kmail, baloo crashes
Status: RESOLVED DUPLICATE of bug 337199
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Indexer (show other bugs)
Version: 4.13
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-06-15 22:56 UTC by Joe Biden
Modified: 2015-03-17 12:46 UTC (History)
5 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 Joe Biden 2014-06-15 22:56:18 UTC
Application: akonadi_baloo_indexer (4.13)
KDE Platform Version: 4.13.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Ubuntu 14.04 LTS

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

Launching kmail just crashes baloo. Every...every...time. What is the deal?

The crash can be reproduced every time.

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

Reported using DrKonqi
Comment 1 Christoph Feck 2014-06-16 12:16:00 UTC
Please reassign to Akonadi developers, if not correct here.
Comment 2 Laurent Montel 2014-07-06 07:12:27 UTC
I caught more exception in 4.13.3 I hope that it will fix your bug.
Comment 3 Vishesh Handa 2014-09-09 13:20:40 UTC

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