Bug 252704 - Kmail Crashed with insert of image
Summary: Kmail Crashed with insert of image
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-29 02:48 UTC by Adam Drake
Modified: 2010-11-20 17:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.16 KB, text/plain)
2010-10-17 11:07 UTC, linuxboy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Drake 2010-09-29 02:48:34 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.34.7-56.fc13.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Copied a *.jpg image from Firefox and attempted to paste it into a new Kmail e-mail.  Kmail went down hard immediately.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  QMimeData::hasImage (this=0x1c72110) at kernel/qmimedata.cpp:470
#6  0x00000035ec40b318 in KPIMTextEdit::TextEdit::insertFromMimeData (this=0x1c4e0f0, source=0x1c72110) at /usr/src/debug/kdepimlibs-4.4.5/kpimtextedit/textedit.cpp:546
#7  0x00000035ef9a8d1d in KMComposerEditor::insertFromMimeData (this=0x1c4e0f0, source=0x1c72110) at /usr/src/debug/kdepim-4.4.6/kmail/kmcomposereditor.cpp:172
#8  0x00000030e93daa24 in QTextControl::qt_metacall (this=0x1c533c0, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0x7ffffe600f20) at .moc/release-shared/moc_qtextcontrol_p.cpp:173
#9  0x00000030e7966a36 in QMetaObject::activate (sender=0x25ba2b0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7ffffe600f20) at kernel/qobject.cpp:3295
#10 0x00000030e91a6422 in QAction::triggered (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#11 0x00000030e91a7b5b in QAction::activate (this=0x25ba2b0, event=<value optimized out>) at kernel/qaction.cpp:1255
#12 0x00000030e95ac9e9 in QMenuPrivate::activateCausedStack (this=0x25bf740, causedStack=..., action=0x25ba2b0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1002
#13 0x00000030e95b1dda in QMenuPrivate::activateAction (this=0x25bf740, action=0x25ba2b0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1094
#14 0x00000030e91f648a in QWidget::event (this=0x1eba6e0, event=0x7ffffe6019d0) at kernel/qwidget.cpp:8044
#15 0x00000030e95b3ddb in QMenu::event (this=0x1eba6e0, e=0x7ffffe6019d0) at widgets/qmenu.cpp:2421
#16 0x00000030e91ab39c in QApplicationPrivate::notify_helper (this=0x1141600, receiver=0x1eba6e0, e=0x7ffffe6019d0) at kernel/qapplication.cpp:4306
#17 0x00000030e91b1e2d in QApplication::notify (this=<value optimized out>, receiver=0x1eba6e0, e=0x7ffffe6019d0) at kernel/qapplication.cpp:3871
#18 0x00000035e6007016 in KApplication::notify (this=0x7ffffe603ec0, receiver=0x1eba6e0, event=0x7ffffe6019d0) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#19 0x00000030e7953ddc in QCoreApplication::notifyInternal (this=0x7ffffe603ec0, receiver=0x1eba6e0, event=0x7ffffe6019d0) at kernel/qcoreapplication.cpp:726
#20 0x00000030e91b101e in sendEvent (receiver=0x1eba6e0, event=0x7ffffe6019d0, alienWidget=0x0, nativeWidget=0x1eba6e0, buttonDown=0x30e9c2f088, lastMouseReceiver=..., spontaneous=true)
    at ../../src/corelib/kernel/qcoreapplication.h:215
#21 QApplicationPrivate::sendMouseEvent (receiver=0x1eba6e0, event=0x7ffffe6019d0, alienWidget=0x0, nativeWidget=0x1eba6e0, buttonDown=0x30e9c2f088, lastMouseReceiver=..., spontaneous=true)
    at kernel/qapplication.cpp:2971
#22 0x00000030e92235cd in QETWidget::translateMouseEvent (this=0x1eba6e0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4314
#23 0x00000030e9221acc in QApplication::x11ProcessEvent (this=0x7ffffe603ec0, event=0x7ffffe6022f0) at kernel/qapplication_x11.cpp:3513
#24 0x00000030e924ab92 in x11EventSourceDispatch (s=0x1144f50, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#25 0x0000003736c3bd02 in g_main_dispatch (context=0x1143d20) at gmain.c:1960
#26 IA__g_main_context_dispatch (context=0x1143d20) at gmain.c:2513
#27 0x0000003736c3fae8 in g_main_context_iterate (context=0x1143d20, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#28 0x0000003736c3fc9c in IA__g_main_context_iteration (context=0x1143d20, may_block=1) at gmain.c:2654
#29 0x00000030e7979863 in QEventDispatcherGlib::processEvents (this=0x10f6840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#30 0x00000030e924a84e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00000030e7952822 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00000030e7952aec in QEventLoop::exec (this=0x7ffffe602620, flags=...) at kernel/qeventloop.cpp:201
#33 0x00000030e95af515 in QMenu::exec (this=0x1eba6e0, p=<value optimized out>, action=0x0) at widgets/qmenu.cpp:2063
#34 0x00000035e60f1d82 in KTextEdit::contextMenuEvent (this=<value optimized out>, event=0x7ffffe603070) at /usr/src/debug/kdelibs-4.4.5/kdeui/widgets/ktextedit.cpp:616
#35 0x00000030e91f5e70 in QWidget::event (this=0x1c4e0f0, event=0x7ffffe603070) at kernel/qwidget.cpp:8211
#36 0x00000030e95730c6 in QFrame::event (this=0x1c4e0f0, e=0x7ffffe603070) at widgets/qframe.cpp:557
#37 0x00000030e79531f7 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x1c4da90, event=0x7ffffe603070) at kernel/qcoreapplication.cpp:841
#38 0x00000030e91ab36c in QApplicationPrivate::notify_helper (this=0x1141600, receiver=0x1c4da90, e=0x7ffffe603070) at kernel/qapplication.cpp:4302
#39 0x00000030e91b181e in QApplication::notify (this=<value optimized out>, receiver=0x1c4da90, e=0x7ffffe603070) at kernel/qapplication.cpp:3950
#40 0x00000035e6007016 in KApplication::notify (this=0x7ffffe603ec0, receiver=0x1c4da90, event=0x7ffffe603070) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#41 0x00000030e7953ddc in QCoreApplication::notifyInternal (this=0x7ffffe603ec0, receiver=0x1c4da90, event=0x7ffffe603070) at kernel/qcoreapplication.cpp:726
#42 0x00000030e92231a2 in QETWidget::translateMouseEvent (this=<value optimized out>, event=<value optimized out>) at kernel/qapplication_x11.cpp:4385
#43 0x00000030e9221acc in QApplication::x11ProcessEvent (this=0x7ffffe603ec0, event=0x7ffffe6039c0) at kernel/qapplication_x11.cpp:3513
#44 0x00000030e924ab92 in x11EventSourceDispatch (s=0x1144f50, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#45 0x0000003736c3bd02 in g_main_dispatch (context=0x1143d20) at gmain.c:1960
#46 IA__g_main_context_dispatch (context=0x1143d20) at gmain.c:2513
#47 0x0000003736c3fae8 in g_main_context_iterate (context=0x1143d20, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#48 0x0000003736c3fc9c in IA__g_main_context_iteration (context=0x1143d20, may_block=1) at gmain.c:2654
#49 0x00000030e7979863 in QEventDispatcherGlib::processEvents (this=0x10f6840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#50 0x00000030e924a84e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#51 0x00000030e7952822 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#52 0x00000030e7952aec in QEventLoop::exec (this=0x7ffffe603cf0, flags=...) at kernel/qeventloop.cpp:201
#53 0x00000030e79561bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#54 0x0000000000403322 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.4.6/kmail/main.cpp:156

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

Possible duplicates by query: bug 252039, bug 249882, bug 246657, bug 244195, bug 238178.

Reported using DrKonqi
Comment 1 Laurent Montel 2010-09-29 15:05:23 UTC
Ok I can reproduce this crash.
We must change to html email and paste as image and not as attachment.
Will look at why it crashs
Comment 2 Laurent Montel 2010-09-29 17:45:53 UTC
SVN commit 1180967 by mlaurent:

Fix Bug 252704 -  Kmail Crashed with insert of image  
processes events which can delete the QMimeData object when we can menu

BUG: 252704


 M  +1 -1      CMakeLists.txt  
 M  +7 -2      kpimtextedit/textedit.cpp  
 M  +5 -2      kpimtextedit/textedit.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1180967
Comment 3 Laurent Montel 2010-09-29 17:46:19 UTC
SVN commit 1180968 by mlaurent:

Fix Bug 252704 -  Kmail Crashed with insert of image  
processes events which can delete the QMimeData object when we can menu

BUG: 252704


 M  +10 -7     kmcomposereditor.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1180968
Comment 4 linuxboy 2010-10-17 11:07:03 UTC
Created attachment 52594 [details]
New crash information added by DrKonqi

kmail (1.13.5) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

The bug persists into KUBUNTU 10.10, KDE 4.5.1, KMAIL 1.13.5

-- Backtrace (Reduced):
#8  0x009fe37b in QMimeData::hasImage (this=0xa270dc8) at kernel/qmimedata.cpp:470
#9  0x0192d420 in KPIMTextEdit::TextEdit::insertFromMimeData (this=0xa358f60, source=0xa270dc8) at ../../kpimtextedit/textedit.cpp:565
#10 0x01373e70 in KMComposerEditor::insertFromMimeData (this=0xa358f60, source=0xa270dc8) at ../../kmail/kmcomposereditor.cpp:172
#11 0x0445e60b in QTextEditControl::insertFromMimeData (this=0x9f6f228, source=0xa270dc8) at widgets/qtextedit.cpp:104
#12 0x041e043e in QTextControl::paste (this=0x9f6f228, mode=QClipboard::Clipboard) at text/qtextcontrol.cpp:863
Comment 5 Laurent Montel 2010-10-17 14:47:36 UTC
in kubuntu 10.10 there is not fix...
Comment 6 Dario Andres 2010-11-20 17:20:52 UTC
[Comment from a bug triager]
Just for information purposes, the commit described in this bug report also closed the bug in bug 219959. Considering that report is older and as it has more information on it; I would suggest to mark this report as a duplicate of that one.
Regards
.