Bug 143500

Summary:	canceling closing kmail while external editor is still open causes crash
Product:	[Unmaintained] kmail	Reporter:	Arnout Boelens <a.m.p.boelens>
Component:	composer	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version First Reported In:	1.9.6
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Arnout Boelens 2007-03-26 22:00:42 UTC

Version:           1.9.6 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-2 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18

I use vim as external editor for kmail. When I close kmail while vim is still open, I get a window telling me my external editor is still open and asking me what I want to do. When I press "cancel" (to not close kmail) kmail crashes.

Comment 1 Thomas McGuire 2007-03-27 18:50:08 UTC

Confirmed.
Backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242220880 (LWP 4815)]
[KCrash handler]
#5  0xb52760a2 in KMFolderComboBox::createFolderList (this=0x86c15c0, 
    names=0xbfd9f168, folders=0xbfd9f164)
    at /root/kdepim2/kdepim-3.5.6/./kmail/kmkernel.h:284
#6  0xb534e20e in KMFolderComboBox::getFolder (this=0x86c15c0)
    at /root/kdepim2/kdepim-3.5.6/./kmail/kmfoldercombobox.cpp:151
#7  0xb544269c in KMComposeWin::writeConfig (this=0x868f448)
    at /root/kdepim2/kdepim-3.5.6/./kmail/kmcomposewin.cpp:652
#8  0xb5442def in ~KMComposeWin (this=0x868f448)
    at /root/kdepim2/kdepim-3.5.6/./kmail/kmcomposewin.cpp:413
#9  0x080610c3 in main (argc=1, argv=0x821b110)
    at /root/kdepim2/kdepim-3.5.6/./kontact/src/main.cpp:165
#10 0xb77228cc in __libc_start_main () from /lib/libc.so.6
#11 0x080583c1 in _start ()

Comment 2 Dominik Tritscher 2008-08-04 20:05:37 UTC

KMail 1.10.0 is asking me what to do if external editor is still open, so I guess this is fixed.

Comment 3 Arnout Boelens 2008-08-04 20:11:03 UTC

Yes, you're right. It works for me now too.