ubuntuone-preferences doesn't open after getting token
Bug #538278 reported by
Joshua Hoover
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Client |
Fix Released
|
Medium
|
dobey | ||
| ubuntuone-client (Ubuntu) |
Fix Released
|
Medium
|
dobey | ||
Bug Description
STEPS TO REPRODUCE:
Running PPA version 1.1.3+r409-0ubuntu2 with no Ubuntu One token in the keyring
1. Open System-
2. Add this computer when prompted via web page
3. Token received, taken to https:/
Result: ubuntuone-
Expected result: ubuntuone-
Related branches
lp:~dobey/ubuntuone-client/devices-remove-local
- Natalia Bidart (community): Approve
- Joshua Hoover (community): Approve (ran branch and verified bug fixes)
-
Diff: 424 lines (+119/-59)3 files modifiedbin/ubuntuone-preferences (+115/-55)
tests/test_preferences.py (+3/-2)
ubuntuone/oauthdesktop/main.py (+1/-2)
| Changed in ubuntuone-client (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+) |
Revision history for this message
| dobey (dobey) wrote | #1 |
| tags: | added: package |
| Changed in ubuntuone-client: | |
| assignee: | Ubuntu One Desktop+ team (ubuntuone-desktop+) → Rodney Dawes (dobey) |
| Changed in ubuntuone-client (Ubuntu): | |
| assignee: | Ubuntu One Desktop+ team (ubuntuone-desktop+) → Rodney Dawes (dobey) |
| Changed in ubuntuone-client: | |
| status: | Confirmed → In Progress |
| Changed in ubuntuone-client: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntuone-client: | |
| status: | Fix Committed → Fix Released |
| Changed in ubuntuone-client (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
It appears there is something wrong in the oauthdesktop code. It looks like what is happening is that we get a valid access token, and also an "Invalid request token" error, at the same time. The access token ends up in the keyring, and the OAuthError signal is fired with the Invalid request token error.