Bug 153139

Summary:	Crash when editing .cfm attachment in composer
Product:	[Unmaintained] kmail	Reporter:	thomas klein <tma.klein>
Component:	composer	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED REMIND
Severity:	crash
Priority:	NOR
Version First Reported In:	enterprise
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description thomas klein 2007-11-29 19:36:41 UTC

Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

Linux adept 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

kontact   4:3.5.7enterprise20070926-0ubuntu2
kmail     4:3.5.7enterprise20070926-0ubuntu2
libqt3-mt 3:3.3.8really3.3.7-0ubuntu11.1


*how to reproduce* : 

1) put this into /tmp/article.cfm (using kwrite for example) : 

<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\"> <html xmlns=\"http://www.w3.org/1999/xhtml\"> <head> </head> <body> </body> </html>

1.1) Save the file :)

2) open kmail

3) click on the "New Message" button

4) drag /tmp/article.cfm in the new message, select "Add as attachement"

5) double click on the article.cfm _in_the_message_your_are_editing_with_kmail_ 

6) click on OK when the a message appear 

"KMail is unable to detect when the choosen editor is closed. To avoid data loss, editing the attachment will be aborted."

7) crash :)

here is the backtrace : 

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243007296 (LWP 28244)]
[New Thread -1286104176 (LWP 28248)]
[New Thread -1277711472 (LWP 28247)]
[New Thread -1269318768 (LWP 28246)]
[New Thread -1260926064 (LWP 28245)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#87 0x08c8c83c in ?? ()
#88 0xb66cbaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#89 0xb66cd91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#90 0xb6e91ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#91 0xb665e209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#92 0xb66ccb28 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#93 0xb66ccc30 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#94 0xb6672101 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#95 0xb66e61ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#96 0xb66e5fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#97 0xb66cd699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#98 0x0805bfe5 in ?? ()
#99 0xbfeea0dc in ?? ()
#100 0x00000001 in ?? ()
#101 0x00000001 in ?? ()
#102 0x00000000 in ?? ()

Comment 1 Thomas McGuire 2007-12-01 22:29:49 UTC

I can't reproduce using the steps you posted. After clicking OK, KMail does not crash for me.
Please try a newer version of KMail, I think the edit attachment feature was work in progress at the time of your version.
If you can still reproduce it with a newer enterprise version, please reopen.