Bug 258476

Summary: Akonadi crashed when refreshing (F5) a folder in kmail2
Product: [Frameworks and Libraries] Akonadi Reporter: Gregor Petrin <gregap>
Component: IMAP resourceAssignee: Kevin Ottens <ervin>
Status: RESOLVED WORKSFORME    
Severity: crash CC: hr.denzler, kdepim-bugs, vkrause
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: should have checked english version

Description Gregor Petrin 2010-12-01 12:30:36 UTC 
Application: akonadi_imap_resource (0.1)
KDE Platform Version: 4.5.80 (4.6 Beta1)
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to refresh my inbox IMAP folder which was not getting synced manually by pressing F5 (I found this hint on KDE forums). I suspect something might be wrong with my configuration and the imap-folder-not syncing and crash-on-sync may be related. I have previously had to delete old nepomuk user data since which was there from an old version, due to which I had to re-create all my email configuration (as I was getting the 'resource not found' error message from kmail2) and that's when the problems seemed to start.

I am sorry if there are any duplicates for this report, my search returned hundreds of seemingly unrelated error reports and I didn't have time go through them all as I am at work :(

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted
[Current thread is 1 (Thread 0xb4af5710 (LWP 8620))]

Thread 2 (Thread 0xb11f0b70 (LWP 8627)):
#0  0xb570efa0 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0xb585e464 in pthread_mutex_lock () from /lib/libc.so.6
#2  0xb55ad14f in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb55ad60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4  0xb7351da7 in QEventDispatcherGlib::processEvents (this=0x8247460, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0xb732289d in QEventLoop::processEvents (this=0xb11f02d0, flags=...) at kernel/qeventloop.cpp:149
#6  0xb7322ac9 in QEventLoop::exec (this=0xb11f02d0, flags=...) at kernel/qeventloop.cpp:201
#7  0xb72217a9 in QThread::exec (this=0x815d080) at thread/qthread.cpp:490
#8  0xb65963d0 in ?? () from /usr/lib/libkimap.so.4
#9  0xb722439a in QThreadPrivate::start (arg=0x815d080) at thread/qthread_unix.cpp:285
#10 0xb570cb25 in start_thread () from /lib/libpthread.so.0
#11 0xb585046e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4af5710 (LWP 8620)):
[KCrash Handler]
#7  0xffffe430 in __kernel_vsyscall ()
#8  0xb57a87ff in raise () from /lib/libc.so.6
#9  0xb57aa140 in abort () from /lib/libc.so.6
#10 0xb57e4fd7 in __libc_message () from /lib/libc.so.6
#11 0xb57eaffb in malloc_printerr () from /lib/libc.so.6
#12 0xb57efb49 in free () from /lib/libc.so.6
#13 0xb59b898f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb7334dea in QMetaCallEvent::~QMetaCallEvent (this=0x81f7d98, __in_chrg=<value optimized out>) at kernel/qobject.cpp:528
#15 0xb7327354 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80caee0) at kernel/qcoreapplication.cpp:1389
#16 0xb732749c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#17 0xb7351bd4 in sendPostedEvents (s=0x80e6920) at kernel/qcoreapplication.h:220
#18 postEventSourceDispatch (s=0x80e6920) at kernel/qeventdispatcher_glib.cpp:277
#19 0xb55acb49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb55ad350 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb55ad60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb7351d5b in QEventDispatcherGlib::processEvents (this=0x80e4400, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#23 0xb68f19aa in QGuiEventDispatcherGlib::processEvents (this=0x80e4400, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0xb732289d in QEventLoop::processEvents (this=0xbf8710e4, flags=...) at kernel/qeventloop.cpp:149
#25 0xb7322ac9 in QEventLoop::exec (this=0xbf8710e4, flags=...) at kernel/qeventloop.cpp:201
#26 0xb7327570 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#27 0xb6839114 in QApplication::exec () at kernel/qapplication.cpp:3719
#28 0xb754a994 in Akonadi::ResourceBase::init (r=0x80e6800) at /usr/src/debug/kdepimlibs-4.5.80/akonadi/resourcebase.cpp:283
#29 0x08063833 in init<ImapResource> (argc=) at /usr/include/akonadi/resourcebase.h:188
#30 main (argc=) at /usr/src/debug/kdepim-runtime-4.5.80/resources/imap/imapresource.cpp:579

Possible duplicates by query: bug 258461, bug 258452, bug 258273, bug 258214, bug 258205.

Reported using DrKonqi
Comment 1 Hans-Rudi Denzler 2010-12-02 14:10:40 UTC 
Click e.g. drafts then e.g. inbox again instead of F5 ?
Comment 2 Gregor Petrin 2010-12-02 15:00:33 UTC 
That did not work for some reason - most recent mail in my mailbox was from January and I couldn't change this either by viewing other directories or restarting KMail (even tried rebooting :)).
Comment 3 Hans-Rudi Denzler 2010-12-02 18:06:35 UTC 
You may start ksystemlog as user (not root) > protocols > Others > X-Sessions-Protokoll (.xsession-errors) with Filter: akonadi

(I deleted some Akonadi resources and added them again: IMAP-E-Mail-Server ?)
Comment 4 Gregor Petrin 2010-12-03 10:18:21 UTC 
I tried doing that, there is no 'protocols > Others > X-Sessions-Protokol' option, I did however find the .xsessions-errors blog in my home directory so I opened that. I started KMail and pressed F5 on the inbox folder - this time nothing crashed, but I'm not getting my email either. A kwallet dialog appears from time to time, wanting my password. Here's the log output:


03.12.10 10:13:15			Database "akonadi" opened using driver "QMYSQL" 
03.12.10 10:13:15			Database "akonadi" opened using driver "QMYSQL" 
03.12.10 10:13:15			kwalletd(1773) KWalletD::setupDialog: Application ' "Akonadi Resource" ' using kwallet without parent window! 
03.12.10 10:13:15			akonadi_imap_resource_2(12839)/kdepimlibs (kimap) KIMAP::SessionThread::~SessionThread: Session thread refuses to die, killing harder... 
03.12.10 10:13:15			KCrash: Application 'akonadi_imap_resource' crashing...
03.12.10 10:13:15			akonadi_imap_resource: Fatal IO error: client killed
03.12.10 10:13:15			Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_imap_resource_2" , discarding cached interface 
03.12.10 10:13:15			ProcessControl: Application '/usr/bin/akonadi_imap_resource' returned with exit code 1 (Unknown error)
03.12.10 10:13:15			Known subscriber "akonadi_imap_resource_2" subscribes again 
03.12.10 10:13:15			Database "akonadi" opened using driver "QMYSQL" 
03.12.10 10:13:15			kwalletd(1773) KWalletD::setupDialog: Application ' "Akonadi Resource" ' using kwallet without parent window! 
03.12.10 10:13:15			akonadi_imap_resource_2(16629)/kdepimlibs (kimap) KIMAP::SessionThread::~SessionThread: Session thread refuses to die, killing harder... 
03.12.10 10:13:51			akonadi_imap_resource_2(16629)/kdepimlibs (kimap) KIMAP::SessionThread::~SessionThread: Session thread refuses to die, killing harder... 
03.12.10 10:13:51			Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_imap_resource_2" , discarding cached interface 
03.12.10 10:13:51			KCrash: Application 'akonadi_imap_resource' crashing...
03.12.10 10:13:51			ProcessControl: Application '/usr/bin/akonadi_imap_resource' returned with exit code 255 (Unknown error)
03.12.10 10:13:53			Known subscriber "akonadi_imap_resource_2" subscribes again 
03.12.10 10:13:53			Database "akonadi" opened using driver "QMYSQL" 
03.12.10 10:13:53			kwalletd(1773) KWalletD::setupDialog: Application ' "Akonadi Resource" ' using kwallet without parent window!
Comment 5 Hans-Rudi Denzler 2010-12-03 11:16:09 UTC 
Created attachment 54026 [details]
should have checked english version
Comment 6 Kevin Ottens 2011-09-17 09:42:11 UTC 
Is it still happening for you with 4.7.x? I've been unable to reproduce that one, it just works for me.

In case you still experience this please feel free to reopen. In such a case, we would need much more information like the actual IMAP server used and so on.