Bug 242241

Summary: KMail crashes when you click the attachment
Product: [Unmaintained] kmail Reporter: Styopa Semenukha <semenukha+kdebugs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: bjoern
Priority: NOR    
Version: 1.13.3   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Styopa Semenukha 2010-06-20 11:18:18 UTC
Application: kmail (1.13.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-gcc44 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
I got a new email with a big attachment to my IMAP account. When I selected the message, it was shown in the Reading panel and the progress indicator in the status bar began to run. While it was running, I clicked the attachment to download it, and KMail crashed.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently asm".
[KCrash Handler]
#5  QBasicAtomicInt::deref (this=0x1bcd390, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133
#6  QByteArray::operator= (this=0x1bcd390, other=...) at tools/qbytearray.cpp:865
#7  0x00007f333c7e55ca in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x00007f333c6e5639 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0x00007f333c96a698 in KMHandleAttachmentCommand::slotStart() () from /usr/lib/libkmailprivate.so.4
#10 0x00007f333c96cab6 in KMHandleAttachmentCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#11 0x00007f333bf21346 in QMetaObject::activate (sender=0x1ad30f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xffffffffffd4a164) at kernel/qobject.cpp:3295
#12 0x00007f333bf2884f in QSingleShotTimer::timerEvent (this=0x1ad30f0) at kernel/qtimer.cpp:308
#13 0x00007f333bf1dba3 in QObject::event (this=0x1ad30f0, e=0x7fff667b5dd0) at kernel/qobject.cpp:1212
#14 0x00007f333b2ae32c in QApplicationPrivate::notify_helper (this=0x10c7fa0, receiver=0x1ad30f0, e=0x7fff667b5dd0) at kernel/qapplication.cpp:4302
#15 0x00007f333b2b480b in QApplication::notify (this=0x7fff667b6240, receiver=0x1ad30f0, e=0x7fff667b5dd0) at kernel/qapplication.cpp:4185
#16 0x00007f333d84a436 in KApplication::notify (this=0x7fff667b6240, receiver=0x1ad30f0, event=0x7fff667b5dd0) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007f333bf0e15c in QCoreApplication::notifyInternal (this=0x7fff667b6240, receiver=0x1ad30f0, event=0x7fff667b5dd0) at kernel/qcoreapplication.cpp:726
#18 0x00007f333bf3aed2 in QCoreApplication::sendEvent (this=0x10cb8e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x10cb8e0) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f333bf37a24 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f33324f76c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f33324fb538 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f33324fb6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007f333bf37713 in QEventDispatcherGlib::processEvents (this=0x1083840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f333b35e14e in QGuiEventDispatcherGlib::processEvents (this=0x1bcd390, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f333bf0ca82 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f333bf0ce5c in QEventLoop::exec (this=0x7fff667b6070, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f333bf11aeb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#29 0x0000000000403462 in _start ()

This bug may be a duplicate of or related to bug 188142.

Possible duplicates by query: bug 232039.

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-08-08 01:43:32 UTC

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