That's what I thought. It doesn't solve the bug, but works around it. I think the correct fix wold be to make ubuntuone-launch not start ubuntuone-syncdaemon if there is no token yet (it used to do that), and perhaps to make syncdaemon not try to connect automatically if there is no token, but if a connect() is explicitly requested, with no token, I think the register() call is still the right one to make. No?
That's what I thought. It doesn't solve the bug, but works around it. I think the correct fix wold be to make ubuntuone-launch not start ubuntuone- syncdaemon if there is no token yet (it used to do that), and perhaps to make syncdaemon not try to connect automatically if there is no token, but if a connect() is explicitly requested, with no token, I think the register() call is still the right one to make. No?