Hi, I'm sorry to hear Ubuntu One isn't working properly for you. Based on the error in your syncdaemon-exceptions.log file, I think this is related to metadata somehow getting corrupted. Did you recently experience a crash while Ubuntu One was in the process of syncing files?
If you run the following from a terminal session (Applications->Accessories->Terminal) it should show the metadata or the pickle error that might help determine the cause of the problem:
A way to recover from this, is to remove the corrupted metadata file, which will be restored on the syncdaemon startup (after connecting to the server a fetch the shares list). Run the following command from a terminal session:
Hi, I'm sorry to hear Ubuntu One isn't working properly for you. Based on the error in your syncdaemon- exceptions. log file, I think this is related to metadata somehow getting corrupted. Did you recently experience a crash while Ubuntu One was in the process of syncing files?
If you run the following from a terminal session (Applications- >Accessories- >Terminal) it should show the metadata or the pickle error that might help determine the cause of the problem:
python -c "import cPickle, os; print cPickle. load(open( os.path. expanduser( '~/.local/ share/ubuntuone /syncdaemon/ vm/shares/ 8/a/8/8a86003d- 1715-401c- 8c6f-8bda6066a0 55'), 'r'))"
A way to recover from this, is to remove the corrupted metadata file, which will be restored on the syncdaemon startup (after connecting to the server a fetch the shares list). Run the following command from a terminal session:
rm ~/.local/ share/ubuntuone /syncdaemon/ vm/shares/ 8/a/8/8a86003d- 1715-401c- 8c6f-8bda6066a0 55
Please let me know if this helps.
Thank you,
Joshua