Hi, I'm using opensuse10, i386, with kde3.5 , binary release downloaded from a Suse Mirror ftp.rediris.es/pub/linux/distributions/suse/pub/suse/i386/supplementary/KDE/update_for_10.0 After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile. I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file. In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts. I searched the internet and nobody seems to be having this problem. any help is welcome. my best regards, -- António Rodrigues Tomé artome@ubi.pt <---official e-mail address artome@gmail.com <---alternative security e-mail address http://www.dfisica.ubi.pt/~artome http://www.cgul.ul.pt/curric/cgul_tome.htm
On Saturday 07 January 2006 14:55, António Rodrigues Tomé wrote: <snip>
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
Hi António, I'm very interested in what you're describing because I'm having a similar experience *except* the system is SUSE 9.3 i686 + KDE 3.4.3 Level 'b' and the applications are jEdit and gedit (the two text/html/css editors I use most frequently.) It isn't very frequent at all... but seems to happen when I've got a page open for editing *and* am viewing it in a browser. If I, say, go for coffee and the phone rings and I'm gone for 15 minutes, I'll come back and find the same message in a pop-up dialog box originating from my editor. I just click "OK" and continue working without experiencing any problems. I supposed I'll scroll down to the EOF next time and see if white space has been appended... This phenomenon is also recently new, meaning within the last few weeks, max a month, and I was still trying to formulate a working hypothesis to develop some tests. As it is, I really haven't got a clue where to begin looking until I know more about it. I guess I'll be following this thread very closely, so thanks for posting! regards, - Carl
On Saturday 07 January 2006 21:41, Carl Hartung wrote:
On Saturday 07 January 2006 14:55, António Rodrigues Tomé wrote: <snip>
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
Hi António,
I'm very interested in what you're describing because I'm having a similar experience *except* the system is SUSE 9.3 i686 + KDE 3.4.3 Level 'b' and the applications are jEdit and gedit (the two text/html/css editors I use most frequently.)
It isn't very frequent at all... but seems to happen when I've got a page open for editing *and* am viewing it in a browser. If I, say, go for coffee and the phone rings and I'm gone for 15 minutes, I'll come back and find the same message in a pop-up dialog box originating from my editor.
I just click "OK" and continue working without experiencing any problems. I supposed I'll scroll down to the EOF next time and see if white space has been appended...
This phenomenon is also recently new, meaning within the last few weeks, max a month, and I was still trying to formulate a working hypothesis to develop some tests. As it is, I really haven't got a clue where to begin looking until I know more about it.
I guess I'll be following this thread very closely, so thanks for posting!
regards,
- Carl Hi,
With kate it is ok to ignore the message or to choose reload the file, but with kile if one chooses to ignore everthing seems to work at first but one risks to lose all the work because at the next save kile says that he has no permition to save the file and aborts. I've just posted the same post on the suse-kde. Some people will see the post twice but the fact is that i'm completely in a unworkable situation because I use kile a lot, and I've no way of downgrading for two or three upgradings before, because the mirrors do not kept the old versions and in the other hand I got used to KDE3.5 and I wouldn't like to go bak to the original distribution. -- António Rodrigues Tomé artome@ubi.pt <---official e-mail address artome@gmail.com <---alternative security e-mail address http://www.dfisica.ubi.pt/~artome http://www.cgul.ul.pt/curric/cgul_tome.htm
I noticed this last night with Kate. It seemed to say the file changed when another app simply read the file only. I thought it was just me and the app (Nanoblogger) was reading the file in R/W format in the code. But i am thinking its not just me now that i have read this. António Rodrigues Tomé wrote:
On Saturday 07 January 2006 21:41, Carl Hartung wrote:
On Saturday 07 January 2006 14:55, António Rodrigues Tomé wrote: <snip>
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
Hi António,
I'm very interested in what you're describing because I'm having a similar experience *except* the system is SUSE 9.3 i686 + KDE 3.4.3 Level 'b' and the applications are jEdit and gedit (the two text/html/css editors I use most frequently.)
It isn't very frequent at all... but seems to happen when I've got a page open for editing *and* am viewing it in a browser. If I, say, go for coffee and the phone rings and I'm gone for 15 minutes, I'll come back and find the same message in a pop-up dialog box originating from my editor.
I just click "OK" and continue working without experiencing any problems. I supposed I'll scroll down to the EOF next time and see if white space has been appended...
This phenomenon is also recently new, meaning within the last few weeks, max a month, and I was still trying to formulate a working hypothesis to develop some tests. As it is, I really haven't got a clue where to begin looking until I know more about it.
I guess I'll be following this thread very closely, so thanks for posting!
regards,
- Carl
Hi,
With kate it is ok to ignore the message or to choose reload the file, but with kile if one chooses to ignore everthing seems to work at first but one risks to lose all the work because at the next save kile says that he has no permition to save the file and aborts.
I've just posted the same post on the suse-kde. Some people will see the post twice but the fact is that i'm completely in a unworkable situation because I use kile a lot, and I've no way of downgrading for two or three upgradings before, because the mirrors do not kept the old versions and in the other hand I got used to KDE3.5 and I wouldn't like to go bak to the original distribution.
I found the same problem. I also experienced that both kate and konqueror often crash when used to display large text files. Before the latest two updates everything worked. Francesco António Rodrigues Tomé wrote:
Hi,
I'm using opensuse10, i386, with kde3.5 , binary release downloaded from a Suse Mirror ftp.rediris.es/pub/linux/distributions/suse/pub/suse/i386/supplementary/KDE/update_for_10.0
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
I searched the internet and nobody seems to be having this problem.
any help is welcome.
my best regards,
On Saturday 07 January 2006 20:55, António Rodrigues Tomé wrote:
I searched the internet and nobody seems to be having this problem.
You didn't search well: https://bugzilla.novell.com/show_bug.cgi?id=131322 Testers for the proposed kernel fix are wanted there.
any help is welcome.
Next kdelibs-3.5 revision will also disable inotify for broken old kernels. Bye, Steve
Well found Stephan I might have to try and use this patch they have supplied. Dont want to use his binary as i have some binary modules :( Stephan Binner wrote:
On Saturday 07 January 2006 20:55, António Rodrigues Tomé wrote:
I searched the internet and nobody seems to be having this problem.
You didn't search well: https://bugzilla.novell.com/show_bug.cgi?id=131322 Testers for the proposed kernel fix are wanted there.
any help is welcome.
Next kdelibs-3.5 revision will also disable inotify for broken old kernels.
Bye, Steve
On 1/9/06, Stephan Binner
On Saturday 07 January 2006 20:55, António Rodrigues Tomé wrote:
I searched the internet and nobody seems to be having this problem.
You didn't search well: https://bugzilla.novell.com/show_bug.cgi?id=131322 Testers for the proposed kernel fix are wanted there.
any help is welcome.
Next kdelibs-3.5 revision will also disable inotify for broken old kernels.
Bye, Steve
Many many thanks, in fact having no clue of the problem source I was unable to choose the right words for a good internet shearch. I was convinced the problem was in the suse binary distribution of KDE 3.5 and not in the linux kernel. I'm going to test the patch but I hope not to lose the nvidea 3D card. best regards, António Tome'
I just installed the latest kde updates. All problems seem to be solved. Francesco António Rodrigues Tomé wrote:
Hi,
I'm using opensuse10, i386, with kde3.5 , binary release downloaded from a Suse Mirror ftp.rediris.es/pub/linux/distributions/suse/pub/suse/i386/supplementary/KDE/update_for_10.0
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
I searched the internet and nobody seems to be having this problem.
any help is welcome.
my best regards,
Must be a work around in KDE perhaps ?? Francesco Teodori wrote:
I just installed the latest kde updates. All problems seem to be solved.
Francesco
António Rodrigues Tomé wrote:
Hi,
I'm using opensuse10, i386, with kde3.5 , binary release downloaded from a Suse Mirror ftp.rediris.es/pub/linux/distributions/suse/pub/suse/i386/supplementary/KDE/update_for_10.0
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
I searched the internet and nobody seems to be having this problem.
any help is welcome.
my best regards,
I think so. After moving to KDE 3.5 (November 30) I did not encounter any problem. After updating the system (December 23, December 28) I started experiencing several crashes both with kate and konqueror. Kate also started showing 'file changed on disk' alerts very frequently. After the last update (January 8) any problem disappeared. Francesco David Ward wrote:
Must be a work around in KDE perhaps ??
Francesco Teodori wrote:
I just installed the latest kde updates. All problems seem to be solved.
Francesco
António Rodrigues Tomé wrote:
Hi,
I'm using opensuse10, i386, with kde3.5 , binary release downloaded from a Suse Mirror ftp.rediris.es/pub/linux/distributions/suse/pub/suse/i386/supplementary/KDE/update_for_10.0
After a new upadates one or two weeks ago I started to observed strange behavior in kate and Kile.
I'm permanently getting the message "file has changed on disk" without that being true! choosing the view difference option it gives a difference of one blank line at the bottom of the file.
In kile choosing the view difference option is a very bad idea because the system starts building some databases and stays freeze for about 5 minutes. After that kile aborts.
I searched the internet and nobody seems to be having this problem.
any help is welcome.
my best regards,
participants (6)
-
A Tome -
António Rodrigues Tomé
-
Carl Hartung -
David Ward -
Francesco Teodori -
Stephan Binner