[Maverick]ubuntu one do not connect at new computer

Bug #625767 reported by Sergey Klimov
68
This bug affects 14 people
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

want to connect new computer at fresh install

in console after ubuntuone-preferences:

ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/bin/ubuntuone-preferences", line 1036, in got_newcredentials
    self.present()
  File "/usr/bin/ubuntuone-preferences", line 1016, in present
    self.dialog.connect_desktopcouch_exclusion()
  File "/usr/bin/ubuntuone-preferences", line 692, in connect_desktopcouch_exclusion
    self.dcouch = dcouch.ReplicationExclusion()
  File "/usr/lib/python2.6/dist-packages/desktopcouch/replication_services/ubuntuone.py", line 167, in __init__
    raise ValueError("No pairing record for ubuntuone.")
ValueError: No pairing record for ubuntuone.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Aug 28 13:44:11 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False

Revision history for this message
Sergey Klimov (nbdarvin) wrote :
Revision history for this message
Duane Hinnen (duanedesign) wrote :

Sergey,
Sorry Ubuntu One is not working as expected. If you would like to help us further debug the issue that would be greatly appreciated. Can you try connecting from the Terminal with the following command:

u1sdtool -q; u1sdtool -c

Give it a minute or two to finish authorizing and connecting. Then run the following command to get the 'Status' of the syncdaemon:

u1sdtool -s

Please post the output of that command here.

thank you,
duanedesign

Revision history for this message
Mingming Ren (portis25) wrote :

I have the same problem, here's the output:

$ u1sdtool -s
State: AUTH_FAILED
    connection: With User With Network
    description: auth failed
    is_connected: False
    is_error: True
    is_online: False
    queues: IDLE

Revision history for this message
Mingming Ren (portis25) wrote :

$ u1sync --authorize
Traceback (most recent call last):
  File "/usr/bin/u1sync", line 29, in <module>
    exit(main(*sys.argv))
  File "/usr/lib/pymodules/python2.6/ubuntuone/u1sync/main.py", line 459, in main
    do_main(argv=argv)
  File "/usr/lib/pymodules/python2.6/ubuntuone/u1sync/main.py", line 398, in do_main
    client = Client(realm=options.realm, reactor=reactor)
AttributeError: Values instance has no attribute 'realm'

Revision history for this message
Greg Ryman (ryman-greg) wrote :

I too am having the same problem.

greg@moniker:~$ u1sdtool -q; u1sdtool -c
ubuntuone-syncdaemon stopped.
greg@moniker:~$ u1sdtool -s
State: AUTH_FAILED
    connection: With User With Network
    description: auth failed
    is_connected: False
    is_error: True
    is_online: False
    queues: IDLE

greg@moniker:~$ u1sync --authorize
Traceback (most recent call last):
  File "/usr/bin/u1sync", line 29, in <module>
    exit(main(*sys.argv))
  File "/usr/lib/pymodules/python2.6/ubuntuone/u1sync/main.py", line 459, in main
    do_main(argv=argv)
  File "/usr/lib/pymodules/python2.6/ubuntuone/u1sync/main.py", line 398, in do_main
    client = Client(realm=options.realm, reactor=reactor)
AttributeError: Values instance has no attribute 'realm'

I'm on 10.10 AMD64.

Revision history for this message
Alberto (alberto-torricelli) wrote :

The same here:

alberto@alberto-laptop:~$ u1sdtool -q; u1sdtool -c
ubuntuone-syncdaemon stopped.
alberto@alberto-laptop:~$ u1sdtool -s
State: AUTH_FAILED
    connection: With User With Network
    description: auth failed
    is_connected: False
    is_error: True
    is_online: False
    queues: IDLE

alberto@alberto-laptop:~$

Revision history for this message
Alberto (alberto-torricelli) wrote :

I must add the following:

1. the following happens if I DO NOT cancel my U1 password from system/preferences/password. In this case I don't get the access to the web page that helps to add a new machine (how I did, following the instructions, on Ubuntu 10.04);

2. On the other hand, if I CANCEL the password I am able to get the window to connect to U1 (anyway without the possibility to add my new machine).

I don't know if this can help....

Revision history for this message
truant (launchpad-ninj4) wrote :

I'm getting this too.

~$ u1sdtool -q; u1sdtool -c
ubuntuone-syncdaemon stopped.

~$ u1sdtool -s
State: AUTH_FAILED
    connection: With User With Network
    description: auth failed
    is_connected: False
    is_error: True
    is_online: False
    queues: IDLE

There's a load more detail here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/630583

Didn't notice this bug report at first, so made a new one. 'pologies for that.

10.10 up to date as of 8 Sept, amd64, Acer 1410 laptop.

Revision history for this message
Duane Hinnen (duanedesign) wrote :

The fix for the authentication failures in Maverick is going to be available in the next day or two. If you are still having this issue after the ubuntu-sso-client update please let us know.

thank you,
duanedesign

summary: - ubuntu one do not connect at new computer
+ [Maverick]ubuntu one do not connect at new computer
Revision history for this message
Duane Hinnen (duanedesign) wrote :

As a workaround you can do the following:

gksudo gedit /usr/lib/pymodules/python2.6/ubuntu_sso/main.py

Near the top of the document, change the http to https in the following line :
PING_URL = "http://edge.one.ubuntu.com/oauth/sso-finished-so-get-tokens/"
so it would be:
PING_URL = "https://edge.one.ubuntu.com/oauth/sso-finished-so-get-tokens/"
Save and close the file.

Restart all the Ubuntu processes. You can do that by running this command:
killall ubuntu-sso-login; u1sdtool -q

Then open Ubuntu One (System > Preferences > Ubuntu One)

You will now if it worked if under the 'Devices' Tab it changes to your computers name instead of <Local Machine>.

thank you,
duanedesign

Revision history for this message
portis (portis24) wrote : Re: [Bug 625767] Re: [Maverick]ubuntu one do not connect at new computer

The workaround doesn't work for me.
Thank you all the same.

On Thu, Sep 9, 2010 at 3:25 PM, duanedesign <email address hidden> wrote:
> As a workaround you can do the following:
>
> gksudo gedit /usr/lib/pymodules/python2.6/ubuntu_sso/main.py
>
> Near the top of the document, change the http to https in the following line :
> PING_URL = "http://edge.one.ubuntu.com/oauth/sso-finished-so-get-tokens/"
> so it would be:
> PING_URL = "https://edge.one.ubuntu.com/oauth/sso-finished-so-get-tokens/"
> Save and close the file.
>
> Restart all the Ubuntu processes. You can do that by running this command:
> killall ubuntu-sso-login; u1sdtool -q
>
> Then open Ubuntu One (System > Preferences > Ubuntu One)
>
> You will now if it worked if under the 'Devices' Tab it changes to your
> computers name instead of <Local Machine>.
>
> thank you,
> duanedesign
>
> --
> [Maverick]ubuntu one do not connect at new computer
> https://bugs.launchpad.net/bugs/625767
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Greg Ryman (ryman-greg) wrote :

Yeah, that doesn't work for me either.

Revision history for this message
portis (portis24) wrote :

I have 2 machines, a 32bit and an amd64, both installed with maverick
and same versions of softwares.
Ubuntu-one finally works on the 32bit machine after I packaged and
installed the 0.99.5 version of ubuntu-sso-client.
But it never works on the 64bit machine, even with the 0.99.6 version
of ubuntu-sso-client.

On Thu, Sep 9, 2010 at 4:05 PM, Greg Ryman <email address hidden> wrote:
> Yeah, that doesn't work for me either.
>
> --
> [Maverick]ubuntu one do not connect at new computer
> https://bugs.launchpad.net/bugs/625767
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
lucke (lucke) wrote :

The workaround worked for me after following https://wiki.ubuntu.com/UbuntuOne/FAQ#I removed my computer, how do I add it again?

Revision history for this message
Ian Santopietro (isantop) wrote :

Same problem here. Output of u1sdtool-s is identical, running up-to-date Maverick 64 on System76 PanP7. The workaround has worked after removing and re-adding my computer; seems like it should be added as a fix. The connection should be using https anyway for security, right?

Revision history for this message
truant (launchpad-ninj4) wrote :

I haven't tried the workaround, I was waiting for the packages to be updated so I could test those instead. Since tonight's update (10th Sept), the fix duanedesign refers to is in place.

Now when I try to load ubuntuone-preferences, I get the sso login screen. I fill in my launchpad id and after "Please wait", ubuntu-sso-client closes with no error.

However, ubuntu-one-preferences doesn't show me logged in, nor does it allow me to connect/add my machine. Same goes for the website - my machine doesn't show as connected, or have the option to connect. The computer I'm using has never been connected to my Ubuntuone account.

Another difference is that ubuntu-sso-login no longer adds a uid/password pair to the keyring.

At first I manually restarted ubuntuone, but I've rebooted since updating too, just to be on the safe side.

~$ u1sdtool -s
State: READY
    connection: Not User With Network
    description: ready to connect
    is_connected: False
    is_error: False
    is_online: False
    queues: IDLE

If I then do: "u1sdtool -c" it throws up ubuntuone-sso-login, a successful login happens (if I deliberately use the wrong credentials, it fails and tells me so), then u1sdtool -s gives the same output as above.

Revision history for this message
Alberto (alberto-torricelli) wrote :

The same to me: even after installing the new package I was not able to get the "add machine screen" as I did in Ubuntu 10.04

Wheb I run u1sdtool -s the answer is different from above:
~$ u1sdtool -s
State: QUEUE_MANAGER
    connection: With User With Network
    description: processing queues
    is_connected: True
    is_error: False
    is_online: True
    queues: IDLE

Revision history for this message
truant (launchpad-ninj4) wrote :

ubuntu-sso-login also crashes from time to time too, after entering username/password (ie, while the "Please wait" animation is displayed). Apport says:

"The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes."

Revision history for this message
truant (launchpad-ninj4) wrote :

Not sure if this is relevant, but if I put any files in my ~/Ubuntu One folder, I get a message at startup saying my Ubuntu One storage is full and a link to upgrade.

Revision history for this message
portis (portis24) wrote :

The 1.4.1 version fixes my problem.

On Mon, Sep 13, 2010 at 5:45 PM, truant <email address hidden> wrote:
> Not sure if this is relevant, but if I put any files in my ~/Ubuntu One
> folder, I get a message at startup saying my Ubuntu One storage is full
> and a link to upgrade.
>
> --
> [Maverick]ubuntu one do not connect at new computer
> https://bugs.launchpad.net/bugs/625767
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Mingming Ren (portis25)
Changed in ubuntuone-client (Ubuntu):
status: New → Fix Released
Revision history for this message
Duane Hinnen (duanedesign) wrote :

The new code has made it to the Maverick repos. If you tried an AUTH with the broken client you might have to go into Seahorse (System -> Preferences -> Password and Encryption keys) and delete the Ubuntu One Token. So the steps would be:

1. Make sure you are fully up to date. Run all updates.

2. Close the Ubuntu One Preferences and open a Terminal (Applications -> Accessories -> Terminal)and run the command:

killall ubuntu-sso-login

3. Open Seahorse (System -> Preferences -> Password and Encryption keys) and delete the Ubuntu One Token.

4. Then open Ubuntu One Preferences (System -> Preferences -> Ubuntu One). You should be prompted to add your computer. this new token should work.

thank you,
duanedesign

Revision history for this message
truant (launchpad-ninj4) wrote :

Thanks for the update. I have followed your instructions, and there has been some changes, but it's still not working correctly.

I can now login with ubuntu-sso-login (although it still crashes with an assertion failure from time to time), and Ubuntu One Preferences now shows an "Upgrade your subscription" link, which it didn't before.

I can't, however, connect to my Ubuntu One space. Preferences panel shows "Disconnected" above the tabs.

My computer is still called <LOCAL MACHINE> and, if I click "Connect" it relaunches sso-login, where I log in, and am returned to Preferences with no change. Clicking "Restart" has no effect other than to un-grey "Connect"

No token is saved in Seahorse.

If there's anything else I can do to help pin this down, please let me know.

Revision history for this message
truant (launchpad-ninj4) wrote :

More attempts, more differences, some success.

Seahorse - on the fourth try - created an Ubuntu One token. Not when loading Preferences - although sso-login did run and allow me to try and login - but success only happened after clicking "Connect" in an existing Preferences screen.

Once this token had been created, I could finally connect my machine. Sync has successfully occurred.

However. There were 21 instances of my machine listed in the Preferences screen (see attached). They vary between being called:

Ubuntu One @ ioko
Ubuntu%20One - ioko
Ubuntu - ioko

My other two machines were listed by their hostnames only.

Looking on one.ubuntu.com shows each instance of my machine has a different unique ID, so this may just be an artifact of my many attempts to connect. The many copies were removed - individually - OK by clicking 'Remove'

Overall, I think it's working. I've got another virgin Maverick system I can double-test this on later.

Revision history for this message
Alberto (alberto-torricelli) wrote :

I removed and reinstalled ubuntu one.

Before I have removed ubuntu one entry from password encryption too.

When I run System -> Preferences -> Ubuntu One I do not see the "add computer" screen but I am requested to setup a new account or log in.

I log in and in "computers on your account" now I see several machines added (same name and different id). I cancelled all of them except the firs one.

At this point the GUI in the preferences menu opens properly: I can see my name/email/machine and I am able to syncronise.

It seems it works properly except that I don't have any more neither the option ("right click") to syncronise folder nor the check box in the folder itself. Moreover on the icons I don't see the symbols showing that files/folder are syncronised or that the process is going.

Revision history for this message
Alberto (alberto-torricelli) wrote :

Update: after restarting everything works.
So I thing it is to fix the lack of "add computer screen" and the multiple istances.

Bye

Revision history for this message
truant (launchpad-ninj4) wrote :

Currently fully up to date and still seeing multiple (40-ish) instances of my machine appear on "first*" connect.

* u1sdtool -q, remove U1 token from seahorse, restart ubuntuone-preferences

If I remove machines through U1Prefs, they don't go from the website. Some attempts return an error:

"org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.sso.ApplicationCredentials was not provided by any .service files"

This crashes U1Prefs hard enough I have to kill manually.

Revision history for this message
Rafael Mendonça França (rafaelfranca) wrote :

This line in my log show the problem: 2010-10-23 12:24:12,252 - ubuntuone.SyncDaemon.DBus - INFO - u'CredentialsFound': callbacking with credentials (token_name: None).

The ubuntu one is not sending the currect credentials.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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