Version: (using KDE KDE 3.5.8) Installed from: Gentoo Packages Compiler: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2) OS: Linux I was writing an e-mail, having composer window open then I had to switch tasks, hitting Ctrl+Q on main kmail window in error kmail closed, vanishing from the tray, but the composer window was still open immediately, I started kmail again using Alt+F2 and typing kmail then it crashed right after the main window appeared the backtrace looks very similar to bug 92737, but I did not manipulate any encrypted message (and none has arrived in my inbox meanwhile) $ kmail --version Qt: 3.3.8 KDE: 3.5.8 KMail: 1.9.7 Using host libthread_db library "/lib/libthread_db.so.1". [KCrash handler] #5 0x00002b440b473134 in KMail::ISubject::notify (this=0x1e675a8) at isubject.cpp:35 #6 0x00002b440b5a8500 in KMMessage::updateBodyPart (this=0x1e67580, partSpecifier=@0x7fff9fc29f20, data=<value optimized out>) at kmmessage.cpp:4129 #7 0x00002b440b5a8e4a in KMail::ImapJob::slotGetMessageResult ( this=0x227b330, job=<value optimized out>) at imapjob.cpp:417 #8 0x00002b440b5c487c in KMail::ImapJob::qt_invoke (this=0x227b330, _id=2, _o=0x7fff9fc2a000) at imapjob.moc:126 #9 0x00002b441199224c in QObject::activate_signal (this=0x22c86f0, clist=<value optimized out>, o=0x7fff9fc2a000) at kernel/qobject.cpp:2356 #10 0x00002b440f8ff1b5 in KIO::Job::result (this=<value optimized out>, t0=0x22c86f0) at jobclasses.moc:162 #11 0x00002b440f919dbb in KIO::Job::emitResult (this=0x22c86f0) at job.cpp:235 #12 0x00002b440f927e3c in KIO::SimpleJob::slotFinished (this=0x22c86f0) at job.cpp:601 #13 0x00002b440f93285f in KIO::TransferJob::slotFinished (this=0x22c86f0) at job.cpp:971 #14 0x00002b440f9185af in KIO::TransferJob::qt_invoke (this=0x22c86f0, _id=17, _o=0x7fff9fc2a4e0) at jobclasses.moc:1071 #15 0x00002b441199224c in QObject::activate_signal (this=0x21f9cb0, clist=<value optimized out>, o=0x7fff9fc2a4e0) at kernel/qobject.cpp:2356 #16 0x00002b4411992ef3 in QObject::activate_signal (this=0x10916f8, signal=<value optimized out>) at kernel/qobject.cpp:2325 #17 0x00002b440f9294bb in KIO::SlaveInterface::dispatch (this=0x21f9cb0, _cmd=104, rawdata=@0x7fff9fc2a820) at slaveinterface.cpp:243 #18 0x00002b440f919900 in KIO::SlaveInterface::dispatch (this=0x21f9cb0) at slaveinterface.cpp:173 #19 0x00002b440f90eadd in KIO::Slave::gotInput (this=0x21f9cb0) at slave.cpp:300 #20 0x00002b440f92ba5d in KIO::Slave::qt_invoke (this=0x21f9cb0, _id=4, _o=0x7fff9fc2a970) at slave.moc:113 #21 0x00002b441199224c in QObject::activate_signal (this=0x2175cb0, clist=<value optimized out>, o=0x7fff9fc2a970) at kernel/qobject.cpp:2356 #22 0x00002b4411992e25 in QObject::activate_signal (this=0x2175cb0, signal=<value optimized out>, param=<value optimized out>) at kernel/qobject.cpp:2449 #23 0x00002b44119ac95b in QSocketNotifier::event (this=0x2175cb0, e=0x7fff9fc2ac60) at kernel/qsocketnotifier.cpp:258 #24 0x00002b441193bcb5 in QApplication::internalNotify ( this=<value optimized out>, receiver=0x2175cb0, e=0x7fff9fc2ac60) at kernel/qapplication.cpp:2635 #25 0x00002b441193c8b7 in QApplication::notify (this=0x7fff9fc2aea0, receiver=0x2175cb0, e=0x7fff9fc2ac60) at kernel/qapplication.cpp:2358 #26 0x00002b441086efea in KApplication::notify (this=0x7fff9fc2aea0, receiver=0x2175cb0, event=0x7fff9fc2ac60) at kapplication.cpp:550 #27 0x00002b4411931e9b in QEventLoop::activateSocketNotifiers (this=0x667480) at kernel/qapplication.h:496 #28 0x00002b44118f2bd3 in QEventLoop::processEvents (this=0x667480, flags=<value optimized out>) at kernel/qeventloop_x11.cpp:383 #29 0x00002b4411950402 in QEventLoop::enterLoop (this=0x10916f8) at kernel/qeventloop.cpp:198 #30 0x00002b44119502b2 in QEventLoop::exec (this=0x10916f8) at kernel/qeventloop.cpp:145 #31 0x0000000000403592 in main (argc=<value optimized out>, argv=<value optimized out>) at main.cpp:110 #32 0x00002b4414adfb74 in __libc_start_main () from /lib/libc.so.6 #33 0x00000000004033d9 in _start ()
*** Bug 154140 has been marked as a duplicate of this bug. ***
I cannot reproduce on 1.9.9 (KDE 3.5.9) and KDE4 (current trunk). @Kavol: Are you able to reproduce it again using a more recent version? Thanks a lot!
I just tried 1.9.9 on KDE 3.5.9 and it did not crash but as I remember, this was not cleanly reproducible even with the old version ... the backtrace is not enough to debug? as bug #154140 is marked as duplicate, it looks like the restart of kmail is not the trigerring point hm, what to do to discover where the devil lies?
*** Bug 162610 has been marked as a duplicate of this bug. ***
*** Bug 167829 has been marked as a duplicate of this bug. ***
*** Bug 168811 has been marked as a duplicate of this bug. ***
*** Bug 174311 has been marked as a duplicate of this bug. ***
*** Bug 172792 has been marked as a duplicate of this bug. ***
*** Bug 178050 has been marked as a duplicate of this bug. ***
*** Bug 180934 has been marked as a duplicate of this bug. ***
*** Bug 181267 has been marked as a duplicate of this bug. ***
I can not reproduce on 1.9.10.
@kavol: Are you able to reproduce this in latest version?
(In reply to comment #13) > @kavol: Are you able to reproduce this in latest version? well, I don't remember 1.9.10 crashing on anything so far ... the situation described within the first comment does not lead to crash even after several retries ... however, on KDE 4 machine, currently running kmail 1.11.1, I have experienced several crashes; unfortunately, no backtrace available to compare with this
(In reply to comment #14) > well, I don't remember 1.9.10 crashing on anything so far ... the situation > described within the first comment does not lead to crash even after several > retries ... however, on KDE 4 machine, currently running kmail 1.11.1, I have > experienced several crashes; unfortunately, no backtrace available to compare > with this You mean you are not able to get backtrace with debug symbols or the one you get is not same as this one. I suggest if you can not reproduce this particular bug then close it. If you can't get back trace, try again after installing debuginfo packages for kdepim4 and kdepimlibs4 and post the backtrace.
Well as no one is able to reproduce the bug, I'm closing this bug for now. Regarding kde4 bugs, please report each different backtrace in separate bug. Please refer following URL to generate useful backtraces. http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
@mcguire: After updating this bug, I saw Blauzahl's comment on bugday page. ** Ask McGuire, he seems to have dup'd some to this "recently". And there are lots of dups, one suggests a race condition --- so this might be a heisenbug? [[User:Blauzahl|Blauzahl]] Can you please let me know if any change required to this report?
*** Bug 197131 has been marked as a duplicate of this bug. ***
BT from #197131: Thread 1 (Thread 0xb38bea10 (LWP 7245)): [KCrash Handler] #6 0xb75201f1 in KMail::ISubject::notify (this=0x905d048) at /usr/src/debug/kdepim-4.2.90/kmail/isubject.cpp:29 #7 0xb71c30de in KMMessage::updateBodyPart (this=0x905cfd8, partSpecifier= {static null = {<No data fields>}, static shared_null = {ref = {_q_value = 107899}, alloc = 0, size = 0, data = 0xb69f147a, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, static shared_empty = {ref = {_q_value = 5946}, alloc = 0, size = 0, data = 0xb69f148e, clean = 1, simpletext = 1, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d = 0xbfd3bc5c, static codecForCStrings = 0x0}, data=@0x8276c00) at /usr/src/debug/kdepim-4.2.90/kmail/kmmessage.cpp:3197 #8 0xb74f28c7 in KMail::ImapJob::slotGetMessageResult (this=0x8f4ace8, job=0x82aae48) at /usr/src/debug/kdepim-4.2.90/kmail/imapjob.cpp:435 #9 0xb74f6f54 in KMail::ImapJob::qt_metacall (this=0x8f4ace8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd3bd6c) at /usr/src/debug/kdepim-4.2.90/build/kmail/imapjob.moc:82 #10 0xb690fdc8 in QMetaObject::activate (sender=0x82aae48, from_signal_index=7, to_signal_index=7, argv=0xbfd3bd6c) at kernel/qobject.cpp:3120 #11 0xb6911552 in QMetaObject::activate (sender=0x82aae48, m=0xb7b35da8, local_signal_index=3, argv=0xbfd3bd6c) at kernel/qobject.cpp:3194
*** Bug 201174 has been marked as a duplicate of this bug. ***
*** Bug 204185 has been marked as a duplicate of this bug. ***
*** Bug 204876 has been marked as a duplicate of this bug. ***
SVN commit 1021457 by tnyblom: Crash guard. Should fix the symptoms in bug 153411, but it's not the cure. The null consumer should not be there at all. CCBUG: 153411 M +6 -1 isubject.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1021457
*** Bug 209926 has been marked as a duplicate of this bug. ***
Bug 210369 got another testcase: -- What I was doing when the application crashed: after a fresh restart of KMail i seem to have hit the same crash as in bug #153411. here were the steps i took: 1. quit KMail 2. start KMail 3. open KMail from the system tray (by clicking on it twice, which it always requires on the first time around for some reason) 4. click my (IMAP) inbox 5. see the "retrieving messages" page for longer than usual; click my inbox again 6. crash KWallet was not open during this process, nor did KMail as it to be opened like it usually does.
*** Bug 210369 has been marked as a duplicate of this bug. ***
*** Bug 211043 has been marked as a duplicate of this bug. ***
*** Bug 212102 has been marked as a duplicate of this bug. ***
*** Bug 213989 has been marked as a duplicate of this bug. ***
*** Bug 213510 has been marked as a duplicate of this bug. ***
*** Bug 213961 has been marked as a duplicate of this bug. ***
From bug 214333: --- What I was doing when the application crashed: i was just looking at some mail thats on the gmail server and when i clicked to retrieve the mail kmail suddenly crashed with a segment fault ,, this has happened before with other actions like attaching photos to emails etc etc and always is a segment fault ,this time i got the proper debugging packages to a proper report
*** Bug 214333 has been marked as a duplicate of this bug. ***
From bug 216886: --- What I was doing when the application crashed: I was trying to load a message from my GMail account's All Mail folder via IMAP. I had previously selected a message in the same thread to view in the preview pane, and that never loaded, then I set KMail to show the preview pane next to the message list, then tried to select the message after which KMail segfaulted. --- From bug 217629: --- What I was doing when the application crashed: kmail crashes when closing application using the X icon
*** Bug 216401 has been marked as a duplicate of this bug. ***
*** Bug 216886 has been marked as a duplicate of this bug. ***
*** Bug 217629 has been marked as a duplicate of this bug. ***
From bug 218645: --- What I was doing when the application crashed: Kmail crashed after closing the preference dialog and selected a mail in the inbox folder for display. The preference dialog was used to change the layout and hide the favorite folders list.
*** Bug 218645 has been marked as a duplicate of this bug. ***
*** Bug 218794 has been marked as a duplicate of this bug. ***
From bug 220802: --- What I was doing when the application crashed: I am able to reproduce it (at least one of 3 attempts is successful - makes KMail crashed). How to reproduce it: launch KMail, click on New..., write an e-mail address into a recipient field, close only the main KMail window (keep the message open), launch KMail and quickly click on an inbox folder (I have to open the inbox folder of my first account.). When it opens, KMail crashes. -- Backtrace: [KCrash Handler] #5 0x00007fdda99906d6 in KMail::ISubject::notify (this=0x1569d10) at ../../kmail/isubject.cpp:30 #6 0x00007fdda967beec in KMMessage::updateBodyPart (this=0x1569c40, partSpecifier=) at ../../kmail/kmmessage.cpp:3235 #7 0x00007fdda9964bca in KMail::ImapJob::slotGetMessageResult (this=0x2118610, job=<value optimized out>) at ../../kmail/imapjob.cpp:435 #8 0x00007fdda996904b in KMail::ImapJob::qt_metacall (this=0x2118610, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff114cc5a0) at ./imapjob.moc:82 ...
*** Bug 220802 has been marked as a duplicate of this bug. ***
From bug 221559: --- I don't know whether this is reproducible. I did this: 1. Add a new IMAP account (this account has dozens of folders and tens or maybe a hundred thousand messages) 2. While kmail was reading message information, I opened the settings dialog 3. Changed folder list to "short", press "apply" 4. Changed folder list back to "long", press "apply" 5. Crash
*** Bug 221559 has been marked as a duplicate of this bug. ***
*** Bug 224238 has been marked as a duplicate of this bug. ***
*** Bug 230452 has been marked as a duplicate of this bug. ***
*** Bug 229106 has been marked as a duplicate of this bug. ***
*** Bug 225291 has been marked as a duplicate of this bug. ***
*** Bug 238929 has been marked as a duplicate of this bug. ***
*** Bug 238427 has been marked as a duplicate of this bug. ***
*** Bug 237911 has been marked as a duplicate of this bug. ***
*** Bug 237422 has been marked as a duplicate of this bug. ***
*** Bug 237549 has been marked as a duplicate of this bug. ***
Created attachment 48045 [details] New crash information added by DrKonqi kmail crashed while changing folder list style from long to short style.
*** Bug 241900 has been marked as a duplicate of this bug. ***
*** Bug 243308 has been marked as a duplicate of this bug. ***
Created attachment 48703 [details] New crash information added by DrKonqi Console output of kmail: kmail(3175)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" kmail(3175)/kdeui (KIconEffect) KIconEffect::overlay: Image depth src ( 0 ) != overlay ( 32 )! kmail(3175)/kdeui (KIconEffect) KIconEffect::overlay: Image depth src ( 0 ) != overlay ( 32 )! kmail(3175)/kdeui (KIconEffect) KIconEffect::overlay: Image depth src ( 0 ) != overlay ( 32 )! kmail(3175)/kdeui (KIconEffect) KIconEffect::overlay: Image depth src ( 0 ) != overlay ( 32 )! kmail(3175)/kio (Slave) KIO::Slave::createSlave: createSlave "file" for KUrl("file:///usr/share/apps/kdeui/about/body-background.png") kmail(3175)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-dan/kmailOe3175.slave-socket" kmail(3175)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("imaps://daniel@community.cacert.org:993/INBOX.dev-security-policy/;UID=862;SECTION=BODY.PEEK[TEXT]") data size = 1975 kmail(3175)/kparts KParts::Part::slotWidgetDestroyed: deleting part "mViewer" kmail(3175)/khtml (part) KHTMLPart::~KHTMLPart: KHTMLPart(0x21d0a90, name = "mViewer") kmail(3175)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail(3175)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("imaps://daniel@community.cacert.org:993/INBOX.dev-security-policy/;UID=861;SECTION=BODY.PEEK[TEXT]") data size = 2107 *** KMail got signal 11 (Crashing) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 3175 sock_file=/home/dan/.kde4/socket-passivegrunt/kdeinit4__0
*** Bug 244552 has been marked as a duplicate of this bug. ***
*** Bug 246109 has been marked as a duplicate of this bug. ***
*** Bug 244638 has been marked as a duplicate of this bug. ***
*** Bug 245783 has been marked as a duplicate of this bug. ***
*** Bug 250929 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] This is still happening with kdepimlibs 4.4.8 according to bug 259174: [KCrash Handler] #6 0x00000038ee834085 in raise () from /lib64/libc.so.6 #7 0x00000038ee835a36 in abort () from /lib64/libc.so.6 #8 0x00000038f38bc08d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93 #9 0x00000038f38ba2a6 in __cxxabiv1::__terminate (handler=<value optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39 #10 0x00000038f38ba2d3 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49 #11 0x00000038f38bac2f in __cxxabiv1::__cxa_pure_virtual () at ../../../../libstdc++-v3/libsupc++/pure.cc:50 #12 0x0000003c39badd71 in KMail::ISubject::notify (this=0x535a070) at /usr/src/debug/kdepim-4.4.8/kmail/isubject.cpp:33 #13 0x0000003c39902613 in KMMessage::updateBodyPart (this=0x5359fa0, partSpecifier=..., data=<value optimized out>) at /usr/src/debug/kdepim-4.4.8/kmail/kmmessage.cpp:3185 #14 0x0000003c39b8860c in KMail::ImapJob::slotGetMessageResult (this=0x2b348b0, job=<value optimized out>) at /usr/src/debug/kdepim-4.4.8/kmail/imapjob.cpp:435 #15 0x0000003c39b8c79b in KMail::ImapJob::qt_metacall (this=0x2b348b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7b396c60) at /usr/src/debug/kdepim-4.4.8/x86_64-redhat-linux-gnu/kmail/imapjob.moc:88 From bug 259476: KMail crashed after first run without adding a new account From bug 256581: -- Information about the crash: I was changing some settings while i had a reply message window open and main window open. I changed some template settings and after that experimented with window layout settings. After hitting 'Apply' kmail crashed. From bug 255557: -- Information about the crash: KMail had been closed for some time (>1 hour); have noticed before that it can hang around (zombie?). Hanging around may be related to some 'notifier' functionality. Anyway, sometime after this interval some mail arrived in my gmail account and KMail crashed. From bug 255410: - What I was doing when the application crashed: I changed the view layout to have the mail preview besides the list of emails. After hitting apply kontact crashed.
*** Bug 259476 has been marked as a duplicate of this bug. ***
*** Bug 259174 has been marked as a duplicate of this bug. ***
*** Bug 255557 has been marked as a duplicate of this bug. ***
*** Bug 255410 has been marked as a duplicate of this bug. ***
*** Bug 253293 has been marked as a duplicate of this bug. ***
*** Bug 266077 has been marked as a duplicate of this bug. ***
*** Bug 263387 has been marked as a duplicate of this bug. ***
*** Bug 256581 has been marked as a duplicate of this bug. ***
*** Bug 266639 has been marked as a duplicate of this bug. ***
*** Bug 270126 has been marked as a duplicate of this bug. ***
Cannot reproduce with KMail2. Closing.
*** Bug 268982 has been marked as a duplicate of this bug. ***
*** Bug 267768 has been marked as a duplicate of this bug. ***
*** Bug 272291 has been marked as a duplicate of this bug. ***
*** Bug 273179 has been marked as a duplicate of this bug. ***
*** Bug 274259 has been marked as a duplicate of this bug. ***
*** Bug 275239 has been marked as a duplicate of this bug. ***
*** Bug 276031 has been marked as a duplicate of this bug. ***
*** Bug 277065 has been marked as a duplicate of this bug. ***
Clearing the CC list. The issue is fixed in kdepim > 4.6
*** Bug 281864 has been marked as a duplicate of this bug. ***
*** Bug 282423 has been marked as a duplicate of this bug. ***
*** Bug 282886 has been marked as a duplicate of this bug. ***
*** Bug 284083 has been marked as a duplicate of this bug. ***
*** Bug 286204 has been marked as a duplicate of this bug. ***