Nothing else was running that should have been writing to the files, though I don't have any actual file stats from the bug. I've only seen it on FAT32, but since I don't have a way to reproduce the bug, this may simply reflect the files I edit most being stored there.
At least some occurrences were after another process had *read* the file (as in the Gnome bug you refer to), but I was unable to deliberately cause the bug this way. While testing this, I noticed that the two files I had seen this bug on both had all zero access times, which were also before their modification times: :~$ stat windocs/firefox2-error.txt File: `windocs/firefox2-error.txt' Size: 153459 Blocks: 320 IO Block: 32768 regular file Device: 301h/769d Inode: 1174 Links: 1 Access: (0770/-rwxrwx---) Uid: ( 0/ root) Gid: ( 46/ plugdev) Access: 2007-07-20 00:00:00.000000000 +0100 Modify: 2007-07-20 08:47:52.000000000 +0100 Change: 2007-07-21 16:41:33.000000000 +0100 However, the bug hadn't occurred the last time these files were saved, and didn't when I tried this file again, which also changed these access times as normal. -- (fat32) Unexpected "file modified by another process" warning https://bugs.launchpad.net/bugs/125887 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
