Bug 354136 - Akonadi Kolab Resource crashes (and continues to crash) after adding a ToDo in Zanshin
Summary: Akonadi Kolab Resource crashes (and continues to crash) after adding a ToDo i...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: 1.13.0
Platform: Mageia RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-20 17:13 UTC by Matija Šuklje
Modified: 2018-02-01 09:47 UTC (History)
1 user (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 Matija Šuklje 2015-10-20 17:13:08 UTC
Application: akonadi_kolab_resource (4.14)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.8-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

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

1) added a new ToDo via Zanshin
2) a sync starts (I guess)

Results:
*) crash
*) crash, crash, crash, regardless if I restart the resource or whatever, it just won’t start crashing

Expecter results:
*) no crash ;)

The crash can be reproduced sometimes.

-- Backtrace:
Application: FSFE 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 0x7f8ca9e197c0 (LWP 19682))]

Thread 2 (Thread 0x7f8c9287e700 (LWP 19684)):
#0  0x00007f8ca4cb9d1d in poll () at /lib64/libc.so.6
#1  0x00007f8ca3c2eeb4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f8ca3c2efbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f8ca9452e3e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#4  0x00007f8ca9424931 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#5  0x00007f8ca9424c45 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#6  0x00007f8ca9322899 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x00007f8ca9324fff in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4
#8  0x00007f8ca43195bd in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8ca4cc55cd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8ca9e197c0 (LWP 19682)):
[KCrash Handler]
#5  0x00007f8ca4c01627 in raise () at /lib64/libc.so.6
#6  0x00007f8ca4c02dba in abort () at /lib64/libc.so.6
#7  0x00007f8ca51f8c0d in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6
#8  0x00007f8ca51f6c96 in __cxxabiv1::__terminate(void (*)()) () at /lib64/libstdc++.so.6
#9  0x00007f8ca51f6ce1 in  () at /lib64/libstdc++.so.6
#10 0x00007f8ca51f6f46 in __cxa_rethrow () at /lib64/libstdc++.so.6
#11 0x00007f8ca9424e5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#12 0x00007f8ca9429e59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#13 0x00007f8ca992045c in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /lib64/libakonadi-kde.so.4
#14 0x0000000000430fe8 in int Akonadi::ResourceBase::init<KolabResource>(int, char**) ()
#15 0x00007f8ca4bedfd0 in __libc_start_main () at /lib64/libc.so.6
#16 0x000000000041b79e in _start ()

Reproducible: Always
Comment 1 Matija Šuklje 2015-10-20 17:41:29 UTC
I had to remove and re-add the resource. Nothing else seemed to work.
Comment 2 Denis Kurz 2017-06-23 20:20:17 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 3 Denis Kurz 2018-02-01 09:47:34 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.