Public bug reported:
Binary package hint: ubuntuone-client
This is something that's been present w/ u1 client for forever, and it's
really annoying...
bladernr@klaatu:~$ u1sdtool --start
Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 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.
After boot up, running u1sdtool always results in dbus NoReply errors
for quite a while. This can take anywhere from several minutes to
maybe 30 - 45 minutes after bootup before you can get any sort of info
from u1sdtool and syncdaemon.
For example, I've been booted for about 10 minutes now. I ran u1sdtool
--start immediately after boot (I have the auto-start disabled for now
as I found the syncdaemon was deleting stored data when I tried
sharing/syncing the same folder between two different computers.
bladernr@klaatu:~$ uptime; u1sdtool -s
21:33:55 up 9 min, 3 users, load average: 0.60, 1.13, 0.72
Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 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.
So for quite a while after bootup, the user has no way of really knowing
whats going on with Ubuntu One. This is the only thing the
syncdaemon.log has to offer after 10 minutes of run time:
bladernr@klaatu:~/.cache/ubuntuone/log$ cat syncdaemon.log
2011-01-30 21:33:57,642 - ubuntuone.SyncDaemon.VM.MD - DEBUG - metadata
version: 6
2011-01-30 21:33:57,646 - ubuntuone.SyncDaemon.fsm - INFO - loading updated
metadata
Now, more than 15 minutes after startup:
bladernr@klaatu:~$ uptime; u1sdtool -s
21:41:09 up 17 min, 3 users, load average: 3.41, 2.31, 1.33
Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 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.
This is on a system running Maverick with the latest updates as of 30
January 2011.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.4.5-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Jan 30 21:30:38 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOneClientConfig:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
UbuntuOneOAuthLoginLog: 2010-06-09 12:52:38,627:627.223968506 ubuntuone-login
Starting Ubuntu One login manager version 1.2.1
UbuntuOneSyncdaemonExceptionsLog:
UbuntuOneUserSyncdaemonConfig:
[bandwidth_throttling]
read_limit = 2097152
write_limit = 2048
on = False
** Affects: ubuntuone-client (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710438
Title:
ubuntuone-client is completely unresponsive for a long time after
boot.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
