Bug 341507

Summary:	Crashing when trying to sync with IMAP server and new Google Apps gmail account
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Chris <crglasoe>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kdepim-bugs, vkrause
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Chris 2014-12-02 21:26:07 UTC

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.3
Qt Version: 4.8.5
Operating System: Linux 3.11.10-21-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
crashed when I try to sync to new gmail account that was setup within google business apps

The crash can be reproduced every time.

-- Backtrace:
Application: Doxadv-GApps of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb461152880 (LWP 2433))]

Thread 3 (Thread 0x7fb44ce79700 (LWP 2756)):
#0  0x00007fb45ca997bd in poll () from /lib64/libc.so.6
#1  0x00007fb45ba29604 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fb45ba2970c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fb460782d76 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007fb460754d0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007fb460755005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007fb460653fef in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007fb46065668f in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007fb45c1030db in start_thread () from /lib64/libpthread.so.0
#9  0x00007fb45caa258d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb444ed1700 (LWP 2757)):
#0  0x00007fb45c107458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fb460656b44 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007fb46064a235 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007fb46065668f in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007fb45c1030db in start_thread () from /lib64/libpthread.so.0
#5  0x00007fb45caa258d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb461152880 (LWP 2433)):
[KCrash Handler]
#5  0x00007fb46076d463 in QMetaObject::changeGuard(QObject**, QObject*) () from /usr/lib64/libQtCore.so.4
#6  0x00007fb460c3edf2 in operator= (p=0x14fa1d0, this=<optimized out>) at /usr/include/QtCore/qpointer.h:68
#7  Akonadi::ResourceBasePrivate::slotRecursiveMoveReplay (this=<optimized out>, mover=0x14fa1d0) at /usr/src/debug/kdepimlibs-4.14.3/akonadi/resourcebase.cpp:1014
#8  0x00007fb460c44d28 in Akonadi::ResourceBase::qt_static_metacall (_o=0x1aa02f0, _c=1557542440, _id=21058880, _a=0x7fb45cd63620 <main_arena>) at /usr/src/debug/kdepimlibs-4.14.3/build/akonadi/moc_resourcebase.cpp:156
#9  0x00007fb460769d68 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007fb460c4f01e in executeRecursiveMoveReplay (_t1=0x14fa1d0, this=0x182a120) at /usr/src/debug/kdepimlibs-4.14.3/build/akonadi/moc_resourcescheduler_p.cpp:202
#11 Akonadi::ResourceScheduler::executeNext (this=0x182a120) at /usr/src/debug/kdepimlibs-4.14.3/akonadi/resourcescheduler.cpp:334
#12 0x00007fb460c4ff3d in Akonadi::ResourceScheduler::qt_static_metacall (_o=0x1aa02f0, _c=1557542440, _id=21058880, _a=0x7fb45cd63620 <main_arena>) at /usr/src/debug/kdepimlibs-4.14.3/build/akonadi/moc_resourcescheduler_p.cpp:101
#13 0x00007fb46076e11e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#14 0x00007fb45faf38ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007fb45faf9e70 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007fb45dc0456a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#17 0x00007fb4607560ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007fb4607590ff in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#19 0x00007fb460783493 in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007fb45ba29316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fb45ba29668 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fb45ba2970c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fb460782d55 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fb45fb90936 in ?? () from /usr/lib64/libQtGui.so.4
#25 0x00007fb460754d0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007fb460755005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007fb46075a13b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#28 0x00007fb460c3e5c3 in Akonadi::ResourceBase::init (r=r@entry=0x1520be0) at /usr/src/debug/kdepimlibs-4.14.3/akonadi/resourcebase.cpp:583
#29 0x000000000041a1f3 in Akonadi::ResourceBase::init<ImapResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:193
#30 0x00007fb45c9dcbe5 in __libc_start_main () from /lib64/libc.so.6
#31 0x000000000041a0b5 in _start () at ../sysdeps/x86_64/start.S:122

Possible duplicates by query: bug 327006.

Reported using DrKonqi

Comment 1 Denis Kurz 2017-06-23 20:01:37 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:44:38 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.