Application: kontact (4.7.3) KDE Platform Version: 4.7.3 (4.7.3) Qt Version: 4.8.0 Operating System: Linux 2.6.37.6-0.9-desktop x86_64 Distribution: "openSUSE 11.4 (x86_64)" -- Information about the crash: I was replying to an email and wanted to change the account that I was sending from and that I wanted replies to be sent to. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f61233cf760 (LWP 11392))] Thread 3 (Thread 0x7f610b5c8700 (LWP 11394)): #0 0x00007f611b33638c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f611fbdcd74 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x00007f611b331a3f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f612090e66d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f610acc7700 (LWP 11395)): #0 0x00007f61209054f3 in poll () from /lib64/libc.so.6 #1 0x00007f6119fc0114 in ?? () from /lib64/libglib-2.0.so.0 #2 0x00007f6119fc0650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007f6121d403e6 in QEventDispatcherGlib::processEvents (this=0x7f61040008b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f6121d10492 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f6121d1070d in QEventLoop::exec (this=0x7f610acc6e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f6121c0e458 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:501 #7 0x00007f6121c10b4b in QThreadPrivate::start (arg=0x6469e0) at thread/qthread_unix.cpp:298 #8 0x00007f611b331a3f in start_thread () from /lib64/libpthread.so.0 #9 0x00007f612090e66d in clone () from /lib64/libc.so.6 #10 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f61233cf760 (LWP 11392)): [KCrash Handler] #6 0x00007f61212fd760 in QTextLine::cursorToX (this=0x7fffda682f70, cursorPos=0x7fffda682fa8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x00007f61212d9a41 in cursorToX (this=0x4359f30, position=<value optimized out>) at ../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x4359f30, position=<value optimized out>) at text/qtextcontrol.cpp:1369 #9 0x00007f61212dcd36 in QTextControl::ensureCursorVisible (this=<value optimized out>) at text/qtextcontrol.cpp:2953 #10 0x00007f61212e0cbf in QTextControl::setTextCursor (this=0x4359f10, cursor=<value optimized out>) at text/qtextcontrol.cpp:834 #11 0x00007f60c1e2b433 in Message::KMeditor::replaceSignature (this=0x4354d20, oldSig=..., newSig=...) at /usr/src/debug/kdepim-4.7.3/messagecomposer/kmeditor.cpp:667 #12 0x00007f60c1e169a1 in Message::ComposerViewBase::identityChanged (this=0x309cd70, ident=..., oldIdent=...) at /usr/src/debug/kdepim-4.7.3/messagecomposer/composerviewbase.cpp:1172 #13 0x00007f60c2741eb9 in KMComposeWin::slotIdentityChanged (this=0x43876c0, uoid=908515716, initalChange=false) at /usr/src/debug/kdepim-4.7.3/kmail/kmcomposewin.cpp:2788 #14 0x00007f60c274dc1e in KMComposeWin::qt_metacall (this=0x43876c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffda683760) at /usr/src/debug/kdepim-4.7.3/build/kmail/kmcomposewin.moc:263 #15 0x00007f6121d26bab in QMetaObject::activate (sender=0x394aac0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffda683760) at kernel/qobject.cpp:3574 #16 0x00007f6108aac0de in KPIMIdentities::IdentityCombo::identityChanged(unsigned int) () from /usr/lib64/libkpimidentities.so.4 #17 0x00007f6108ab88c3 in KPIMIdentities::IdentityCombo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkpimidentities.so.4 #18 0x00007f6121d26bab in QMetaObject::activate (sender=0x394aac0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffda683900) at kernel/qobject.cpp:3574 #19 0x00007f6121472a11 in QComboBox::activated (this=<value optimized out>, _t1=2) at .moc/release-shared/moc_qcombobox.cpp:288 #20 0x00007f6121472a9c in QComboBoxPrivate::emitActivated (this=<value optimized out>, index=...) at widgets/qcombobox.cpp:1261 #21 0x00007f6121473be7 in QComboBoxPrivate::_q_itemSelected (this=0x394ab10, item=...) at widgets/qcombobox.cpp:1252 #22 0x00007f6121d269ba in QMetaObject::activate (sender=0x427c160, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffda683ad0) at kernel/qobject.cpp:3555 #23 0x00007f612171ad62 in QComboBoxPrivateContainer::itemSelected (this=<value optimized out>, _t1=<value optimized out>) at .moc/release-shared/moc_qcombobox_p.cpp:253 #24 0x00007f612146dfea in QComboBoxPrivateContainer::eventFilter (this=0x427c160, o=0x309cd40, e=<value optimized out>) at widgets/qcombobox.cpp:691 #25 0x00007f6121d11547 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x309cd40, event=0x7fffda684370) at kernel/qcoreapplication.cpp:986 #26 0x00007f612108b271 in QApplicationPrivate::notify_helper (this=0x639060, receiver=0x309cd40, e=0x7fffda684370) at kernel/qapplication.cpp:4514 #27 0x00007f6121094134 in QApplication::notify (this=<value optimized out>, receiver=0x309cd40, e=0x7fffda684370) at kernel/qapplication.cpp:4061 #28 0x00007f612277dae6 in KApplication::notify (this=0x7fffda6850b0, receiver=0x309cd40, event=0x7fffda684370) at /usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kapplication.cpp:311 #29 0x00007f6121d113bc in QCoreApplication::notifyInternal (this=0x7fffda6850b0, receiver=0x309cd40, event=0x7fffda684370) at kernel/qcoreapplication.cpp:876 #30 0x00007f612108c2b5 in sendEvent (receiver=0x309cd40, event=0x7fffda684370, alienWidget=0x309cd40, nativeWidget=0x427c160, buttonDown=0x7f6121b8d258, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:231 #31 QApplicationPrivate::sendMouseEvent (receiver=0x309cd40, event=0x7fffda684370, alienWidget=0x309cd40, nativeWidget=0x427c160, buttonDown=0x7f6121b8d258, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3157 #32 0x00007f612110adb4 in QETWidget::translateMouseEvent (this=0x427c160, event=<value optimized out>) at kernel/qapplication_x11.cpp:4433 #33 0x00007f6121109239 in QApplication::x11ProcessEvent (this=0x7fffda6850b0, event=0x7fffda684cd0) at kernel/qapplication_x11.cpp:3625 #34 0x00007f6121131772 in x11EventSourceDispatch (s=0x64cc00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #35 0x00007f6119fbfbd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #36 0x00007f6119fc03b0 in ?? () from /lib64/libglib-2.0.so.0 #37 0x00007f6119fc0650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #38 0x00007f6121d4038f in QEventDispatcherGlib::processEvents (this=0x612160, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #39 0x00007f612113140e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #40 0x00007f6121d10492 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #41 0x00007f6121d1070d in QEventLoop::exec (this=0x7fffda685000, flags=...) at kernel/qeventloop.cpp:204 #42 0x00007f6121d14e5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #43 0x000000000040416f in _start () Possible duplicates by query: bug 231588. Reported using DrKonqi
Both accounts have a default signature ?
*** Bug 288466 has been marked as a duplicate of this bug. ***
Laurent, an idea maybe ? I couldn't reproduce with two accounts with two different signatures
*** Bug 289037 has been marked as a duplicate of this bug. ***
from bug 289037 -- Information about the crash: - What I was doing when the application crashed: I was trying to forward message inline form my 'Sent' folder on an IMAP server. The crash can be reproduced every time.
*** Bug 289370 has been marked as a duplicate of this bug. ***
*** Bug 289478 has been marked as a duplicate of this bug. ***
*** Bug 290651 has been marked as a duplicate of this bug. ***
Created attachment 67724 [details] New crash information added by DrKonqi kmail (4.8 rc2) on KDE Platform 4.7.98 (4.8 RC2+ (4.7.98) using Qt 4.8.0 - What I was doing when the application crashed: After sending a message I went into Sent filder, right-clicked on the just sent message and selected to Resend it This is with KMail from KDE 4.8 compiled from Git and using Qt 4.8. -- Backtrace (Reduced): #6 0x00000031dda4c896 in QTextLine::cursorToX (this=0x7fffd4b13460, cursorPos=0x7fffd4b134a8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x00000031dda298b8 in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0x7fffd4b13460) at ../../include/QtGui/../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x277fffb0, position=<optimized out>) at text/qtextcontrol.cpp:1368 #9 0x00000031dda2d1a8 in QTextControl::ensureCursorVisible (this=<optimized out>) at text/qtextcontrol.cpp:2950 #10 0x00000031dda30c1f in QTextControl::setTextCursor (this=0x106b3eb0, cursor=...) at text/qtextcontrol.cpp:833
(In reply to comment #9) > kmail (4.8 rc2) on KDE Platform 4.7.98 (4.8 RC2+ (4.7.98) using Qt 4.8.0 > > - What I was doing when the application crashed: > After sending a message I went into Sent filder, right-clicked on the just sent > message and selected to Resend it > This is with KMail from KDE 4.8 compiled from Git and using Qt 4.8. > Can't reproduce with these steps. is it an html message? does it have a signature?
It's a plain text message with a signature
*** Bug 291583 has been marked as a duplicate of this bug. ***
*** Bug 292851 has been marked as a duplicate of this bug. ***
Created attachment 68443 [details] New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0 - What I was doing when the application crashed: I tried to forward an e-mail (plain text, with signature) from an IMAP server and kmail crashed. It is always reproducible with the same set of e-mails, but with others everything is OK (I'm not able to find any patern though). -- Backtrace (Reduced): #6 0x00007fa47eaf6ab0 in QTextLine::cursorToX (this=0x7fff0dcafee0, cursorPos=0x7fff0dcaff18, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x00007fa47ead2ed1 in cursorToX (this=0x2b109f0, position=<value optimized out>) at ../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x2b109f0, position=<value optimized out>) at text/qtextcontrol.cpp:1368 #9 0x00007fa47ead61a6 in QTextControl::ensureCursorVisible (this=<value optimized out>) at text/qtextcontrol.cpp:2950 #10 0x00007fa47eada11f in QTextControl::setTextCursor (this=0x2b109d0, cursor=<value optimized out>) at text/qtextcontrol.cpp:833
Created attachment 68551 [details] New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.00 (4.8.0 "release 462" using Qt 4.8.0 - What I was doing when the application crashed: Clicked on new email, changed the account in the email editor... ...crash. reproducable. when I click restart application in dr. konqi, sometimes the email editor window is respawned additionally to kmail. then I can change the account without a crash. If I close dr. konqi and restart kmail manually, the email editor is not starting, too. then the crash is reproducable as described. -- Backtrace (Reduced): #6 0x00007fcaa2ad2c1c in QTextLine::cursorToX (this=0x7fffc01b3be0, cursorPos=0x7fffc01b3c28, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x00007fcaa2aafd8c in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0x7fffc01b3be0) at ../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x3aa5000, position=<optimized out>) at text/qtextcontrol.cpp:1368 #9 0x00007fcaa2ab35a8 in QTextControl::ensureCursorVisible (this=<optimized out>) at text/qtextcontrol.cpp:2950 #10 0x00007fcaa2ab7143 in QTextControl::setTextCursor (this=0x3aa4fe0, cursor=...) at text/qtextcontrol.cpp:833
please add valgrind log. Not necessary to add all the time the same backtrace.
Created attachment 68555 [details] valgrind log I never used valgrind before - if I did something wrong, please tell me how to use it properly.
*** Bug 293780 has been marked as a duplicate of this bug. ***
*** Bug 294222 has been marked as a duplicate of this bug. ***
Created attachment 68879 [details] valgrind log#2 It happens here, too, but I assume it is related to composer windows which I didn't close when shutting down KMail the last time. When trying to start KMail in valgrind, I can see 2 composer windows show up for a moment, but before the content of the windows is rendered (only gray window background + the title in the window decoration is rendered at this point), KMail crashes. I'm using KDE 4.8.0 here + 2 Akonadi IMAP accounts. See valgrind log#2 for more details.
(In reply to comment #20) > It happens here, too, but I assume it is related to composer windows which I > didn't close when shutting down KMail the last time. It turned out to be actually autosave related. After moving away ~/.kde/share/apps/kmail2/autosave, I was able to start KMail again. autosave contains 7 messages, all referring to the same reply I was composing previously, while 2 of them seem to have broken formatting (newline after each word in the reply). I'll try to contact a dev on IRC directly to provide the autosave messages, as I can't provide them here publicly.
*** Bug 294916 has been marked as a duplicate of this bug. ***
*** Bug 293105 has been marked as a duplicate of this bug. ***
(In reply to comment #21) > I'll try to contact a dev on IRC directly to provide the autosave messages, as > I can't provide them here publicly. As I didn't get a response back then on IRC, please provide a contact here. I still have several autosave mails backed up here which cause KMail to crash.
*** Bug 295216 has been marked as a duplicate of this bug. ***
*** Bug 296115 has been marked as a duplicate of this bug. ***
Created attachment 69869 [details] New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) "release 483" using Qt 4.8.0 - What I was doing when the application crashed: changing the sender identity. The chosen idendity doesn't have a signature, it was a html message -- Backtrace (Reduced): #6 0x00007f40f6d72c1c in QTextLine::cursorToX (this=0x7fffc5bfc370, cursorPos=0x7fffc5bfc3b8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x00007f40f6d4fd8c in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0x7fffc5bfc370) at ../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x1f7ba60, position=<optimized out>) at text/qtextcontrol.cpp:1368 #9 0x00007f40f6d535a8 in QTextControl::ensureCursorVisible (this=<optimized out>) at text/qtextcontrol.cpp:2950 #10 0x00007f40f6d57143 in QTextControl::setTextCursor (this=0x19be040, cursor=...) at text/qtextcontrol.cpp:833
I fixed a crash for me in 4.8.2/master. Not sure that all is perfect (because I just have this crash one)
Thread 1 (Thread 0xb26b4730 (LWP 7190)): [KCrash Handler] #7 0xb6c2fbe1 in QTextLine::cursorToX (this=0xbff5bdb0, cursorPos=0xbff5bdc8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #8 0xb6c0ae4a in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0xbff5bdb0) at ../../include/QtGui/../../src/gui/text/qtextlayout.h:230 #9 QTextControlPrivate::rectForPosition (this=0xa3612e0, position=585) at text/qtextcontrol.cpp:1368 #10 0xb6c0ef90 in QTextControl::ensureCursorVisible (this=0xa0fc3f8) at text/qtextcontrol.cpp:2950 #11 0xb6c131dd in QTextControl::setTextCursor (this=0xa0fc3f8, cursor=...) at text/qtextcontrol.cpp:833 #12 0xb6e7db0c in QTextEdit::setTextCursor (this=0xa4e0ed8, cursor=...) at widgets/qtextedit.cpp:805 #13 0xadebf7d4 in Message::KMeditor::replaceSignature (this=0xa4e0ed8, oldSig=..., newSig=...) at ../../messagecomposer/kmeditor.cpp:708 Here I can reduce the problem to the plain text signature. When the signature ends with a CR -> no crash, no CR -> crash The BT was generated when forwarding in text using an identity with signature: Enchant dict for "de_DE" 0x9f027f8 *** KMail got signal 11 (Exiting) *** Dead letters dumped. KCrash: Application 'kontact' crashing... When restarting kontact the dead letter opens (text only message) but the formatting is broken. It looks like the max line length is set to 16 + wordwrap + CR after each line. HTH Thorsten
I can confirm what Thorsten found out. Adding a final CR to my signature avoids the crash. Thank you Thorsten, now I have a workaround.
I can reproduce here crash. (I work on this crash from 2 days ago) not success for the moment.
*** Bug 296342 has been marked as a duplicate of this bug. ***
*** Bug 294312 has been marked as a duplicate of this bug. ***
*** Bug 295676 has been marked as a duplicate of this bug. ***
I am exposed to the same issue, when switching from an identity with a signature to an identity without. Commenting out the setTextCursor line solves the issue for me. --- kmeditor.cpp.4.8.1 2012-04-02 15:11:52.216043987 +0200 +++ kmeditor.cpp 2012-04-02 15:12:48.926043685 +0200 @@ -705,7 +705,7 @@ // Remove the old and insert the new signature cursor.removeSelectedText(); - setTextCursor( cursor ); + //setTextCursor( cursor ); newSig.insertIntoTextEdit( KPIMIdentities::Signature::AtCursor, KPIMIdentities::Signature::AddNothing, this ); found = true; However, this has surely side-effects. But at least I don't have those crashes anymore. PS: Adding a CR at the end of the signature of the first identity also resolves the issue. Thanks to those pointing that out. Could that look like an out of range cursor ?
I confirm that adding a newline at the end of every identity solved the problem for me, but this is obviously a workaround. That explains also the difficulty that someone may had to reproduce the problem: clearly it occours only with some signature structure.
could be https://bugreports.qt-project.org/browse/QTBUG-24718
Created attachment 70415 [details] New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.1 (4.8.1) "release 2" using Qt 4.8.0 - What I was doing when the application crashed: When a sent message is sought to be 'send again', kmail crashes. Thing to note is, before updating to 4.8.1 on Opensuse 12.1, (Tumbleweed) I did not hav ethis problem. Till yesterday, kmail was working for me well. The signature is same, configurtaion is same. It is triggered by the upgdated kmail, not the kmail of 4.7.x of Opensuse 12.1 -- Backtrace (Reduced): #6 0xb63d90e1 in QTextLine::cursorToX (this=0xbff01030, cursorPos=0xbff01048, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0xb63b4172 in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0xbff01030) at ../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0xa6d6e38, position=79) at text/qtextcontrol.cpp:1368 #9 0xb63b82d0 in QTextControl::ensureCursorVisible (this=0xa6d6e28) at text/qtextcontrol.cpp:2950 #10 0xb63bc52d in QTextControl::setTextCursor (this=0xa6d6e28, cursor=...) at text/qtextcontrol.cpp:833
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.