Bug 195997

Summary: Kontact crashes when I try to open and PDF attachment
Product: [Applications] kontact Reporter: Rico Zienke <zonken>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rico Zienke 2009-06-11 11:14:44 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Hi,
I have an IMAP-account and using kmail (kontact).
I just received an email in my inbox with an attachment.

When I click on the attachment link inside the email (I did not open the email) I get following crash.
Best Regards Rico

Anwendung: Kontact (kontact), Signal SIGSEGV
[Current thread is 0 (LWP 3686)]

Thread 2 (Thread 0xace38b90 (LWP 6720)):
#0  0xb80d9430 in __kernel_vsyscall ()
#1  0xb5a357b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5d09380 in QProcessManager::run (this=0xa05bc00) at io/qprocess_unix.cpp:305
#3  0xb5c3796e in QThreadPrivate::start (arg=0xa05bc00) at thread/qthread_unix.cpp:189
#4  0xb522e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5a3d49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4948700 (LWP 3686)):
[KCrash Handler]
#6  0xb1151b11 in KMHandleAttachmentCommand::slotStart (this=0xb7380f0) at /build/buildd/kdepim-4.2.2/kmail/kmcommands.cpp:2869
#7  0xb113ff23 in KMHandleAttachmentCommand::qt_metacall (this=0xb7380f0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfff67d8)
    at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:2240
#8  0xb5d41ca8 in QMetaObject::activate (sender=0xb09ad80, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#9  0xb5d42932 in QMetaObject::activate (sender=0xb09ad80, m=0xb5e1d908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#10 0xb5d470a7 in QSingleShotTimer::timeout (this=0xb09ad80) at .moc/release-shared/qtimer.moc:76
#11 0xb5d471cc in QSingleShotTimer::timerEvent (this=0xb09ad80) at kernel/qtimer.cpp:298
#12 0xb5d3c15f in QObject::event (this=0xb09ad80, e=0xbfff6c5c) at kernel/qobject.cpp:1082
#13 0xb61fce9c in QApplicationPrivate::notify_helper (this=0xa070bb8, receiver=0xb09ad80, e=0xbfff6c5c) at kernel/qapplication.cpp:4084
#14 0xb620519e in QApplication::notify (this=0xbfff6f08, receiver=0xb09ad80, e=0xbfff6c5c) at kernel/qapplication.cpp:3631
#15 0xb6e2094d in KApplication::notify (this=0xbfff6f08, receiver=0xb09ad80, event=0xbfff6c5c) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#16 0xb5d2ba3b in QCoreApplication::notifyInternal (this=0xbfff6f08, receiver=0xb09ad80, event=0xbfff6c5c) at kernel/qcoreapplication.cpp:602
#17 0xb5d5ad71 in QTimerInfoList::activateTimers (this=0xa05b834) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0xb5d574e0 in timerSourceDispatch (source=0xa05b800) at kernel/qeventdispatcher_glib.cpp:164
#19 0xb4dfeb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb4e020eb in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb4e02268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb5d57438 in QEventDispatcherGlib::processEvents (this=0xa040238, flags={i = -1073779240}) at kernel/qeventdispatcher_glib.cpp:323
#23 0xb629e365 in QGuiEventDispatcherGlib::processEvents (this=0xa040238, flags={i = -1073779192}) at kernel/qguieventdispatcher_glib.cpp:202
#24 0xb5d2a06a in QEventLoop::processEvents (this=0xbfff6e80, flags={i = -1073779128}) at kernel/qeventloop.cpp:149
#25 0xb5d2a4aa in QEventLoop::exec (this=0xbfff6e80, flags={i = -1073779064}) at kernel/qeventloop.cpp:200
#26 0xb5d2c959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#27 0xb61fcd17 in QApplication::exec () at kernel/qapplication.cpp:3553
#28 0x0804c072 in main (argc=1, argv=0xbfff7204) at /build/buildd/kdepim-4.2.2/kontact/src/main.cpp:218
Comment 1 Dario Andres 2009-06-12 00:41:23 UTC
Thanks!

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