keep getting AUTH_FAILED in ubuntu one

[Ralf Nieuwenhuijsen]

Binary package hint: ubuntuone-client

Steps to reproduce
- install natty beta 2 or daily image (Both have been tried)
- connect with Ubuntu One
- get AUTH_FAILED

Things that have been tried:
 - reinstalling from scratch with daily image
 - choosing a different name for the laptop (hostname)
 - removing device through web ui
 - removing passwords
 - synchronizing clock

Pretty much all workarounds that are floating around in the thousands of forums posts, askubuntu questions, and open bug reports, about Ubuntu One not syncing / connecting properly. Honestly, for one of the few commercial products offered by Canonical, the scale of the issues and the general consensus of using all kinds of workarounds; its a bit discomforting)

We need these files; the only alternative at the moment is downloading file-by-file by hand.
I really hope there is a workaround that actually works; or even better; that you guys actually resolve this bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.6.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Mon Apr 25 23:14:34 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110425)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-client
UpgradeStatus: No upgrade log present (probably fresh install)

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

This seems relevant:

2011-04-25 23:09:15,603 - ubuntuone.controlpanel.webclient - DEBUG - got http response 400 for uri 'https://one.ubuntu.com/api/account/'
2011-04-25 23:09:15,604 - ubuntuone.controlpanel.dbus_service - ERROR - processing failure: None
2011-04-25 23:09:15,604 - ubuntuone.controlpanel.dbus_service - ERROR - AccountInfoError: args (<ubuntuone.controlpanel.dbus_service.ControlPanelBackend at /preferences
 at 0xa4d7e2c>, {'error_type': 'WebClientError', 'error_msg': u"(400L, 'Invalid signature. Expected signature base string: GET&https%3A%2F%2Fone.ubuntu.com%2Fapi%2Facco
unt%2F&oauth_consumer_key%3DJPnbJ7C%26oauth_nonce%3D37560275%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1303765755%26oauth_token%3DVpHcYLOEJKiMJkqTIwwnIkV
aoyeVpoXeEuUitbqnhopnQsWAJX%26oauth_version%3D1.0')"}), kwargs {}.

Two things come to mind. Could it be a variation of the bad-local-time bug? Except the local time isn't incorrect.
Could it be related to the fact that Launchpad "connection has been reset" error that comes up every now and then?

The error code of 400 does not suggest such a thing, but perhaps an earlier request didn't come through?

[Martin Albisetti (beuno)]

Is the clock on your computer by any chance off?
oauth gets upset if the time is not the correct one on the client.

[Roman Yepishev (rye)]

Can also be related to LP:762004

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

No, the clock is correct. It has also been synced with the internet manually, just to make sure.

However, the language is set to English, yet the location has been set to Amsterdam. Perhaps it's getting the locale wrong, or it isn't using the proper ways to get the system time?

LP:762004 seems more likely though. Is that bug on schedule to be fixed for Natty release?

As friendly as possible, I would like to emphasize to you guys, that people tend to consider this a backup solution. You might be suprised how upset people can get when they loose their files, or access to them. So I strongly suggest you guys make Ubuntu One actually working, for people with existing accounts, a release-blocking priority.

Also, while I have your attention, when looking around at existing bug reports, many of the bugs marked as 'incomplete' have since provided the requested information. Some of those include paying customers, (assuming they aren't lying) that may be getting a little upset. If you guys have the resources, I would investigate it a little bit.

My gut says many many of those bug reports, both the incomplete ones as well as the open ones may are all symptons of the same issues. (wrong local time, bad ubuntu sso keys, corrupted cache). And like always, the people actually submitting bug reports are likely just the tip of the iceberg.

Perhaps in the future, you guys should try to get it a little more robust as well. Verifying system time, removing/resetting cache on failed connections. (because it may have been corrupted when the user ran out of the disc-space) The majority of the target audience isn't likely to be skilled enough to even execute the many 'workarounds' posted in the Ubuntu Forums.

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

It could be a duplicate, but incomplete suggests there are logs that I could provide, or something.
But all requested information is provided.

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

Regarding the priority: the files have been recovered. (broken up old laptop to get hard-drive out)

But perhaps, we should file a separate report, about being able to download all files from the web-interface at once? Something like an export-files-to-tgz button?

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

In the mean time, i've hit this bug two more times.

The scenario's:

1 x with development versions of Natty (this bug report), on new hardware
1 x with clean install of release version of Natty, before and after updating, on same hardware
1 x with clean install of release version of Natty, after updating, on same hardware

In all three cases we've used the same network/machiene name. They all were from the same IP as the original was.
In two cases we explictely synchronised the time.

Many of the workarounds have been tried in the first scenario (during development)
But not since.

[jeremy-list (quick-dudley)]

I am also experiencing the same bug on one of my machines and I'm willing to provide any necessary logs. In the meantime this bug is a minor annoyance because sync is still working on my desktop machine and I can just scp my files over, but it will be more of a problem when I put the desktop into storage and start travelling.