Version: 1.12.0 (using KDE 4.3.0) Compiler: gcc 4.3.3 Ubuntu 4.3.3-5ubuntu4 OS: Linux Installed from: Ubuntu Packages I receive the digital version of Linux Journal (large PDF files ~17MB) as attachments in my gmail account. I use kmail to read my gmail account using IMAP and when I try to download the Linux Journal PDF files it always crashes when it reaches 100% download. To reproduce: - Subscribe the digital Linux Journal using a gmail account. - Wait until you get your first issue of the magazine. - Configure kmail to access the gmail account using IMAP. - Try to download or view the PDF. - Crash....
- Can you post the backtrace of the crash ? (using the "Developer Information" tab of the crash handler dialog) You may need to install the "kdepim-dbg" package in order to get a better backtrace. Thanks
I just made an upgrage (aptitude safe-upgrade) and now is worst... now kmail crashes as soon as I press save attachment. Here is the trace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 QByteArray::operator= (this=0x9bb15b8, other=@0xbfec2dc8) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #7 0xb73fcbfb in KMMessagePart::clear (this=0x9bb15b4) at /build/buildd/kdepim-4.3.0/kmail/kmmsgpart.cpp:65 #8 0xb72d2164 in KMMessage::bodyPart (aDwBodyPart=0x0, aPart=0x9bb15b4, withBody=true) at /build/buildd/kdepim-4.3.0/kmail/kmmessage.cpp:2711 #9 0xb75b2b1a in KMHandleAttachmentCommand::slotStart (this=0x95c3ac8) at /build/buildd/kdepim-4.3.0/kmail/partNode.h:99 #10 0xb75a04e3 in KMHandleAttachmentCommand::qt_metacall (this=0x95c3ac8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfec2f28) at /build/buildd/kdepim-4.3.0/obj-i486-linux-gnu/kmail/kmcommands.moc:2240 #11 0xb5e451b8 in QMetaObject::activate (sender=0x9a64460, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #12 0xb5e45e42 in QMetaObject::activate (sender=0x9a64460, m=0xb5f21908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #13 0xb5e4af77 in QSingleShotTimer::timeout (this=0x9a64460) at .moc/release-shared/qtimer.moc:76 #14 0xb5e4b09c in QSingleShotTimer::timerEvent (this=0x9a64460) at kernel/qtimer.cpp:298 #15 0xb5e4016f in QObject::event (this=0x9a64460, e=0xbfec33ac) at kernel/qobject.cpp:1075 #16 0xb60bbd3c in QApplicationPrivate::notify_helper (this=0x84f2968, receiver=0x9a64460, e=0xbfec33ac) at kernel/qapplication.cpp:4056 #17 0xb60c403e in QApplication::notify (this=0xbfec36c8, receiver=0x9a64460, e=0xbfec33ac) at kernel/qapplication.cpp:3603 #18 0xb7dd05cd in KApplication::notify (this=0xbfec36c8, receiver=0x9a64460, event=0xbfec33ac) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302 #19 0xb5e2fbcb in QCoreApplication::notifyInternal (this=0xbfec36c8, receiver=0x9a64460, event=0xbfec33ac) at kernel/qcoreapplication.cpp:610 #20 0xb5e5ed51 in QTimerInfoList::activateTimers (this=0x857fc14) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 0xb5e5b3a0 in timerSourceDispatch (source=0x857fbe0) at kernel/qeventdispatcher_glib.cpp:165 #22 0xb4235b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb42390eb in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb4239268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb5e5b2f8 in QEventDispatcherGlib::processEvents (this=0x84c43e8, flags={i = -1075038936}) at kernel/qeventdispatcher_glib.cpp:327 #26 0xb615da75 in QGuiEventDispatcherGlib::processEvents (this=0x84c43e8, flags={i = -1075038888}) at kernel/qguieventdispatcher_glib.cpp:202 #27 0xb5e2e1fa in QEventLoop::processEvents (this=0xbfec35d0, flags={i = -1075038824}) at kernel/qeventloop.cpp:149 #28 0xb5e2e642 in QEventLoop::exec (this=0xbfec35d0, flags={i = -1075038760}) at kernel/qeventloop.cpp:201 #29 0xb5e30ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0xb60bbbb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #31 0x0804a7d0 in main (argc=0, argv=0x0) at /build/buildd/kdepim-4.3.0/kmail/main.cpp:146
*** Bug 203722 has been marked as a duplicate of this bug. ***
This could be related to bug 195683. Thanks
Bug 210298 got updated information: What I was doing when the application crashed: Clicking on one of several attached PDF files in an email crashed KMail -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QByteArray::operator= (this=0xb5f7da8, other=@0xbfd08398) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #7 0xb10b495b in KMMessagePart::clear (this=0xb5f7da4) at /build/buildd/kdepim-4.3.2/kmail/kmmsgpart.cpp:65 #8 0xb0f88794 in KMMessage::bodyPart (aDwBodyPart=0x616e090a, aPart=0xb5f7da4, withBody=true) at /build/buildd/kdepim-4.3.2/kmail/kmmessage.cpp:2712 #9 0xb126b5da in KMHandleAttachmentCommand::slotStart (this=0x941f7f8) at /build/buildd/kdepim-4.3.2/kmail/partNode.h:99
*** Bug 210298 has been marked as a duplicate of this bug. ***
*** Bug 254038 has been marked as a duplicate of this bug. ***
*** Bug 271474 has been marked as a duplicate of this bug. ***
*** Bug 272950 has been marked as a duplicate of this bug. ***
Created attachment 60687 [details] New crash information added by DrKonqi kontact (4.4.11) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.3 - What I was doing when the application crashed: crashed download big file jpeg, when downloading small files this is not observed. -- Backtrace (Reduced): #6 0x00007f80f25be483 in KMHandleAttachmentCommand::slotStart() () from /usr/lib64/libkmailprivate.so.4 #7 0x00007f80f25c0b96 in KMHandleAttachmentCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #8 0x00007f8109727abe in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f810a10ffbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #10 0x00007f810a11545d in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
*** Bug 274585 has been marked as a duplicate of this bug. ***
*** Bug 289337 has been marked as a duplicate of this bug. ***
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