Empty conflict files have executable file permissions

Hello, thank you for testing Ubuntu One!

We do absolutely nothing with permissions (other than setting some folders readonly), so the only thing I can think of is that you have your Ubuntu One folder on a FAT or similar filesystem, where everything is executable.

I'll repeat myself, just to be clear: no file permission information is sent over the wire, ever. The only 'chmod' you'll find in ubuntuone-syncdaemon is the one related to setting some folders read-only.

So I'm grasping at straws as to what you are seeing. Could you come up with a way we can reproduce it?

Thanks,

I probably shouldn't file bug reports in the middle of the night, instead of "partial" files I meant to say "conflict" files.

The files in question are zero-byte *.u1conflict files. Also, the last time that this happened was August 2, and I haven't seen this problem since then, but I still have a number of unresolved conflicts.

I don't use any FAT file system on the machines that I've been using for U1 testing. All of the partitions where I've been testing are using JFS. I can also verify that the original file on my home machine had 664 permissions and the zero byte .u1conflict on my work laptop was 755. Only the zero-byte conflict files are executable, the conflict files with data are set to umask (022) permissions.

I've gotten most of my conflict files by switching off wireless on my laptop at work during a sync. We have both a wired and wireless network and I sometimes forget to switch off my laptop wireless until I log in and Evolution can't connect to my email (because it's timing out on the public wireless connection). This also happens to be the time that the U1 sync is checking all of the files and syncing changes from my home machine.

If the files which were partials at that time are ones that I'm working on that day I'll resort to `scp -p` from my home machine to get the updated file. I manually delete the partial file. These seem to be the files which are conflicting.