Bug 352280 - akonadi kolab connector crash every repeatly
Summary: akonadi kolab connector crash every repeatly
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
Keywords: drkonqi
Depends on:
Reported: 2015-09-04 16:40 UTC by Johann-Nikolaus Andreae
Modified: 2018-02-01 09:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Johann-Nikolaus Andreae 2015-09-04 16:40:06 UTC
Application: akonadi_kolab_resource (4.14)
KDE Platform Version: 4.14.10
Qt Version: 4.8.7
Operating System: Linux 4.1.6-1-desktop x86_64
Distribution: "openSUSE 20150831 (Tumbleweed) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Everey time I open konact the kolab connector crash. If I close the crash window the connector crash again.

The crash can be reproduced every time.

-- Backtrace:
Application: E-Mail of type Kolab Groupware Server (akonadi_kolab_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f137770e880 (LWP 17261))]

Thread 3 (Thread 0x7f135f96a700 (LWP 17263)):
#0  0x00007f13724eb32d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f1371b0ee94 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f13580013e0, timeout=<optimized out>, context=0x7f13580009a0) at gmain.c:4103
#2  0x00007f1371b0ee94 in g_main_context_iterate (context=context@entry=0x7f13580009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3803
#3  0x00007f1371b0ef9c in g_main_context_iteration (context=0x7f13580009a0, may_block=may_block@entry=1) at gmain.c:3869
#4  0x00007f137721926e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f13580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x00007f13771e93e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f135f969d60, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f13771e96f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f135f969d60, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f13770e2a59 in QThread::exec() (this=<optimized out>) at thread/qthread.cpp:538
#8  0x00007f13770e523c in QThreadPrivate::start(void*) (arg=0xb8f9f0) at thread/qthread_unix.cpp:352
#9  0x00007f13721f54a4 in start_thread (arg=0x7f135f96a700) at pthread_create.c:334
#10 0x00007f13724f3cad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f135f169700 (LWP 17264)):
#0  0x00007f13721fb428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x00007f13770e5732 in QWaitCondition::wait(QMutex*, unsigned long) (time=30000, this=0x7f1358016bd0) at thread/qwaitcondition_unix.cpp:84
#2  0x00007f13770e5732 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f1358016980, mutex=mutex@entry=0x7f13580167a8, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f13770d8c3f in QThreadPoolThread::run() (this=0x7f1358016970) at concurrent/qthreadpool.cpp:142
#4  0x00007f13770e523c in QThreadPrivate::start(void*) (arg=0x7f1358016970) at thread/qthread_unix.cpp:352
#5  0x00007f13721f54a4 in start_thread (arg=0x7f135f169700) at pthread_create.c:334
#6  0x00007f13724f3cad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f137770e880 (LWP 17261)):
[KCrash Handler]
#6  0x00007f137243e7a8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007f137243fbfa in __GI_abort () at abort.c:78
#8  0x00007f1372a5cb1d in __gnu_cxx::__verbose_terminate_handler() () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007f1372a5ab86 in __cxxabiv1::__terminate(void (*)()) (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x00007f1372a5abd1 in std::terminate() () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x00007f1372a5ae36 in __cxxabiv1::__cxa_rethrow() () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:125
#12 0x00007f13771e9914 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffedfa265f0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f13771eeef9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1227
#14 0x00007f137656f7dc in QApplication::exec() () at kernel/qapplication.cpp:3823
#15 0x00007f1374f4c12d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) (r=r@entry=0xb1af20) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/resourcebase.cpp:583
#16 0x00000000004334fe in Akonadi::ResourceBase::init<KolabResource>(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:193
#17 0x00007f137242b610 in __libc_start_main (main=0x41bdc0 <main(int, char**)>, argc=3, argv=0x7ffedfa26788, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffedfa26778) at libc-start.c:289
#18 0x000000000041c309 in _start () at ../sysdeps/x86_64/start.S:118

The reporter indicates this bug may be a duplicate of or related to bug 350831.

Possible duplicates by query: bug 351097, bug 350831, bug 349113, bug 347814, bug 347595.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:20:23 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:50:15 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.