Comment 17 for bug 774295

Chad, I was able to reproduce this on 1.0.7+r277-14~natty1 - simply delete the machine via ubuntuone control panel, restart desktopcouch and see it using all the CPU.

Nothing is written in desktopcouch-replication logs during this misbehavior.

DEBUG:replication:Looking up prefix for service 'ubuntuone'
INFO:root:get_oauth_data: asking for credentials to Ubuntu SSO. App name: Ubuntu One
INFO:root:Got credentials from Ubuntu SSO. Non emtpy credentials? False
DEBUG:replication:Looking up prefix for service 'ubuntuone'
ERROR:root:Could not get access token from sso.
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/desktopcouch/application/replication_services/ubuntuone.py", line 103, in __str__
    consumer = oauth.OAuthConsumer(oauth_data['consumer_key'],
KeyError: 'consumer_key'
replication 2011-07-19 15:37:59,187 - Could not get access token from sso.
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/desktopcouch/application/replication_services/ubuntuone.py", line 103, in __str__
    consumer = oauth.OAuthConsumer(oauth_data['consumer_key'],
KeyError: 'consumer_key'
WARNING:replication:Can't reach service ubuntuone. No access token.
replication 2011-07-19 15:37:59,188 - Can't reach service ubuntuone. No access token.
DEBUG:replication:finished replicating
DEBUG:root:starting replicator main loop