Bug 378187 - akonadi_control crashes when starting kontact for the first time
Summary: akonadi_control crashes when starting kontact for the first time
Status: RESOLVED NOT A BUG
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 378240 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-28 06:52 UTC by Martin Tlustos
Modified: 2017-04-21 02:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2017-03-28 06:52:38 UTC 
I have KDE Neon installed, and with version 4:16.12.3 akonadi_control always crashes the first time I start any pim application (normally kontact). Then it restarts itself and everything is fine, except I get this crash information.
Comment 1 Martin Tlustos 2017-03-28 06:53:05 UTC 
Crash information:
Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f19272f58c0 (LWP 2328))]

Thread 2 (Thread 0x7f191a8be700 (LWP 2329)):
#0  0x00007f1925644b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f1922136c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f19221388d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f191ce16d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f1925f59b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f19253346ba in start_thread (arg=0x7f191a8be700) at pthread_create.c:333
#6  0x00007f192565082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f19272f58c0 (LWP 2328)):
[KCrash Handler]
#6  0x00007f192557f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007f192558102a in __GI_abort () at abort.c:89
#8  0x00007f1925f40811 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x000000000042f85f in akInit (appName=...) at /workspace/build/src/shared/akdebug.cpp:197
#10 0x000000000042d5e2 in AkApplicationBase::init (this=this@entry=0x7ffd0ad471b0) at /workspace/build/src/shared/akapplication.cpp:62
#11 0x0000000000409d9b in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffd0ad47318, argc=@0x7ffd0ad4701c: 1, this=0x7ffd0ad471b0) at /workspace/build/src/shared/akapplication.h:83
#12 main (argc=1, argv=0x7ffd0ad47318) at /workspace/build/src/akonadicontrol/main.cpp:56
Comment 2 Daniel Vrátil 2017-03-28 20:53:28 UTC 
That's a fatal error message when akonadi_control cannot connect to DBus session. Means that there's some problem with your session not starting DBus properly or not having the environment set, not a bug in Akonadi.
Comment 3 Christoph Feck 2017-04-21 02:07:34 UTC 
*** Bug 378240 has been marked as a duplicate of this bug. ***