Comment 3 for bug 440908

Hi Joey!

I was able to reproduce the error...but only after nuking some metadata, so looks like the metadata of a share is broken in your install :(

ATM, and in the time frame imposed by karmic, the best solution I can think of is to handle the brokeness by invalidating the share and cleaning up all metadata related to the broken share.
The side effects of this apporach is that the files/folders in the share are (quite probably) going to be marked as conflicts (renamed to <name>.u1conflict)

I'm already have a branch that fix this as described, but I'm doing some tests IRL.

Regards,