Ubuntu One - displays incorrect captcha on SSO creation failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Servers |
Invalid
|
Undecided
|
Unassigned | ||
ubuntuone-client (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
I just made an error when creating an Ubuntu One account by using an email address that already had an SSO. This caused the account creation process to fail (not unreasonably) but in doing so I discovered the following issue:
When I filled in the account creation dialogue a captcha was displayed. I entered the words I saw and the submitted the form. The captcha was accepted but the form submission failed due to the email address I was using already existing. The dialogue was returned to me to correct my error with the same captcha picture displayed and the captcha field still filled in with the answer I gave before that was accepted.
I submitted the form again and the submission failed with the reason given that I had incorrectly completed the captcha even though the same picture and answer were displayed. The only way to get it accepted was to hit the captcha refresh button and enter the new words. Clearly either the wrong captcha graphic was displayed or the correct answer was rejected.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.4.4.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
Date: Tue Oct 12 19:09:12 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOnePrefer
2010-10-12 18:35:56,448 - ubuntuone-
2010-10-12 18:51:29,971 - ubuntuone-
2010-10-12 18:51:35,272 - ubuntuone-
UbuntuOneUserSy
[bandwidth_
on = False
read_limit = 2097152
write_limit = 2097152
tags: | added: desktop+ |
This is a know issue (see bug #634593) and was already fixed on new releases. I'm closing this as invalid since this bug belongs to other project.
Thanks for the report!