Version: 3.2.0 (using KDE 3.2.0, Gentoo) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice) OS: Linux (i686) release 2.6.2-rc2-mm1 Steps to reproduce: 1. Create a project and load some files into the project. 2. Open a file by clicking on it in the tree column under the Project tab 3. Select this menu sequence: File->Save As and enter a new name. When asked, choose to add this file to the project. 4. Change something in the new file and press "CTRL+S". 5. The "File Changed" dialog pops up. Regardless of what option you choose, this dialog will continue to pop up. Expected behaviour: The file should save without incident, and without that dialog popping up. Other Information: File System: Reiserfs-3.6, standard journal mounted with "defaults" in fstab File Format: *.php
This is the behaviour I get when "Automatic Cleanups" are in effect, see bug #74217
I do not have any automatic clean up options enabled.
CVS commit by amantia: Workaround for a Kate bug. Might fix those "File changed" dialog pops up errors. Those who experienced that problem, please test it. CCMAIL: quanta@kde.org CCMAIL: 74305@bugs.kde.org CCMAIL: 74217@bugs.kde.org M +1 -0 document.cpp 1.250 --- kdewebdev/quanta/src/document.cpp #1.249:1.250 @@ -140,4 +140,5 @@ Document::Document(const KURL& p_baseURL Document::~Document() { + m_doc->closeURL(false); //TODO: Workaround for a Kate bug. Remove when KDE < 3.2.0 support is dropped. delete m_view; delete m_doc;
Unfortunately the patch didn't work for me.
An update... By setting "Replace tabs with spaces" in the settings under "Automatic Cleanups on Save" this problem disappears. Perhaps tab characters have something to do with this? Also, when the file changed dialog pops up, the option "Compare the two version and load the result" is greyed out which I assume means the file are identical. Perhaps the code that decides that option is greyed out can decide to kill the window itself? Would my quantarc file help? Is there anything else I can provide to help resolve the bug?
Although the triggering action might be different, this is basicly the same bug. *** This bug has been marked as a duplicate of 74217 ***