Bug 230452 - Kontact crashes trying to accidentally open a hidden imap directory
Summary: Kontact crashes trying to accidentally open a hidden imap directory
Status: RESOLVED DUPLICATE of bug 153411
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-12 14:52 UTC by Irene Korff
Modified: 2010-03-26 11:01 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 Irene Korff 2010-03-12 14:52:36 UTC
Application: kontact (4.4.1)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-20-generic x86_64
Distribution: Ubuntu 9.10

-- Information about the crash:
This happens after having changed the settings from displaying hidden imap directories to deselecting this option in Kmail incoming imap mail account settings. For now it seems to be solved by reselecting the option, but you apparently can't change this setting once you've selected it.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x0000000000000061 in ?? ()
#6  0x00007fa6aa0a9f41 in KMail::ISubject::notify (this=0x11b3a80) at ../../kmail/isubject.cpp:33
#7  0x00007fa6a9da50ec in KMMessage::updateBodyPart (this=0x11b39b0, partSpecifier=) at ../../kmail/kmmessage.cpp:3185
#8  0x00007fa6aa0818b9 in KMail::ImapJob::slotGetMessageResult (this=0x2a3a4a0, job=<value optimized out>) at ../../kmail/imapjob.cpp:435
#9  0x00007fa6aa08347b in KMail::ImapJob::qt_metacall (this=0x2a3a4a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd4460070) at ./imapjob.moc:88
#10 0x00007fa6c3208c0f in QMetaObject::activate (sender=0x3c0f8a0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7) at kernel/qobject.cpp:3293
#11 0x00007fa6c360eda2 in KJob::result (this=0x13eb908, _t1=0x3c0f8a0) at ./kjob.moc:194
#12 0x00007fa6c360f040 in KJob::emitResult (this=0x3c0f8a0) at ../../kdecore/jobs/kjob.cpp:312
#13 0x00007fa6c09a9853 in KIO::SimpleJob::slotFinished (this=0x3c0f8a0) at ../../kio/kio/job.cpp:486
#14 0x00007fa6c09aa217 in KIO::TransferJob::slotFinished (this=0x3c0f8a0) at ../../kio/kio/job.cpp:1058
#15 0x00007fa6c09a8191 in KIO::TransferJob::qt_metacall (this=0x3c0f8a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd4460470) at ./jobclasses.moc:367
#16 0x00007fa6c3208c0f in QMetaObject::activate (sender=0x27ceaa0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7) at kernel/qobject.cpp:3293
#17 0x00007fa6c0a68a91 in KIO::SlaveInterface::dispatch (this=0x27ceaa0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#18 0x00007fa6c0a65e03 in KIO::SlaveInterface::dispatch (this=0x27ceaa0) at ../../kio/kio/slaveinterface.cpp:91
#19 0x00007fa6c0a5a166 in KIO::Slave::gotInput (this=0x27ceaa0) at ../../kio/kio/slave.cpp:324
#20 0x00007fa6c0a5a34c in KIO::Slave::qt_metacall (this=0x27ceaa0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd4460890) at ./slave.moc:82
#21 0x00007fa6c3208c0f in QMetaObject::activate (sender=0x21fbb80, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7) at kernel/qobject.cpp:3293
#22 0x00007fa6c0978ad7 in KIO::ConnectionPrivate::dequeue (this=0x2950b30) at ../../kio/kio/connection.cpp:82
#23 0x00007fa6c0978bfd in KIO::Connection::qt_metacall (this=0x21fbb80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x210e300) at ./connection.moc:79
#24 0x00007fa6c3205b49 in QObject::event (this=0x21fbb80, e=0x3edf7d0) at kernel/qobject.cpp:1248
#25 0x00007fa6c25b012c in QApplicationPrivate::notify_helper (this=0xae6210, receiver=0x21fbb80, e=0x3edf7d0) at kernel/qapplication.cpp:4300
#26 0x00007fa6c25b671b in QApplication::notify (this=0x7fffd44613a0, receiver=0x21fbb80, e=0x3edf7d0) at kernel/qapplication.cpp:4183
#27 0x00007fa6c3be5d76 in KApplication::notify (this=0x7fffd44613a0, receiver=0x21fbb80, event=0x3edf7d0) at ../../kdeui/kernel/kapplication.cpp:302
#28 0x00007fa6c31f5e0c in QCoreApplication::notifyInternal (this=0x7fffd44613a0, receiver=0x21fbb80, event=0x3edf7d0) at kernel/qcoreapplication.cpp:704
#29 0x00007fa6c31f8587 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xabbcd0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xabbcd0) at kernel/qcoreapplication.cpp:1345
#31 0x00007fa6c321f7f3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#32 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#33 0x00007fa6ba785bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x00007fa6ba789598 in ?? () from /lib/libglib-2.0.so.0
#35 0x00007fa6ba7896c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x00007fa6c321f333 in QEventDispatcherGlib::processEvents (this=0xabb420, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#37 0x00007fa6c265ff0e in QGuiEventDispatcherGlib::processEvents (this=0x13eb908, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#38 0x00007fa6c31f4732 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#39 0x00007fa6c31f4b0c in QEventLoop::exec (this=0x7fffd44612e0, flags=) at kernel/qeventloop.cpp:201
#40 0x00007fa6c31f884b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#41 0x0000000000403ece in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

Possible duplicates by query: bug 230446, bug 230419, bug 230341, bug 230083, bug 229947.

Reported using DrKonqi
Comment 1 Christophe Marin 2010-03-26 11:01:25 UTC

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