Bug 200946 - kmail crash when opening attachment (.doc in external openoffice)
Summary: kmail crash when opening attachment (.doc in external openoffice)
Status: RESOLVED DUPLICATE of bug 188142
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-21 02:17 UTC by andrew
Modified: 2009-07-21 02:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2009-07-21 02:17:56 UTC
Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
actual mail message resides on gmail, accessed via imap.  Kmail crash caused simply by clicking on the attachment.  There are a number of possibly related bugs.  

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0xb7508a81 in KMHandleAttachmentCommand::slotStart (this=0x8e9e520) at /home/jan/kdemod/testing/kdepim/src/kdepim-4.2.96/kmail/kmcommands.cpp:2884
#7  0xb74f690b in KMHandleAttachmentCommand::qt_metacall (this=0x8e9e520, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfc0efcc)
    at /home/jan/kdemod/testing/kdepim/src/kdepim-4.2.96/kmail/kmcommands.moc:2240
#8  0xb6f8798c in QMetaObject::activate (sender=0x90999e0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#9  0xb6f885c2 in QMetaObject::activate (sender=0x90999e0, m=0xb7060ae8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#10 0xb6f8ca17 in QSingleShotTimer::timeout (this=0x90999e0) at .moc/release-shared/qtimer.moc:76
#11 0xb6f8cb2c in QSingleShotTimer::timerEvent (this=0x90999e0) at kernel/qtimer.cpp:298
#12 0xb6f81b3f in QObject::event (this=0x90999e0, e=0xbfc0f460) at kernel/qobject.cpp:1074
#13 0xb65c4694 in QApplicationPrivate::notify_helper (this=0x8741f60, receiver=0x90999e0, e=0xbfc0f460) at kernel/qapplication.cpp:4056
#14 0xb65cbd7c in QApplication::notify (this=0xbfc0f840, receiver=0x90999e0, e=0xbfc0f460) at kernel/qapplication.cpp:3603
#15 0xb7d75f0a in KApplication::notify (this=0xbfc0f840, receiver=0x90999e0, event=0xbfc0f460) at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kdeui/kernel/kapplication.cpp:302
#16 0xb6f71fab in QCoreApplication::notifyInternal (this=0xbfc0f840, receiver=0x90999e0, event=0xbfc0f460) at kernel/qcoreapplication.cpp:610
#17 0xb6f9f77e in QTimerInfoList::activateTimers (this=0x87440b4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0xb6f9c760 in timerSourceDispatch (source=0x8744080) at kernel/qeventdispatcher_glib.cpp:165
#19 0xb4638d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb463c3e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#21 0xb463c513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb6f9c6ac in QEventDispatcherGlib::processEvents (this=0x8741de0, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#23 0xb6662315 in QGuiEventDispatcherGlib::processEvents (this=0x8741de0, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#24 0xb6f70559 in QEventLoop::processEvents (this=0xbfc0f724, flags=) at kernel/qeventloop.cpp:149
#25 0xb6f709aa in QEventLoop::exec (this=0xbfc0f724, flags={i = 0}) at kernel/qeventloop.cpp:201
#26 0xb6f72e1f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0xb65c4517 in QApplication::exec () at kernel/qapplication.cpp:3525
#28 0x0804a6b2 in main (argc=3, argv=0xbfc0f9f4) at /home/jan/kdemod/testing/kdepim/src/kdepim-4.2.96/kmail/main.cpp:146

This bug may be a duplicate of or related to bug 195256

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-21 02:41:50 UTC
Merging with bug 188142. Thanks

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