Comment 9 for bug 509556
Revision history for this message
| Gavin Chappell (g-a-c) wrote Re: Invalid request token: PN3P7jcRV4BJTdp2JQJD | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
I'm getting the same problem as Paul in comment #8. My seahorse entry and UbuntuOne account management entry match up, but the oauth-login log gives a different token which is invalid.
This laptop was do-release-upgraded from Karmic, however I have managed to add a desktop to my Ubuntu One account which was installed straight into Lucid Beta 1 and is working (as in Ubuntu One contains a couple of test files from this desktop).