It does not connect. I put files in and nothing happens, even if I press "connect" on either the folder view or the applet at the top. The icon at the top always has a red x. I've re-installed and tested and still have the same problem.

[Ben]

Hi, files put in the ubuntu folder will not sync. Connect button on either the folder or applet do not seem to work. Nothing is being uploaded, nothing appears on the web interface. I've re-installed but with no luck.

ProblemType: Bug
.home.ben..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 0
 on = True
.home.ben..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 1
Architecture: i386
CrashDB: ubuntuone
DistroRelease: Ubuntu 9.04
MediaBuild: Xubuntu 7.10 "Gutsy Gibbon" - Release i386 (20071016)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.1+r283-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.28-16-generic i686
UnreportableReason: This is not a genuine Ubuntu package

[John O'Brien (jdobrien)]

From the looks of things, you client never authenticated. When you started the client, did you get a web page asking you to authorize your computer?

[WojtekNowak (nowak-w)]

I have the same problem. In my case in file oauth-login.log is:
"Unable to contact NetworkManager".
My client never was authenticated because it never connected.

[Janne Nykänen (finguin)]

So far, my 64 bit karmic installation has never been working, so nothing changed after 4.December upgrade.

$ cat .cache/ubuntuone/log/oauth-login.log
2009-12-04 07:30:22,580:580.888032913 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.1

I keep getting red x icon. Logging in goes smoothly, but after connect x does not disappear and the folder is not synching.

[Janne Nykänen (finguin)]

I noticed if I start ubuntuone-client-applet in command line, the following error message appears:

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-client-applet", line 162, in __new_credentials
    self.set_up_desktopcouch_pairing(consumer_key)
  File "/usr/bin/ubuntuone-client-applet", line 337, in set_up_desktopcouch_pairing
    db = CouchDatabase("management", create=True)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/records/server.py", line 50, in __init__
    desktopcouch.find_pid()
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 29, in find_pid
    pid = start_local_couchdb.start_couchdb()
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 300, in start_couchdb
    username, password = create_ini_file()
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 128, in create_ini_file
    True)
DeniedError

[Chad Miller (cmiller)]

DeniedError is the result of gnome keyring refusing to let us access its credentials. As far as I know, the only reason for that is the user pressing "Deny" when the keyring pops up a window and asks "Allow application access to keyring?" We must have (write-) access to the Ubuntu One credentials, or else we can not store the data for applications to use.

Run "seahorse" or Apps/Accessories/Passwords-and-encryption-keys . Look for Desktop Couch user authentication. If any exist, remove them.

When you start the applet again, if you get the question about allowing access to desktopcouch service or applet, this time Allow it.

[Janne Nykänen (finguin)]

It works now!

Something changed after upgrading to the version 4th December after all, because on Monday (i.e. yesterday) when I came to work and started the computer (so, basically, after rebooting the system), it worked! I didn't know that a reboot was needed, so my bad.

Believe me, earlier I really tried all the possible tricks including reinstalling everything and deleting all the local files under "hidden" (dot) folders under my home directory (many times, and always after installing a new ubuntuone version). So, I guess this had nothing to do with pressing Deny (which I did not do).

Anyway, thanks guys, finally it works also in Karmic (I've been using it succesfully with no problems in two Jaunty installations).

[Joshua Hoover (joshuahoover)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 488413, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.