Bug 285591

Summary: Kmail crashes when double clicking and opening jpeg attachments
Product: [I don't know] kde Reporter: Vivek Umasuthan <vivekumasuthan>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: cfeck
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Vivek Umasuthan 2011-11-02 19:36:11 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-amd64 x86_64
Distribution: Debian GNU/Linux 6.0.3 (squeeze)

-- Information about the crash:
IMAP was configured to use Gmail. The e-mail contains 2 jpeg files. Doublw clicking a jpeg file and selecting 'Gwenview' crashes Kmail.

Note: This does not happen when jpeg attachments in my other mail account (IMAP to Microsoft Exchange) in the same Kmail application are opened.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently asm".
[KCrash Handler]
#5  QBasicAtomicInt::operator!= (this=0x11155f8, str=0x7f3919a5ed82 "text") at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:75
#6  QByteArray::operator= (this=0x11155f8, str=0x7f3919a5ed82 "text") at tools/qbytearray.cpp:887
#7  0x00007f391961d269 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x00007f391951c8f9 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0x00007f39197a1b48 in KMHandleAttachmentCommand::slotStart() () from /usr/lib/libkmailprivate.so.4
#10 0x00007f39197a4276 in KMHandleAttachmentCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#11 0x00007f3918d592e6 in QMetaObject::activate (sender=0x15cfbd0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x2) at kernel/qobject.cpp:3295
#12 0x00007f3918d607ef in QSingleShotTimer::timerEvent (this=0x15cfbd0) at kernel/qtimer.cpp:308
#13 0x00007f3918d55b43 in QObject::event (this=0x15cfbd0, e=0x7fff8198ff30) at kernel/qobject.cpp:1212
#14 0x00007f39180e632c in QApplicationPrivate::notify_helper (this=0x729040, receiver=0x15cfbd0, e=0x7fff8198ff30) at kernel/qapplication.cpp:4302
#15 0x00007f39180ec80b in QApplication::notify (this=0x7fff819903a0, receiver=0x15cfbd0, e=0x7fff8198ff30) at kernel/qapplication.cpp:4185
#16 0x00007f391a681796 in KApplication::notify (this=0x7fff819903a0, receiver=0x15cfbd0, event=0x7fff8198ff30) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007f3918d4609c in QCoreApplication::notifyInternal (this=0x7fff819903a0, receiver=0x15cfbd0, event=0x7fff8198ff30) at kernel/qcoreapplication.cpp:726
#18 0x00007f3918d72e72 in QCoreApplication::sendEvent (this=0x72ca30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x72ca30) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f3918d6f9c4 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f390f3286f2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f390f32c568 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f390f32c71c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007f3918d6f6b3 in QEventDispatcherGlib::processEvents (this=0x6e4840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f391819619e in QGuiEventDispatcherGlib::processEvents (this=0xfffffffffffffffe, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f3918d449c2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f3918d44d9c in QEventLoop::exec (this=0x7fff819901d0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f3918d49a2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#29 0x0000000000403462 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2011-11-02 22:11:42 UTC
KMail 1.x is no longer maintained. If this bug is reproducible with KMail 2.x, please add a comment, or report a new bug for entry "kmail2".