Bug 326437 - Imap resource crash when moving e-mails between server folders
Summary: Imap resource crash when moving e-mails between server folders
Status: RESOLVED DUPLICATE of bug 328601
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.11
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-10-22 12:03 UTC by Rod Sheaff
Modified: 2013-12-09 21:12 UTC (History)
4 users (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 Rod Sheaff 2013-10-22 12:03:40 UTC
Application: akonadi_imap_resource (4.11)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:
Moving a batch of e-mails from one folder to another on remote IMAP server

- Custom settings of the application:
Access to MS-Exchange server via DavMail 4.3.4-2174 interface

-- Backtrace:
Application: Plymouth-University of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4a6b740 (LWP 12876))]

Thread 2 (Thread 0xb22f0b40 (LWP 18981)):
#0  0xb777b424 in __kernel_vsyscall ()
#1  0xb57b1a0b in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb54f0a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb54e1b58 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb54e1c98 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb73448df in QEventDispatcherGlib::processEvents (this=0xb191bcb8, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb73139f3 in QEventLoop::processEvents (this=this@entry=0xb22f0258, flags=...) at kernel/qeventloop.cpp:149
#7  0xb7313d19 in QEventLoop::exec (this=this@entry=0xb22f0258, flags=...) at kernel/qeventloop.cpp:204
#8  0xb7202e3d in QThread::exec (this=this@entry=0x9ba9980) at thread/qthread.cpp:542
#9  0xb7202f8b in QThread::run (this=0x9ba9980) at thread/qthread.cpp:609
#10 0xb720572f in QThreadPrivate::start (arg=0x9ba9980) at thread/qthread_unix.cpp:338
#11 0xb5610d78 in start_thread (arg=0xb22f0b40) at pthread_create.c:311
#12 0xb57c101e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 1 (Thread 0xb4a6b740 (LWP 12876)):
[KCrash Handler]
#7  0x080898be in ?? ()
#8  0x08089ee0 in ?? ()
#9  0xb7329fc7 in QMetaObject::activate (sender=sender@entry=0x9bc0d70, m=m@entry=0xb5c354cc <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbfce10c8) at kernel/qobject.cpp:3539
#10 0xb5a8f9e5 in KJob::result (this=this@entry=0x9bc0d70, _t1=_t1@entry=0x9bc0d70) at ./kjob.moc:208
#11 0xb5a8fa32 in KJob::emitResult (this=0x9bc0d70) at ../../kdecore/jobs/kjob.cpp:318
#12 0xb6551e0e in KIMAP::Job::handleErrorReplies(KIMAP::Message const&) () from /usr/lib/libkimap.so.4
#13 0xb6577469 in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () from /usr/lib/libkimap.so.4
#14 0xb656ad06 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /usr/lib/libkimap.so.4
#15 0xb656d77b in ?? () from /usr/lib/libkimap.so.4
#16 0xb732677a in QMetaCallEvent::placeMetaCall (this=0xb1923920, object=0x9bc2fb8) at kernel/qobject.cpp:524
#17 0xb732e58b in QObject::event (this=0x9bc2fb8, e=0xb1923920) at kernel/qobject.cpp:1194
#18 0xb6826744 in QApplicationPrivate::notify_helper (this=0x9a56730, receiver=0x9bc2fb8, e=0xb1923920) at kernel/qapplication.cpp:4567
#19 0xb682d223 in QApplication::notify (this=0xbfce1914, receiver=receiver@entry=0x9bc2fb8, e=e@entry=0xb1923920) at kernel/qapplication.cpp:4353
#20 0xb5e11ff4 in KApplication::notify (this=0xbfce1914, receiver=0x9bc2fb8, event=0xb1923920) at ../../kdeui/kernel/kapplication.cpp:311
#21 0xb7314eda in QCoreApplication::notifyInternal (this=0xbfce1914, receiver=receiver@entry=0x9bc2fb8, event=event@entry=0xb1923920) at kernel/qcoreapplication.cpp:946
#22 0xb73186ad in sendEvent (event=0xb1923920, receiver=0x9bc2fb8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9a32f48) at kernel/qcoreapplication.cpp:1570
#24 0xb7318bbc in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#25 0xb7344f6e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=0x9a566c8) at kernel/qeventdispatcher_glib.cpp:279
#27 0xb54e182e in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0xb54e1bd8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0xb54e1c98 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0xb73448bf in QEventDispatcherGlib::processEvents (this=this@entry=0x9a33dd0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0xb68db32e in QGuiEventDispatcherGlib::processEvents (this=0x9a33dd0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0xb73139f3 in QEventLoop::processEvents (this=this@entry=0xbfce1888, flags=...) at kernel/qeventloop.cpp:149
#33 0xb7313d19 in QEventLoop::exec (this=this@entry=0xbfce1888, flags=...) at kernel/qeventloop.cpp:204
#34 0xb731989e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#35 0xb6824974 in QApplication::exec () at kernel/qapplication.cpp:3828
#36 0xb7643a78 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#37 0x080614ed in _start ()

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

Possible duplicates by query: bug 326391, bug 326242, bug 325742, bug 325619.

Reported using DrKonqi
Comment 1 pa_collins 2013-10-29 15:24:16 UTC
This also describes my own situation after upgrading to kubuntu 13.10. I get it when moving one or more messages (using kmail).

I have 2 imap connections (virginmedia and msn). Moving a message within virginmedia does not provoke the crash, but moving a message within msn does! The only apparent difference is that the msn account has many more messages in its folders then the virginmedia account.

Also, although akonadi crashes, the message movement does actually take place.

I've deleted and recreated the imap resource within akonadi, but I still get the crash.
Comment 2 Kevin Ottens 2013-11-16 07:32:41 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 3 Christian Mollekopf 2013-12-09 21:12:47 UTC

*** This bug has been marked as a duplicate of bug 328601 ***