does not re-attempt oauth setup when credentials removed

Bug #528260 reported by Kees Cook
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Invalid
Medium
Ubuntu One Foundations+ team

Bug Description

Binary package hint: ubuntuone-client

Might be related to bug 498052. Once I removed my machine via the u1 web interface, the local client will not attempt to set up the oauth via the browser again. (It fails on the old credentials over and over.)

ProblemType: Bug
Architecture: amd64
Date: Thu Feb 25 23:59:39 2010
DistroRelease: Ubuntu 10.04
Package: ubuntuone-client 1.1.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.32-14-generic x86_64

Revision history for this message
Kees Cook (kees) wrote :
Revision history for this message
Kees Cook (kees) wrote :

As a work-around, I finally located the U1 credentials (they're in the gnome keyring) and deleted them. When re-launching the U1 preferences, I was redirected through oauth again.

Revision history for this message
Eric Casteleijn (thisfred) wrote :

Confirmed this is still an issue:

I removed my machine through the web, then clicked 'connect' in nautilus. I get no feedback, (other than the button not changing to 'disconnect') and strangely, the oauth-login.log shows no errors, but the syncdaemon log (attached) shows authentication errors.

Revision history for this message
Eric Casteleijn (thisfred) wrote :
Revision history for this message
Eric Casteleijn (thisfred) wrote :
Changed in ubuntuone-client (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
Revision history for this message
dino99 (9d9) wrote :

Closing that outdated report as EOL has been reached long time ago

Changed in ubuntuone-client (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.