Bug 290410

Summary: Crash on exit from kmail
Product: [Applications] kmail2 Reporter: abrahams
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: johannesobermayr
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description abrahams 2012-01-02 15:14:42 UTC 
Application: kmail (4.8 rc1)
KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-15-generic x86_64
Distribution: Ubuntu 11.10

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

- Unusual behavior I noticed: inbox was out of sync, highlighted message not the same as the one displayed.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0x7f0065ad57a0 (LWP 3271))]

Thread 4 (Thread 0x7f00463b4700 (LWP 3277)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f0057d5cc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f0057d5cd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f0060a18efc in start_thread (arg=0x7f00463b4700) at pthread_create.c:304
#4  0x00007f0062e7289d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f0045aa3700 (LWP 3278)):
#0  0x00007f0062e66773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f005bb3ef68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f005bb3f429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f00637e4f3e in QEventDispatcherGlib::processEvents (this=0x2025a00, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f00637b8cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f00637b8ef7 in QEventLoop::exec (this=0x7f0045aa2de0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f00636d027f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007f00636d2d05 in QThreadPrivate::start (arg=0x20251a0) at thread/qthread_unix.cpp:331
#8  0x00007f0060a18efc in start_thread (arg=0x7f0045aa3700) at pthread_create.c:304
#9  0x00007f0062e7289d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7efffddb0700 (LWP 3279)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007f0062e0f9df in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f0062e0dd71 in __GI___libc_free (mem=0x7f006312b1c0) at malloc.c:3736
#3  0x00007f00637e4665 in socketNotifierSourceCheck (source=0x24cb540) at kernel/qeventdispatcher_glib.cpp:92
#4  0x00007f005bb3e734 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f005bb3ef82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f005bb3f429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f00637e4ed6 in QEventDispatcherGlib::processEvents (this=0x24ca650, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#8  0x00007f00637b8cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#9  0x00007f00637b8ef7 in QEventLoop::exec (this=0x7efffddafdb0, flags=...) at kernel/qeventloop.cpp:201
#10 0x00007f00636d027f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#11 0x00007f006379bcbf in QInotifyFileSystemWatcherEngine::run (this=0x24c8370) at io/qfilesystemwatcher_inotify.cpp:248
#12 0x00007f00636d2d05 in QThreadPrivate::start (arg=0x24c8370) at thread/qthread_unix.cpp:331
#13 0x00007f0060a18efc in start_thread (arg=0x7efffddb0700) at pthread_create.c:304
#14 0x00007f0062e7289d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0065ad57a0 (LWP 3271)):
[KCrash Handler]
#6  0x00007f0062dc73a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f0062dcab0b in __GI_abort () at abort.c:92
#8  0x00007f0062dff113 in __libc_message (do_abort=2, fmt=0x7f0062ef00d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007f0062e09a96 in malloc_printerr (action=3, str=0x7f0062eed0ef "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
#10 0x00007f0062e0dd7c in __GI___libc_free (mem=<optimized out>) at malloc.c:3738
#11 0x00007f005fb2c96d in qDeleteAll<QList<Node*>::const_iterator> (end=<optimized out>, begin=<optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:322
#12 qDeleteAll<QList<Node*> > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330
#13 Akonadi::EntityTreeModel::~EntityTreeModel (this=0x11c1730, __in_chrg=<optimized out>) at ../../akonadi/entitytreemodel.cpp:79
#14 0x00007f005fb2c9f9 in Akonadi::EntityTreeModel::~EntityTreeModel (this=0x11c1730, __in_chrg=<optimized out>) at ../../akonadi/entitytreemodel.cpp:83
#15 0x00007f00637cbd75 in QObjectPrivate::deleteChildren (this=0x1d08020) at kernel/qobject.cpp:1955
#16 0x00007f00637d1349 in QObject::~QObject (this=0x7fff35a23a30, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#17 0x00007f00648a83ad in KMKernel::~KMKernel (this=0x7fff35a23a30, __in_chrg=<optimized out>) at ../../kmail/kmkernel.cpp:226
#18 0x0000000000402bee in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:128

Possible duplicates by query: bug 290055, bug 289967, bug 289927, bug 289693, bug 289453.

Reported using DrKonqi
Comment 1 Johannes Obermayr 2012-01-02 16:34:51 UTC 
On my both openSUSE 12.1, KDE:Unstable:SC, x86_64 based systems this crash as well as the outage of IMAP sync happens only if I deleted sth. in IMAP folders (but only sometimes).

Moving emails to lokal folders (e.g. via filters) doesn't crash KMail.

KMail delivered with 4.7.90 worked fine.

Can you verify it?
Comment 2 abrahams 2012-01-02 16:59:20 UTC 
What should I do to verify that crash (which is only one of my kmail problems now)?  I see the message on the screen after I quit.  What more information would there be?  I've already submitted a backtrace.  And now I get the crash on every exit.

Right now my inbox is badly out of sync and I can't find any way to straighten it out.  The message in the index is not the same as the message in the lower pane.  And when I delete a message, it doesn't go away; instead it gets grayed out in the index.

I don't know if all my kmail problems are interconnected, but there are many of them.  They all started after I migrated from kmail.
Comment 3 Christophe Marin 2012-01-02 17:38:07 UTC 

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