Bug 189126

Summary:	[data loss] Choosing "save as" in the dialog after an open file got deleted does not work
Product:	[Applications] kate	Reporter:	Thomas Braun <thomas.braun>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	thomas.braun
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Thomas Braun 2009-04-08 15:14:56 UTC

Version:           2.5.10 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-0lenny1 (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.26-1-686

This is bug report which was reported on kile-devel and turned out to be a grave katepart bug, see also http://sourceforge.net/mailarchive/message.php?msg_name=554ba11a0904060803w13a39bc0s59f570d05634a0ca%40mail.gmail.com. It is also known to ubuntu, see https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/133431, but has unfrotunately not been reported here.

How to reproduce it:
1. start kate
2. create a new document
3. save it as test.tex
4. delete test.tex from a terminal
5. kate detects that the file is deleted and asks the user to either
save the file or ignore it.
6. If you select "save as" under the name new-test.text, you get the message that the file could not be written and that the user should check the permission (but the permissions are okay)
7. All data is lost. If you select ignore in the above dialog, then all is fine.

Please tell me if you plan to fix this bug and if there is a plan for a KDE 3.5.11 release.

Thanks a lot,
Thomas (member of kile dev team)

Comment 1 Thomas Braun 2009-04-08 15:16:38 UTC

This bug is _not_ present in the KDE 4.2 branch.

Comment 2 Andreas Pakulat 2009-04-08 16:43:56 UTC

Seeing that there's been no change in the last couple of weeks in KDE4 for kate, I doubt any of the devs has time to care for old codebases. The last significant change to kate/kde3.5 has been almost a year ago.

And if this works in KDE4.2 I think we can close this as fixed.