Bug 192789 - Kontact Crashes Upon Emptying IMAP Trash Folder (with stacktrace)
Summary: Kontact Crashes Upon Emptying IMAP Trash Folder (with stacktrace)
Status: RESOLVED DUPLICATE of bug 174839
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-15 17:22 UTC by Jeffery Tincher
Modified: 2009-05-15 17:27 UTC (History)
1 user (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 Jeffery Tincher 2009-05-15 17:22:57 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Application: Kontact (kontact), signal SIGABRT
0x00007f21ae004d21 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c

Thread 1 (Thread 0x7f21b44ad750 (LWP 13130)):
[KCrash Handler]
#5  0x00007f21adf8ffb5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007f21adf91bc3 in *__GI_abort () at abort.c:88
#7  0x00007f21aeadd885 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2006
#8  0x00007f21aeadd9cb in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2201
#9  0x00007f219bb75414 in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x2c5ac90) at /build/buildd/kdepim-4.2.2/kmail/messagelistview/core/model.cpp:3853
#10 0x00007f219b711268 in KMail::MessageListView::Core::Model::qt_metacall (this=0x2c5ac90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbc4e6d30)
    at /build/buildd/kdepim-4.2.2/obj-x86_64-linux-gnu/kmail/moc_model.cpp:76
#11 0x00007f21aebe41f2 in QMetaObject::activate (sender=0x2c5a9c0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xffffffffffffffff) at kernel/qobject.cpp:3069
#12 0x00007f21aebde4d3 in QObject::event (this=0x2c5a9c0, e=0x334a) at kernel/qobject.cpp:1082
#13 0x00007f21af77778d in QApplicationPrivate::notify_helper (this=0x24873a0, receiver=0x2c5a9c0, e=0x7fffbc4e73e0) at kernel/qapplication.cpp:4084
#14 0x00007f21af77f97a in QApplication::notify (this=0x7fffbc4e7730, receiver=0x2c5a9c0, e=0x7fffbc4e73e0) at kernel/qapplication.cpp:4049
#15 0x00007f21b0bac26b in KApplication::notify (this=0x7fffbc4e7730, receiver=0x2c5a9c0, event=0x7fffbc4e73e0) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#16 0x00007f21aebce75c in QCoreApplication::notifyInternal (this=0x7fffbc4e7730, receiver=0x2c5a9c0, event=0x7fffbc4e73e0) at kernel/qcoreapplication.cpp:602
#17 0x00007f21aebfb7f6 in QTimerInfoList::activateTimers (this=0x24810c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0x00007f21aebf7f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#19 0x00007f21a831720a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0x00007f21a831a8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x00007f21a831aa7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0x00007f21aebf7e6f in QEventDispatcherGlib::processEvents (this=0x245ef20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#23 0x00007f21af80fbef in QGuiEventDispatcherGlib::processEvents (this=0x334a, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x00007f21aebcd002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1135708592}) at kernel/qeventloop.cpp:149
#25 0x00007f21aebcd3cd in QEventLoop::exec (this=0x7fffbc4e7690, flags={i = -1135708512}) at kernel/qeventloop.cpp:200
#26 0x00007f21aebcf694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#27 0x0000000000404a15 in main (argc=1, argv=0x7fffbc4e7e18) at /build/buildd/kdepim-4.2.2/kontact/src/main.cpp:218
Comment 1 Dario Andres 2009-05-15 17:27:32 UTC
Marking as duplicate of bug 174839 (from bug 192756)
Thanks

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