Bug 106107

Summary:	Closing kontact when composing a new message in knode or kmail does not ask for confirmation
Product:	[Applications] kontact	Reporter:	Vincenzo Ciancia <vincenzo_ml>
Component:	news	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	carlos-spam, finex, mail, sven.burmeister
Priority:	NOR	Keywords:	triaged
Version:	1.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Vincenzo Ciancia 2005-05-22 12:52:14 UTC

Version:           sconosciuto (using KDE KDE 3.4.0)
Installed from:    Unlisted Binary Package
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
OS:                Linux (i686) release 2.6.11.7

I begin to compose a new usenet message, then by mistake close kontact. Voila, my work is completely lost, while if I do this in knode standalone the system asks for confirmation and eventually allows me to save the artcle in my drafts folder.

Comment 1 Vincenzo Ciancia 2005-12-11 17:58:03 UTC

Still there in kde 3.5

Comment 2 S. Burmeister 2006-10-28 15:13:46 UTC

Confirmed on KDE 3.5.5 and as it causes data-loss, it should get a higher priority.

Comment 3 Will Stephenson 2006-10-28 22:37:32 UTC

There's a similar bug where Kontact suppresses the kmail 'save composing message on exit' dialog, but I can't find it.

Comment 4 Will Stephenson 2006-10-28 22:55:21 UTC

*** Bug 111041 has been marked as a duplicate of this bug. ***

Comment 5 FiNeX 2007-12-11 18:25:51 UTC

This bug is still present in KDE 4.

Comment 6 George Kiagiadakis 2008-09-30 12:24:57 UTC

Still reproducable in kontact 1.3 svn trunk r865463 (KDE 4.1.68).

Comment 7 Denis Kurz 2016-09-24 19:20:11 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 8 Denis Kurz 2017-01-07 22:24:21 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.