Bug 118015 - quanta wrongly says my file has been modified
Summary: quanta wrongly says my file has been modified
Status: RESOLVED WORKSFORME
Alias: None
Product: quanta
Classification: Miscellaneous
Component: general (show other bugs)
Version: 3.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: András Manţia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-09 16:13 UTC by Alexis Rimbaud
Modified: 2006-01-17 14:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexis Rimbaud 2005-12-09 16:13:42 UTC
Version:           3.5 (using KDE 3.5.0, Kubuntu Package 4:3.5.0-0ubuntu0breezy1 breezy)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-9-k7

Hi,

When I want to save a PHP/HTML file I have modified in quanta, it always (or after one or two saves) says that the file has been modified outside the editor even if it has not. This bug makes quanta unusable, so I'm surprised nobody reported this bug (or maybe nobody else use quanta on breezy? :-)).

I'm running Kubuntu Breezy.

Thank for help.
Comment 1 Frank Mutsaers 2005-12-14 13:26:24 UTC
I updated some kde-files (using Yast) last monday and since i have the same problem.
It is not with all the files i update. Some files don't give the warning.
I first thought it happens with new files, the first time you save a new file it goes oke, but then you edit something and then save again there is the warning. But it happens also on files which are allready in my project.

I have OpenSuse 10 with kde 3.5.0 level 'a"
Comment 2 Martin Fabian Hohenberg 2005-12-18 17:17:41 UTC
Same effect here with KUbuntu Dapper and 3.5.0
Comment 3 András Manţia 2005-12-23 17:07:24 UTC
Does this happen after some action (save, close, switch tabs, update 
from CvS) or just without doing anything? Does it happen if you work 
with files in Kate?
Are you using local files or smb/nfs/whatever shares?
Comment 4 Alexis Rimbaud 2005-12-23 17:39:47 UTC
This happens on local files without doing anything (except trying to save the file of course! :-)) and whichever extension the file has.

I have no such problem neither with Kate 3.5.0 nor with Quanta 3.4.3.
Comment 5 András Manţia 2005-12-23 19:03:55 UTC
Is it when you use Save As or normal save? Does your kernel have inotify 
support (see /proc/config.gz)?
Comment 6 Alexis Rimbaud 2005-12-23 19:36:49 UTC
I use "normal save". I didn't try "save as" (except for the first save, when no file exists).

I have no /proc/config.gz, but "nodev   inotifyfs" in /proc/filesystems, if it helps...
Comment 7 András Manţia 2006-01-17 14:29:11 UTC
The bug is in Kubuntu's kernel + kdelibs combination. I checked with 
Kubuntu and I can reproduce with it. The problem is the kernel's 
inotify support is broken and the original KDE 3.5.0 release does not 
have a check to see if you have broken inotify or not. The solution:
- upgrade to a kernel which does not have the bug
- upgrade kdelibs to a version where inotify is disabled (you may 
compile from source the 3.5 branch)
- bug the ubuntu developers to do the above ;-)

Anyway, the problem is not in Quanta. If you still see the problem with 
the upcoming KDE 3.5.1, let me know.
Comment 8 András Manţia 2006-01-17 14:35:20 UTC
On Wednesday 14 December 2005 14:26, Frank Mutsaers wrote:
> I have OpenSuse 10 with kde 3.5.0 level 'a"


For SuSE there is a fixed kdelibs and kernel:
kernel: 2.6.13-15.7-default
kdelibs: 3.5.0-31