** Changed in: ubuntu-sso-client (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696361
Title:
Ubuntu sso fails with 'An HTTP non-2xx response code w
Closing due to lack of response.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696361
Title:
Ubuntu sso fails with 'An HTTP non-2xx response code was received'
--
ubuntu-bugs mailing list
ubuntu-b
Hi Noel,
I would guess your box does not have the time and date set properly.
Ubuntu Single Sign On, as many other auth services, uses OAuth. the
latter requires that your box has the correct date and time to work
properly.
Can you confirm you have correctly set the time and date, and, even
bette
I am Seeing the above issue.
removing this machine from ubuntuone "your machine" list
https://one.ubuntu.com/account/machines/
completely removed ubuntuone, tomboy, etc. re-installed. Made sure there
is no ubuntuone listed in preferences->passwords and keys
With
env DEBUG=1 /usr/lib/ubuntu-sso-
Found it! The token is called "UbuntuOne," but the one I deleted
earlier was called "Ubuntu One" IIRC.
After connecting, the preferences UI showed my other Maverick system
logged in multiple times. This is strange, since I had deleted those
before and, as on this Maverick machine, I completely f
That did start ubuntuone-syncdaemon, but as always, there's no sign of a
login dialog.
FWIW I had no trouble logging in with a Lucid machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696361
Titl
According to your oauth-login.log, you did have an Ubuntu One token as
per:
2011-01-07 13:34:24,058:58.7830543518 - ubuntu_sso.main - INFO -
keyring_get_credentials: app_name "Ubuntu One", resulting credentials is not
None? True
2011-01-07 13:34:24,059:59.051990509 - ubuntu_sso.main - INFO - SSO
Actually I didn't have an Ubuntu One token locally, since I had removed
it at the same time as the server-side ones.
As for the killalls, ubuntuone-syncdaemon and ubuntuone-preferences were
not running; ubuntu-sso-login was.
--
You received this bug notification because you are a member of Ubunt
Jeroen,
since you removed all your token server side, you need to remove your
local token. To do so, please open seahorse (System -> Preferences ->
Passwords and Encryption Keys) and remove the token named 'Ubuntu One'.
Then, in a terminal, please do:
u1sdtool -q
killall ubuntuone-syncdaemon
kill
Just one log file in ~/.cache/sso.
** Attachment added: "oauth-login.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/696361/+attachment/1786674/+files/oauth-login.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Oh well. I just deleted all the Ubuntu One tokens (which were all for
my other machine) and restarted the U1 prefs. This time it gave me a
Connect option! Very briefly it said it was synchronizing, and then it
went back to Disconnected without the option to connect.
I'll attach logs.
--
You r
There was only one entry in the machines list; I have no idea how to see
whether it's "unused" or not or which machine it is, so I just deleted
it.
The tokens list has about a dozen tokens from my other machine, all for
the same date (I guess those were login attempts I tried from there
after upgr
Hello all,
the error 'An HTTP non-2xx response code was received' is returned from
the SSO server to the local sso client, so please:
* check that the date and time are correct in your system, OAuth depends
on this value to be correct in order to work (that's a requirement
specific to OAuth)
* c
@Jeroen: "" is what I got when I still had an entry for
"Ubuntu One" in "preferences / passwords and encrypted keys" (inside the
Passwords:login item). Deleting that (and probably the reboot but I
didn't need to reboot my 2 other machines) unblocked me.
--
You received this bug notification becau
I'm still having the problem. I also tried removing all connected
devices, though from the desktop client. (This is also Maverick BTW).
I also rebooted a few times since then. But I still can't connect; my
connection status is permanently "Disconnected," my usage meter says 0.0
KB (0.0%), the De
Hmm, while looking at the Ubuntu One Preferences, the devices tab shows
no less than *15* entries for the machine I was trying to register.
So I went ahead and tweak some more:
- deleting the first entry (presumably the successful registration)
worked as expected: I got prompted for login/passwor
/me blinks
I went to the u1 website, deleted what remained there (probably from
lucid registration) for the failing machine. Try again some more. Get no
results.
Rebooted.
Try once more, it worked...
So the problem is solved as far as I'm concerned, let me know if I can
still collect data t
Also note that I'm using u1 from another machine (also under maverick)
without problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696361
Title:
Ubuntu sso fails with 'An HTTP non-2xx response c
Same problem here after an upgrade to maverick for a machine that has
been working fine with u1 in the past.
As indicated in https://wiki.ubuntu.com/UbuntuOne/Bugs, I did reset my
previous key from gnome-keyring, tried connecting and got this error.
Let me know if I can provide more info or where
** Attachment added: "Screenshot, showing the error."
https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/696361/+attachment/1781409/+files/Connect%20to%20Ubuntu%20One_001.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
20 matches
Mail list logo
