Bug 201622 - Kontact crash after renaming a folder
Summary: Kontact crash after renaming a folder
Status: RESOLVED DUPLICATE of bug 180373
Alias: None
Product: kmail
Classification: Applications
Component: disconnected IMAP (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 07:24 UTC by Andreas Roth
Modified: 2009-07-27 09:28 UTC (History)
0 users

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 Andreas Roth 2009-07-27 07:24:54 UTC
Application that crashed: kontact
Version of the application: 4.3.0 rc3
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I just renamed on of my IMAP folders and a some time after renaming it kontact crashed. I'm using DIMAP with Kolab data in my mail account.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f3a8fdf08c2 in KMFolderCachedImap::findByUID (this=0x166cbf0, uid=16) at /build/buildd/kdepim-4.2.98/kmail/kmfoldercachedimap.cpp:691
#6  0x00007f3a8fe06cb8 in KMFolderCachedImap::slotGetMessagesData (this=0x166cbf0, job=0x174ce70, data=@0x7fffb053eb00) at /build/buildd/kdepim-4.2.98/kmail/kmfoldercachedimap.cpp:1862
#7  0x00007f3a8fe0a06b in KMFolderCachedImap::qt_metacall (this=0x166cbf0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb053e740)
    at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmfoldercachedimap.moc:201
#8  0x00007f3aa2a708d2 in QMetaObject::activate (sender=0x174ce70, from_signal_index=<value optimized out>, to_signal_index=40, argv=0x386ee20) at kernel/qobject.cpp:3120
#9  0x00007f3aa4ee3bb4 in KIO::TransferJob::data (this=0x166cbf0, _t1=0x174ce70, _t2=<value optimized out>) at /build/buildd/kde4libs-4.2.98a/obj-x86_64-linux-gnu/kio/jobclasses.moc:364
#10 0x00007f3aa4ee9519 in KIO::TransferJob::qt_metacall (this=0x174ce70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb053e870)
    at /build/buildd/kde4libs-4.2.98a/obj-x86_64-linux-gnu/kio/jobclasses.moc:344
#11 0x00007f3aa2a708d2 in QMetaObject::activate (sender=0x15ce480, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x386ee20) at kernel/qobject.cpp:3120
#12 0x00007f3aa4fa72a2 in KIO::SlaveInterface::data (this=0x166cbf0, _t1=<value optimized out>) at /build/buildd/kde4libs-4.2.98a/obj-x86_64-linux-gnu/kio/slaveinterface.moc:140
#13 0x00007f3aa4faab28 in KIO::SlaveInterface::dispatch (this=0x15ce480, _cmd=100, rawdata=<value optimized out>) at /build/buildd/kde4libs-4.2.98a/kio/kio/slaveinterface.cpp:163
#14 0x00007f3aa4fa7552 in KIO::SlaveInterface::dispatch (this=0x15ce480) at /build/buildd/kde4libs-4.2.98a/kio/kio/slaveinterface.cpp:91
#15 0x00007f3aa4f9a0d3 in KIO::Slave::gotInput (this=0x15ce480) at /build/buildd/kde4libs-4.2.98a/kio/kio/slave.cpp:322
#16 0x00007f3aa4f9c338 in KIO::Slave::qt_metacall (this=0x15ce480, _c=QMetaObject::InvokeMetaMethod, _id=145, _a=0x7fffb053ec60)
    at /build/buildd/kde4libs-4.2.98a/obj-x86_64-linux-gnu/kio/slave.moc:76
#17 0x00007f3aa2a708d2 in QMetaObject::activate (sender=0x26a6910, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x386ee20) at kernel/qobject.cpp:3120
#18 0x00007f3aa4eb7761 in KIO::ConnectionPrivate::dequeue (this=0x25a97c0) at /build/buildd/kde4libs-4.2.98a/kio/kio/connection.cpp:82
#19 0x00007f3aa4eb7bba in KIO::Connection::qt_metacall (this=0x26a6910, _c=QMetaObject::InvokeMetaMethod, _id=145, _a=0x30a9ff0)
    at /build/buildd/kde4libs-4.2.98a/obj-x86_64-linux-gnu/kio/connection.moc:73
#20 0x00007f3aa2a6af28 in QObject::event (this=0x26a6910, e=0x2947a70) at kernel/qobject.cpp:1118
#21 0x00007f3aa35d9b9d in QApplicationPrivate::notify_helper (this=0xb93e90, receiver=0x26a6910, e=0x2947a70) at kernel/qapplication.cpp:4057
#22 0x00007f3aa35e1dea in QApplication::notify (this=0x7fffb053f6c0, receiver=0x26a6910, e=0x2947a70) at kernel/qapplication.cpp:4022
#23 0x00007f3aa4a0971b in KApplication::notify (this=0x7fffb053f6c0, receiver=0x26a6910, event=0x2947a70) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#24 0x00007f3aa2a5adfc in QCoreApplication::notifyInternal (this=0x7fffb053f6c0, receiver=0x26a6910, event=0x2947a70) at kernel/qcoreapplication.cpp:610
#25 0x00007f3aa2a5ba6a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xb62850) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 0x00007f3aa2a848a3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#27 0x00007f3a9c1ad20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007f3a9c1b08e0 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x00007f3a9c1b0a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007f3aa2a8452f in QEventDispatcherGlib::processEvents (this=0xb620a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#31 0x00007f3aa367270f in QGuiEventDispatcherGlib::processEvents (this=0x166cbf0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#32 0x00007f3aa2a596a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1336674848}) at kernel/qeventloop.cpp:149
#33 0x00007f3aa2a59a6d in QEventLoop::exec (this=0x7fffb053f620, flags={i = -1336674768}) at kernel/qeventloop.cpp:200
#34 0x00007f3aa2a5bd34 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#35 0x0000000000404945 in main (argc=1, argv=0x7fffb053fda8) at /build/buildd/kdepim-4.2.98/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Christophe Marin 2009-07-27 09:28:05 UTC

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