Version: unspecified (using Devel) OS: Linux Checking the 'Enable Disconnected Mode' check box from the Akonadi Resource dialogue crashes the Imap resource. Reproducible: Always Steps to Reproduce: - Launch Kmail-mobile - Click on your Imap account - Open the 'Actions' tab - Click on 'Account' - Click on 'Edit account' - Check the ' Enable Disconnected Mode' check box Actual Results: After less than a minute the Imap resource crashes After it crashes clicking on 'Edit account' does nothing anymore (impossible to make the dialogue appear again) The work around this bug is to stop akonadi server and launch it back manually. Expected Results: The Imap resource should just disconnect to enable off line work. N900, 4:4.5~20100914.1175313-1maemo1.1174921 Known subscriber "akonadi_imap_resource_16" subscribes again Database "akonadi" opened using driver "QMYSQL" Database "akonadi" opened using driver "QMYSQL" akonadi_imap_resource_16(1794)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredCollectionChanged: Got a stale notification for a collection which was already removed. 1805 "1732" akonadi_imap_resource_16(1794)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_imap_resource_16(1794)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState akonadi_imap_resource_16(1794)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_imap_resource_16(1794)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState akonadi_imap_resource_16(1794)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: *** glibc detected *** /usr/bin/akonadi_imap_resource: double free or corruption (out): 0x41e02218 *** ======= Backtrace: ========= /lib/libc.so.6[0x41d4823c] /lib/libc.so.6[0x41d49558] /lib/libc.so.6(cfree+0xb8)[0x41d497e8] /usr/lib/libstdc++.so.6(_ZdlPv+0x14)[0x41c290dc] /usr/bin/akonadi_imap_resource[0x4854c] /usr/bin/akonadi_imap_resource[0x4913c] /usr/bin/akonadi_imap_resource[0x4918c] /usr/bin/akonadi_imap_resource[0x491b0] /usr/bin/akonadi_imap_resource[0x46af0] /usr/bin/akonadi_imap_resource[0x473c0] /usr/bin/akonadi_imap_resource[0x47be0] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN11QMetaObject8metacallEP7QObjectNS_4CallEiPPv+0x38)[0x40440bf4] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x328)[0x40457b98] /usr/lib/libkdecore.so.5(_ZN4KJob6resultEPS_+0x3c)[0x41a88aa8] /usr/lib/libkdecore.so.5(_ZN4KJob10emitResultEv+0x40)[0x41a8960c] /usr/lib/libkimap.so.4(_ZN5KIMAP8LoginJob14handleResponseERKNS_7MessageE+0x85c)[0x4120c3f8] /usr/lib/libkimap.so.4(_ZN5KIMAP14SessionPrivate16responseReceivedERKNS_7MessageE+0x4b0)[0x41212864] /usr/lib/libkimap.so.4(_ZN5KIMAP7Session11qt_metacallEN11QMetaObject4CallEiPPv+0xbc)[0x41212b70] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN11QMetaObject8metacallEP7QObjectNS_4CallEiPPv+0x38)[0x40440bf4] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x20)[0x4044f444] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x288)[0x40450a18] /opt/qt4-maemo5/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xa0)[0x406b71b0] /opt/qt4-maemo5/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x7b8)[0x406b9914] /usr/lib/libkdeui.so.5(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x19c)[0x417630b8] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x7c)[0x40438fcc] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2fc)[0x4043a5e0] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x24)[0x4043a7f0] /opt/qt4-maemo5/lib/libQtCore.so.4[0x4047453c] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1d0)[0x41f042d4] /usr/lib/libglib-2.0.so.0[0x41f07e1c] /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x70)[0x41f08410] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x50)[0x40474794] /opt/qt4-maemo5/lib/libQtGui.so.4[0x40785194] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x48)[0x404381c0] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x114)[0x404384c0] /opt/qt4-maemo5/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xa4)[0x4043a898] /opt/qt4-maemo5/lib/libQtGui.so.4(_ZN12QApplication4execEv+0x24)[0x406b6b34] /usr/lib/libakonadi-kde.so.4(_ZN7Akonadi12ResourceBase4initEPS0_+0x1c)[0x4012c650] /usr/bin/akonadi_imap_resource(_ZN7Akonadi12ResourceBase4initI12ImapResourceEEiiPPc+0x74)[0x1e764] /usr/bin/akonadi_imap_resource[0x1d2a4] /lib/libc.so.6(__libc_start_main+0x108)[0x41cf4974] /usr/bin/akonadi_imap_resource(_ZNK7Akonadi4Item21throwPayloadExceptionEii+0x44)[0x1a020]
Is it still valid? I massaged the resource without success so far, didn't crash at all.
Hi Ervin! I retested this today and it does not happen anymore. The Imap sync works fine after checking the 'Enable Disconnected Mode' check box This bug has probably been fixed in the meantime so I am closing it. N900,4:4.5~20100922.1178352-1maemo1.1177763