[09:36] <JamesTait> Good morning all, happy Friday, and happy Fight Procrastination Day! :-D
[11:34] <adeuring> Hi, I'm trying to buy a few mp3 files via ubuntuone, but I'm getting only the message "Communication with the Ubuntu One servers failed. Please try again in a few moments." -- first attempt was 2 hours ago
[11:42] <davmor2> adeuring: in https://one.ubuntu.com/music-store-up/purchases do you see a retry button or just contact support?
[11:45] <adeuring> davmor2: I see my "Purchase history", and when the page loads, there was also for a few seconds an error message.... now it's gone, when i try copy & paste it.
[11:48] <davmor2> adeuring: Yeah that is a bug it's because you changed page and it wasn't expecting you too :)  Ah sorry had you actually purchased the apps?
[11:49] <davmor2> tracks even
[11:49] <adeuring> davmor2: I've successfully bought several track before, but today its not possible.
[11:50] <davmor2> let me have a quick look then
[11:53] <adeuring> davmor2: looking into ~/.cache/ubuntuone/log/syncdaemon-exceptions.log I see   File "/usr/lib/python2.7/dist-packages/ubuntuone-client/ubuntuone/syncdaemon/interaction_interfaces.py", line 1273, in connect
[11:53] <adeuring>     raise NoAccessToken("got empty credentials.")
[11:53] <adeuring> ubuntuone.syncdaemon.interaction_interfaces.NoAccessToken: got empty credentials.
[11:55] <adeuring> logged in now, but still can't buy tracks
[12:05] <adeuring> davmor2: just tried on another machine. Buying tracks worked fine there
[12:06] <davmor2> adeuring: it looks like there might be an issue so I don't think it is just you I've got onto the team to look, thanks for bringing it to our attention.
[12:08] <adeuring> davmor2: no problem. But it might be related to my setup -- see my message above about the missing login for the sync client.
[12:08] <adeuring> davmor2: I'd like to buy some more tracks, so can try again on the machine where it does not work right now. Just tell me what i should do
[12:09] <davmor2> adeuring: it could be indeed lets double check the issue on the server first though and rule that out then we can look at your individual machine and see if it is still and issue :)
[12:09] <adeuring> sure ;)