Ubuntu One Client

cannot connect to localhost for OAuth

Bug #461614 reported by wesmagyar
112
This bug affects 21 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Won't Fix
High
John Lenton

Bug Description

i installed it following the guide on launch pad and when i launched it it pulled up a website that said it couldnt connect to local host. then when i tried to connect the client it pulled up the bug report thingy.

ProblemType: Bug
.home.wes..cache.ubuntuone.log.oauth.login.log:
 2009-10-26 15:59:54,942:942.533969879 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.1
 2009-10-26 18:32:08,027:27.2829532623 UbuntuOne.Client.Applet DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
.home.wes..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 show_applet = 1
 connected = True
 connect = 0
 bookmarked = True
Architecture: i386
CrashDB: ubuntuone
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia wl
Package: ubuntuone-client 1.1+r269-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.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

Revision history for this message
wesmagyar (wesmagyar) wrote :
Revision history for this message
Rick McBride (rmcbride) wrote : Re: ubuntu one wouldnt connect and then crashed w/ d-bus error

I'm seeing reports of this non-connection, referrencing the same dbus error on Freenode while working with users. I can't seem to locate the original master for this issue, so I'm making this the new master report until I find out otherwise.

Changed in ubuntuone-client:
status: New → Confirmed
importance: Undecided → High
summary: - ubuntu one wouldnt connect and then crashed
+ ubuntu one wouldnt connect and then crashed w/ d-bus error
Changed in ubuntuone-client:
assignee: nobody → Lucio Torre (lucio.torre)
summary: - ubuntu one wouldnt connect and then crashed w/ d-bus error
+ ubuntu one wouldnt connect and then gets d-bus error: did not recieve
+ reply
Revision history for this message
Roman Yepishev (rye) wrote : Re: ubuntu one wouldnt connect and then gets d-bus error: did not recieve reply

Full oauth debug log as discussed over IRC.

The bottom line is that ubuntuone-client-applet calls to syncdaemon do not complete in time under high system load.

In my case gnome starts trackerd applet, Empathy, Tomboy, indicator applets and everything competes for the CPU and disk.

Revision history for this message
Joshua Hoover (joshuahoover) wrote :

See http://irclogs.ubuntu.com/2009/11/13/%23ubuntuone.html#t17:53 for more info. It sounds like this happens when syncdaemon is working on a lot of metadata. There is supposed to be a bug for optimizing fixing the scanning of metadata but I was unable to find it so I'm leaving this comment on this bug as a reminder. :-)

Revision history for this message
Facundo Batista (facundo) wrote :

This seems to be the applet that does not get any response from the syncdaemon (but nothing seems to be wrong there (no exceptions log updated automatically here), so most probably syncdaemon is not started yet).

Maybe the applet should support better this "no answer"?

Changed in ubuntuone-client:
assignee: Lucio Torre (lucio.torre) → John Lenton (chipaca)
Revision history for this message
papukaija (papukaija) wrote :

I'm confirming this bug with dbus error about syncdaemon.

Revision history for this message
Roman Yepishev (rye) wrote :

@Facundo Batista Re: "most probably syncdaemon is not started yet"

Observed on my real (i.e. not vm) PC: gnome-session starts, Empathy, Trackerd are loading and then the hard drive is completely possessed by ubuntuone-syncdaemon, with applet not displaying the Icon (in order to avoid the flickering, as the sources say). Then the applet pops up and says we are disconnected. So syncdaemon is started but not ready to service DBus requests.

Revision history for this message
Roman Yepishev (rye) wrote :

This bug report should not be used as a master bug report for startup failure due to d-bus timeout.
The original reporter said:
"when i launched it it pulled up a website that said it couldnt connect to local host"
So it can be something related to local HTTP server failure (for OAuth response), browser accessing localhost over IPv6 socket (IPv4-only socket is created by syncdaemon) etc.

Revision history for this message
tz (thomas-mich) wrote :

Someone just marked a much different path but failure to sync as a duplicate of this bug.

(In my case killing and manually restarting the syncdaemon fixed it, and I tend to use wireless roaming - multiple access points on different networks during the day). It also didn't present any error messages (it just said my files were in sync when they weren't).

Roman Yepishev (rye)
summary: - ubuntu one wouldnt connect and then gets d-bus error: did not recieve
- reply
+ cannot connect to localhost for OAuth
Revision history for this message
Alejandro J. Cura (alecu) wrote :

The mechanism to retrieve OAuth credentials was changed from the previous versions, so this error is no longer valid.

Changed in ubuntuone-client:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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