ubuntu one does not connect

I can confirm that this is also a problem on my system. Other programs can accesses the internet successfully, but the Ubuntu One Client doesn't connect.

Hi Jatin and Kåre,

It appears we're having some server issues that are causing these errors. We're working on a fix currently. My apologies for the inconvenience.

Joshua

I closed the client, and restarted... it asked me to re-authorize my machine, after that it connects OK. It appears to be syncing now, but the notifications don't seem to be happening as before.

just an update the ubuntu one client icon has changed over last few updates, but still can't connect. I guess the servers are still being fixed? and its not a client issue.

Just a correction, after a reboot the notifications started again, so I think all is well at the moment. Jatin, try closing the client, then restart from the Applications -> Internet menu. For me, this prompted me to re-authorise my machine and the problem has gone.

James - i did all that. I even removed and re-installed the ubuntu one client. Not sure where it is broken. Is there same way to get it to forgot my authorization?

You could go to your account on the web, and remove the authorization for that computer then restart the client... although TBH I find the U1 authentication mechanism much less than transparrent... it would help to have some way to get clearer information regarding what's going on from the applet... such as authentication options and errors, as well as other things like the time of the last file sync.

i removed my machine from the ubuntu one web account - removied client, reinstalled, restarted - still no go. I am still stuck at the same place. There must be a local option to forget my authorization - some directory under home?. Clearly if its not even speaking to the web account and even if after clean install it just picks credentials from some local place.
running from command line gives no messages just this at start
"jatin@jassi:~$ ubuntuone-client-applet
ERROR:dbus.proxies:Introspect error on org.freedesktop.NetworkManager:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files

(nautilus:3504): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
"
attached screenshot of current status

ok one more thing - i can't change any preferences. i goto prefs and changing something and close. Then when i open prefs again, the prefs are back to defaults with no changes.
I think there is some local directory i need to delete to re-initialize the client - any hints?

after rebooting i always see a notification saying ubuntu one is updating my files - but obviously that isn't happening.
screenshot of the same is attached.

Update - I am still living with a non-working uubuntu one. The client just sits with an exclamation mark and does not make any attempts to connect. The local ubuntu-one folder does not connect and sync.
I found an ubuntu one folder under /etc/xdg - this has some config files- anything i can do there? to get this to reconnect.
Hope I don't need to do an OS re-install to get this function back.

screenshot of ubuntuone client sitting disconnected with an exclaimation mark in the tray and the greyed out notification indicating it is updating files after booting up.
Can someone tell me how to get to a fresh install - removing everything related to ubuntuone (client, python libs, couch evolution plugin,, et al) does not help.

ok here is my syncdaemon.log and oath-login.log from /home/user/.cache/ubuntuone/log
It looks like it has something to do with not being able to get my network manager status?

maybe because i use wicd?

I've noticed this morning that my 9.04 machine isn't able to connect to U1 either... I've not had time to try anything to make it re-connect other than close and re-open and re-authorise the machine, but it may be the same problem, more to follow.

ok i tried with changing from wicd to network manager. Still no go!
Just that now when i click connect on the ubuntu one client - it does some cloud like animation and goes back to the exclamation mark and remains disconnected.

Jatin, thanks for your bug report, and all the follow-ups. I'm tagging this bug for a developer to look into. Please continue to add information here as and when you find it. Thanks.

brand new symptom today.

the usual behavior was when i clicked on the panel icon and selected connect, it would do the cloud animation and immediately goto the exclamation mark disconnected phase as evidenced in above screenshots.
The same would happen when I clicked connect from the ubuntu one folder.

However, today the client is doing the cloud animation thingie and trying to connect continuously for over an 2 hours now - see attached screenshot

i am thinking if this is a server side issue with my account? Does anyone else have any issues - or possibly mine is a corner case where-in the client got screwed - however there must be some way to do get this working without doing a complete OS re-install

I did

1. Quit the UbuntuOne applet
2. rm -rf ~/.config/ubuntuone
3. Applications -> Internet -> Ubuntu One.

Everything works fine. Sync is perfect.

i get a capabilities mismatch with server message now
attached screenshot

The "Capabilities Mismatch" is a known issue that we're working to resolve. If you're using the beta PPA, you can run Update Manager and get the fix. Non-beta users will have the fix soon. Follow bug 462828 or our blog (http://one.ubuntu.com/blog/) for further updates.

last update works fine for me. I had to select all kind of sources in "update manager" to get the update. Default settings would not tell me that there is a new version of Ubuntu One.

I Want to Confirm that the solution posted by swamytk (comment #22 ) did the work for me.

Is AMAZING! It's working now!!!!

Thanks.

Hi Alan,

The solution posted by swamytk probably is the workaround proposed for Bug #455544

There is a fix already proposed, so it'll be available in the nightly and beta ppa in a few days

#22 fixes it, yeah

Ops... Now it's fixed: In my case I deleted the Ubuntu One folder after trying it and removing it on Jaunty. The ~/.cache/ubuntuone/log/syncdaemon.log said

   OSError: [Errno 2] No such file or directory: '/home/user/Ubuntu One'

, so I just recreate the folder and now everything is working like a charm!

Maybe the ubuntuone-client-applet should be more resilient and recreate the folder itself...

Yesss! Thanks. I never know how developers understand these things!

Oh wait. I cant seem to open Ubuntu One again.
When I go to Apps>Internet>Ubuntu One it shows the preference menu and when I close it, nothing happens!

Hi linux, If you want to see the client, be sure to set the client to "Always" show and then you can run the following command to quit the client from a terminal session: killall ubuntuone-client-applet ubuntuone-syncdaemon

Once you've quit the client from the terminal session, you can start the client from Applications->Internet->Ubuntu One and it should always show going forward.

Thank you,

Joshua

I confirm the solution given from swamytk on 2009-10-25.

Thank you very much!

Marco

I confirm the solution from swamytk on 2009-10-25.

Thank you

Jose

is anyone still having problems - mine just stopped working yesterday! It won't connect anymore.

I use gdm autologin, but "ubuntu one" every time ask me for the password in gnome keyring. Before I give the password it doesn't connect, so I need to connect manually, despite it is configure to connect automatically. Could "ubuntu one" works like "dropbox", whith autologin and without askyng for password?
thank's
Jose

Jatin,

the problem you're having is surely sue to the throttling setting for syncdaemon. Could you please follow the instructions in this FAQ https://answers.launchpad.net/ubuntuone-client/+faq/835 ?

I believe you'll be able to make it work that way. Let us know, good luck!

A lot of people reports that this was fixed.

Jatin, please check Naty's fix from comment #37... if you still have any issue, please open a new bug because surely it's another problem.

I'm marking this as fix released. Thanks everybody for your time and help!