Bug 349194

Summary:	Akonadi mykolab resource crashes when connection is established
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Andrei Sebastian Cimpean <andreiamenta>
Component:	Kolab Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kdepim-bugs
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Andrei Sebastian Cimpean 2015-06-15 17:07:36 UTC

Application: akonadi_kolab_resource (4.14)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 4.0.5-2.g0e899eb-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
A crash dialog appears after the latest update, constantly.

In akonadi configuration it shows that the resource oscilates between Connection Established and Establishin ( i think ). The resource used to work just fine.

The crash can be reproduced every time.

-- Backtrace:
Application: andreime@mykolab.com 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 0x7f7efa8518c0 (LWP 8056))]

Thread 3 (Thread 0x7f7ee3092700 (LWP 8064)):
#0  0x00007f7ef5765c5d in poll () at /lib64/libc.so.6
#1  0x00007f7ef46edbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f7ef46edcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f7ef9ea60de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007f7ef9e77e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007f7ef9e78165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f7ef9d750bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007f7ef9d7779f in  () at /usr/lib64/libQtCore.so.4
#8  0x00007f7ef4dd20a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f7ef576e08d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7ee2891700 (LWP 8067)):
#0  0x00007f7ef4dd6408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f7ef9d77c64 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4
#2  0x00007f7ef9d6b7ba in  () at /usr/lib64/libQtCore.so.4
#3  0x00007f7ef9d7779f in  () at /usr/lib64/libQtCore.so.4
#4  0x00007f7ef4dd20a4 in start_thread () at /lib64/libpthread.so.0
#5  0x00007f7ef576e08d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7efa8518c0 (LWP 8056)):
[KCrash Handler]
#5  0x00007f7ef56be187 in raise () at /lib64/libc.so.6
#6  0x00007f7ef56bf538 in abort () at /lib64/libc.so.6
#7  0x00007f7ef5cac975 in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6
#8  0x00007f7ef5caa9f6 in  () at /usr/lib64/libstdc++.so.6
#9  0x00007f7ef5caaa41 in  () at /usr/lib64/libstdc++.so.6
#10 0x00007f7ef5caaca6 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6
#11 0x00007f7ef9e78356 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#12 0x00007f7ef9e7d5b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#13 0x00007f7efa362f83 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4
#14 0x000000000042f9f3 in _start ()

Reported using DrKonqi

Comment 1 Denis Kurz 2017-06-23 20:01:32 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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:43:57 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.