modification time changes after upload

[Paul]

I edit a file directly in the Ubuntu One folder. After saving the U1 client duly starts "Updating files...". Shortly afterwards the editor reports a file change on disk, and asks whether to load the new contents. When I print modification times (twice very shortly after saving) in the shell I get:

$ ls --full-time -c Ubuntu\ One/test.txt
-rw-r--r-- 1 peters peters 9 2009-12-29 23:58:32.000000000 +0100 Ubuntu One/test.txt

$ ls --full-time -c Ubuntu\ One/test.txt
-rw-r--r-- 1 peters peters 9 2009-12-29 23:58:35.000000000 +0100 Ubuntu One/test.txt

The upload seems to change the modification time of the file. Does that make any sense? Since a report of file modification on disk by the editor usually points to a work flow problem, ignoring this message is really difficult.

I also suspect that this is the root of a more serious problem, which I can not reproduce consistently. After some edits (saving sometimes more than once in a few seconds) the file disappears, is replaced by an empty file, or an old version and one or two conflict files appear (up to now I use Ubuntu One only from one computer, so no changes on another computer, so the appearance of conflict files is very strange). Saving is sometimes not possible any more (the file immediately disappears again after saving) until I remove the conflict files. I checked the file in the web interface at one such occasion and it was a very old version.

This is not related to bug #491777. I checked that nautilus was not open during the shell print outs above.

ProblemType: Bug
.home.peters..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.peters..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 0
 on = False
.home.peters..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 0
Architecture: i386
CrashDB: ubuntuone
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.1.0+r300-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.28-17-generic i686
UnreportableReason: Das Paket stammt nicht von Ubuntu.

[Duane Hinnen (duanedesign)]

 i think bug 501493 _is_ related to bug 491777, one does not really need to have Nautilus to be opened _just_ then. The DBus callback will operate on the cached data which may or may not be cleaned up by nautilus at that time.

If you would like to help us further debug the problem we would greatly appreciate it. You can do the following in order to provide important details that will help determine the root cause of this issue?

1) Quit the Ubuntu One client. R-click on the Ubuntu One applet and select 'Quit'

2) Open Applications->Accessories->Terminal, then run the command:
  mv ~/.cache/ubuntuone/log ~/.cache/ubuntuone/log_old && mkdir ~/.cache/ubuntuone/log

3) Run the following in a Terminal to open/create this file:
 gedit ~/.config/ubuntuone/syncdaemon.conf

    #Add the following 2 lines to this file and save:
    [__main__]
    log_level = DEBUG

4) Open Ubuntu One Applications->Internet->Ubuntu One

5) Let Ubuntu One run for a bit, copy some files into your Ubuntu One Folder. Then attach the following logs to this bug:
~/.cache/ubuntuone/log/syncdaemon.log
~/.cache/ubuntuone/log/syncdaemon-exceptions.log

You can attach logs to this bug report by clicking the 'Add Attachment or patch' button at the bottom of the page. Thank you for filing this bug report and helping to make Ubuntu better.

[Paul (paul-peters)]

I did what duanedesign suggested, but could only find
"~/.cache/ubuntuone/log/syncdaemon.log"
 the file "~/.cache/ubuntuone/log/syncdaemon-exceptions.log" did not exist.

Note that I switched to 64bit version of ubuntu 9.10

I first saved test.txt (with only "1" in it) with gedit and gedit complained about a file change on disk (see attached screenshot).

Then I very often saved a very long version of test.txt, and did not get any complains by gedit any more. Also I could not get the different times with "ls --full-time -test.txt" as in mentioned in my first post.

Then I saved the file as test2.txt (once!!!) and gedit did not complain, but I got in the terminal

peters@dell-1720:~/Ubuntu One$ ls --full-time -c test2.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:08:24.351779027 +0100 test2.txt
peters@dell-1720:~/Ubuntu One$ ls --full-time -c test2.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:08:25.784248307 +0100 test2.txt
peters@dell-1720:~/Ubuntu One$ ls --full-time -c test2.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:08:25.784248307 +0100 test2.txt
peters@dell-1720:~/Ubuntu One$ ls --full-time -c test2.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:08:25.784248307 +0100 test2.txt
peters@dell-1720:~/Ubuntu One$ ls --full-time -c test3.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:09:30.871750213 +0100 test3.txt
peters@dell-1720:~/Ubuntu One$ ls --full-time -c test3.txt
-rw-r--r-- 1 peters peters 1357507 2010-02-08 21:09:32.834248792 +0100 test3.txt

the last 2 lines after I saved the same file with again a new name "test3.txt".

Hope that helps.

[Roman Yepishev (rye)]

Hello Paul,

Thanks for the extended explanation. I was able to reproduce it reliably so I am now checking what is actually happening to the file.

[Roman Yepishev (rye)]

Paul, i have actually hit the behavior that I have described in #2 (bug #491777).
Could you please quit nautilus with:
$ nautilus -q

(this will shut down all nautilus processes along with desktop file view, to restore, just launch "nautilus &" from terminal)

Then try to save one more file in gedit. Is gedit reporting that file is changed on disk in this case?

I can confirm that this behavior is now present in 1.0.3-0ubuntu1 as well as in r300, the version that was this bug originally reported for.

[Paul (paul-peters)]

I agree with Roman that this bug is a duplicate of bug #491777.

However, I want to report here what when I followed Romans advice comment #6 of the present bug. I shut down nautilus with nautilus -q and then I could not reproduce the bug. Neither gedit, "ls --full-time" nor Eclipse (with which I bumped into that bug in the first place) reported any file modification.

The strange thing is that after restarting nautilus and also after many restarts of the system I could not reproduce the bug. For me it looks like the bug has been fixed somehow. I see an u1 client update from February 11th , which is before I started testing with nautilus shutdown.

[Paul (paul-peters)]

I mixed up dates. The bug seems to have been disappeared before the u1 update February 11th. I could not reproduce it before that update. So I really don't know what happend