Application: kmail (1.13.6) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 2.6.38-8-generic x86_64 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: Just usual stuff - konsole, chrome runnin. Ive got popup from tray that new email came and kmail instantly crashed. Happend to me several times before and is still happening. - Unusual behavior I noticed: Tray popup showed with 1 unread email. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f7077d63840 (LWP 11154))] Thread 2 (Thread 0x7f7058df3700 (LWP 11157)): #0 0x00007f7074cbff03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f706cbc8104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f706cbc89f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f7063df9c44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x00007f706cbef3e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f707287cd8c in start_thread (arg=0x7f7058df3700) at pthread_create.c:304 #6 0x00007f7074ccd04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f7077d63840 (LWP 11154)): [KCrash Handler] #6 KMail::ActionScheduler::actionMessage (this=0x22dea20, res=<value optimized out>) at ../../kmail/actionscheduler.cpp:675 #7 0x00007f707679e697 in KMail::ActionScheduler::filterMessage (this=0x22dea20) at ../../kmail/actionscheduler.cpp:648 #8 0x00007f707679ea54 in KMail::ActionScheduler::qt_metacall (this=0x22dea20, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff7eb1fbd0) at ./actionscheduler.moc:130 #9 0x00007f70756075f8 in QMetaObject::activate (sender=0x22df0e0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3287 #10 0x00007f70756061c9 in QObject::event (this=0x22df0e0, e=<value optimized out>) at kernel/qobject.cpp:1190 #11 0x00007f7075ae09e4 in QApplicationPrivate::notify_helper (this=0x1b60480, receiver=0x22df0e0, e=0x7fff7eb202d0) at kernel/qapplication.cpp:4462 #12 0x00007f7075ae53aa in QApplication::notify (this=<value optimized out>, receiver=0x22df0e0, e=0x7fff7eb202d0) at kernel/qapplication.cpp:4341 #13 0x00007f707778c866 in KApplication::notify (this=0x7fff7eb20700, receiver=0x22df0e0, event=0x7fff7eb202d0) at ../../kdeui/kernel/kapplication.cpp:311 #14 0x00007f70755f249c in QCoreApplication::notifyInternal (this=0x7fff7eb20700, receiver=0x22df0e0, event=0x7fff7eb202d0) at kernel/qcoreapplication.cpp:731 #15 0x00007f707561ff12 in sendEvent (this=0x1b5f2d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #16 QTimerInfoList::activateTimers (this=0x1b5f2d0) at kernel/qeventdispatcher_unix.cpp:604 #17 0x00007f707561ccf4 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184 #18 0x00007f706cbc7bcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f706cbc83a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f706cbc8639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f707561d3ef in QEventDispatcherGlib::processEvents (this=0x1ad2310, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #22 0x00007f7075b87dfe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x00007f70755f1882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #24 0x00007f70755f1abc in QEventLoop::exec (this=0x7fff7eb20540, flags=...) at kernel/qeventloop.cpp:201 #25 0x00007f70755f5ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #26 0x0000000000403175 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:158 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 169048 ***