Summary: | Kate does not truncate files in write protected folders | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Martin Walch <walch.martin> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | digimer, emmanuel.lepage, kevin.kofler, michal.humpula, peter.maloney |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kate/cb28209081def580849b194620892ef489be55dd | Version Fixed In: | 4.12.5 |
Description
Martin Walch
2013-08-18 22:40:36 UTC
Git commit cb28209081def580849b194620892ef489be55dd by Michal Humpula. Committed on 29/12/2013 at 14:41. Pushed by michalhumpula into branch 'master'. don't forget to truncate file if we are overwriting REVIEW: 114724 M +3 -2 part/buffer/katetextbuffer.cpp M +35 -0 tests/katetextbuffertest.cpp M +1 -0 tests/katetextbuffertest.h http://commits.kde.org/kate/cb28209081def580849b194620892ef489be55dd *** Bug 319679 has been marked as a duplicate of this bug. *** *** Bug 333086 has been marked as a duplicate of this bug. *** As far as I can tell, users are still reporting corruption in (stable) 4.12 branch, the fix was never backported. Can it? This is clearly a data loss bug, why was that critical fix not backported to the stable branch immediately? @Dieter: Yes, the patch is safe. Will you do it? @Kevin: Why was it never backported? Obviously simply noone did it, probably out of being too busy or it simply slipped. Git commit 874b16040ed6706bdf1be5917657f2278894776e by Dominik Haumann. Committed on 07/04/2014 at 20:30. Pushed by dhaumann into branch 'KDE/4.12'. backport: truncate files when opening for writing This backport was kind of requested in bug #323693. FIXED-IN: 4.12.4 M +3 -2 part/buffer/katetextbuffer.cpp http://commits.kde.org/kate/874b16040ed6706bdf1be5917657f2278894776e Unfortunately, 4.12.4 was already released, so this will be only in 4.12.5 (scheduled for April 29 (tagging on April 24) according to the schedule). Given the severity of this bug, shouldn't a new release be pushed out as soon as is possible? I corrupted two files thanks to this. It's up to the distributions to ship these kind of updates. It will come eventually. *** Bug 339143 has been marked as a duplicate of this bug. *** |