Comment 5 for bug 1413655

OK. So this is somewhat expected behavior under certain conditions. If you have an account created with a version of ubuntuone-credentials prior to 14.04+15.04.20150120 on vivid or 14.04+15.04.20150122~rtm on the RTM image, then that account will not have the "unconfined" ACL needed to work correctly with some more recent updates in signon. With such an account, upgrading to an image which has signon version 8.57+15.04.20150204.1-0ubuntu1 or newer on vivid or 8.57+15.04.20150205~rtm-0ubuntu1 or newer on the RTM image, the existing account will no longer be usable. When opening the Updates panel of System Settings, this will result in the existing account being deleted as it is no longer usable. If you were to browse through the store and install an app, the resolution to this would be fluid and straightforward, as the store scope would cause the signon UI for U1 to pop up and require you to log in again, when you tap the Install or Buy buttons. However, the Updates panel in system-settings does not open this UI, and instead shows a button. The solution here is to fix system-settings to open that UI when the existing token is deleted. We must delete the token and require the user to log in again, as a matter of improved security in the newer images. So, I'm moving this to system-settings.