Bug 201962 - Crash when deleting emails.
Summary: Crash when deleting emails.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: disconnected IMAP (show other bugs)
Version: 1.12.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 208777 214094 238319 260255 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-30 05:51 UTC by Martial Paupe
Modified: 2012-08-19 11:07 UTC (History)
5 users (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 Martial Paupe 2009-07-30 05:51:12 UTC
Application that crashed: kontact
Version of the application: 4.3.0 rc2
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.2
Operating System: Linux 2.6.30-1-amd64 x86_64
Distribution: Debian GNU/Linux 5.0.2 (lenny)

What I was doing when the application crashed:
When I did open a link into kontact - kmail after a little while kontact crashed.

Not sure if it's reproducible.

Cheers,

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f81d7dff780 (LWP 26036))]

Thread 2 (Thread 0x7f81b968d950 (LWP 26169)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007f81d672f3e9 in QWaitConditionPrivate::wait (this=0x3217720, mutex=0x3217718, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=0x3217720, mutex=0x3217718, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f81d06fbfc4 in QHostInfoAgent::run (this=0x3217700) at kernel/qhostinfo.cpp:260
#4  0x00007f81d672e3f5 in QThreadPrivate::start (arg=0x3217700) at thread/qthread_unix.cpp:188
#5  0x00007f81cf969faa in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007f81d552129d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f81d7dff780 (LWP 26036)):
[KCrash Handler]
#5  0x0000000000000030 in ?? ()
#6  0x00007f81bf52cf5b in KMail::CachedImapJob::slotPutMessageInfoData (this=0x116a3440, job=<value optimized out>, data=...) at ../../kmail/cachedimapjob.cpp:467
#7  0x00007f81bf531a4d in KMail::CachedImapJob::qt_metacall (this=0x116a3440, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6ccd5890) at ./cachedimapjob.moc:109
#8  0x00007f81d6829602 in QMetaObject::activate (sender=0x4783a40, from_signal_index=<value optimized out>, to_signal_index=12, argv=0x0) at kernel/qobject.cpp:3112
#9  0x00007f81d6c00c91 in KJob::infoMessage (this=0x5735eb0, _t1=0x4783a40, _t2=<value optimized out>, _t3=<value optimized out>) at ./kjob.moc:202
#10 0x00007f81d4089dc7 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=<value optimized out>, msg=<value optimized out>) at ../../kio/kio/job.cpp:499
#11 0x00007f81d408d45e in KIO::SimpleJob::qt_metacall (this=0x4783a40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6ccd5a10) at ./jobclasses.moc:166
#12 0x00007f81d408d5e5 in KIO::TransferJob::qt_metacall (this=0x5735eb0, _c=18672, _id=65, _a=0x0) at ./jobclasses.moc:331
#13 0x00007f81d6829602 in QMetaObject::activate (sender=0x97600f0, from_signal_index=<value optimized out>, to_signal_index=25, argv=0x0) at kernel/qobject.cpp:3112
#14 0x00007f81d414bb05 in KIO::SlaveInterface::infoMessage (this=0x5735eb0, _t1=<value optimized out>) at ./slaveinterface.moc:281
#15 0x00007f81d414f180 in KIO::SlaveInterface::dispatch (this=0x97600f0, _cmd=26, rawdata=<value optimized out>) at ../../kio/kio/slaveinterface.cpp:294
#16 0x00007f81d414c1d2 in KIO::SlaveInterface::dispatch (this=0x97600f0) at ../../kio/kio/slaveinterface.cpp:91
#17 0x00007f81d413ec3e in KIO::Slave::gotInput (this=0x97600f0) at ../../kio/kio/slave.cpp:322
#18 0x00007f81d4140f68 in KIO::Slave::qt_metacall (this=0x97600f0, _c=QMetaObject::InvokeMetaMethod, _id=106003328, _a=0x7fff6ccd5e00) at ./slave.moc:76
#19 0x00007f81d6829602 in QMetaObject::activate (sender=0x95fcb20, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#20 0x00007f81d405c281 in KIO::ConnectionPrivate::dequeue (this=0x925e460) at ../../kio/kio/connection.cpp:82
#21 0x00007f81d405c6da in KIO::Connection::qt_metacall (this=0x95fcb20, _c=QMetaObject::InvokeMetaMethod, _id=106003328, _a=0x572ce80) at ./connection.moc:73
#22 0x00007f81d6823ee8 in QObject::event (this=0x95fcb20, e=0x15f0c260) at kernel/qobject.cpp:1110
#23 0x00007f81d5c8c7ad in QApplicationPrivate::notify_helper (this=0x1165b20, receiver=0x95fcb20, e=0x15f0c260) at kernel/qapplication.cpp:4056
#24 0x00007f81d5c9480a in QApplication::notify (this=0x7fff6ccd6960, receiver=0x95fcb20, e=0x15f0c260) at kernel/qapplication.cpp:4021
#25 0x00007f81d71aea1b in KApplication::notify (this=0x7fff6ccd6960, receiver=0x95fcb20, event=0x15f0c260) at ../../kdeui/kernel/kapplication.cpp:302
#26 0x00007f81d681449c in QCoreApplication::notifyInternal (this=0x7fff6ccd6960, receiver=0x95fcb20, event=0x15f0c260) at kernel/qcoreapplication.cpp:610
#27 0x00007f81d68150e4 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x1129170) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1129170) at kernel/qcoreapplication.cpp:1247
#29 0x00007f81d683cef3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#30 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#31 0x00007f81cfbb7f7a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0x00007f81cfbbb640 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0x00007f81cfbbb7dc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0x00007f81d683cb7f in QEventDispatcherGlib::processEvents (this=0x1128da0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#35 0x00007f81d5d235ef in QGuiEventDispatcherGlib::processEvents (this=0x5735eb0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#36 0x00007f81d6812d62 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#37 0x00007f81d6813134 in QEventLoop::exec (this=0x7fff6ccd67c0, flags=...) at kernel/qeventloop.cpp:201
#38 0x00007f81d68153a4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0x0000000000404751 in main (argc=1, argv=0x7fff6ccd6f38) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-29 03:51:36 UTC
*** Bug 208777 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Thomas 2009-11-11 14:50:58 UTC
*** Bug 214094 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2010-06-06 22:58:48 UTC
*** Bug 238319 has been marked as a duplicate of this bug. ***
Comment 4 Christian Trippe 2010-06-07 14:14:57 UTC
I wanted to add that the crash is reproducible for me in the following way mentioned in bug 238319

I deleted an email (with a large attachment  ~12 MiB ) in my trash folder which is on an disconneted imap account. Then kontact crashed. It may take some time until kontact crashes (up to ~ 1 minute). But I have tried this now 3 times and it crashes every time for me.

I am using the KDE:Unstable repo from openSUSE this means. KDE 4.5 beta 1 and kdepim from 4.4
Comment 5 Christophe Marin 2011-01-25 13:57:07 UTC
from bug 260255:

-- Information about the crash:
- What I was doing when the application crashed:
Deleting "null"-mails.

"null"-mails: mails without anycontent - the just appear (seam to me like a bug
themselves) with no subject, no date, no from....
Comment 6 Christophe Marin 2011-01-25 13:57:13 UTC
*** Bug 260255 has been marked as a duplicate of this bug. ***
Comment 7 Myriam Schweingruber 2012-08-19 11:07:05 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding