Scott, thanks for the logs :)
The actual startup of the syncdaemon is taking ~5s, see the inline
comments:
>2009-07-17 16:29:08,672 - ubuntuone.SyncDaemon.fsm - INFO - loading updated
>metadata
>2009-07-17 16:29:08,849 - ubuntuone.SyncDaemon.fsm - INFO - initialized:
>idx_path: 1, idx_node_id: 0, shares: 1
Most of the startup time is in this step: (~4s):
>2009-07-17 16:29:08,862 - ubuntuone.SyncDaemon.HQ - INFO - HashQueue: _hasher
>started
>2009-07-17 16:29:12,873 - ubuntuone.SyncDaemon.DBus - DEBUG - using the real
>system bus
I have a branch, that's going to be proposed today, that fix this and
now the step above takes ~0.2s (would be nice to test this in a similar
netbook)
>2009-07-17 16:29:12,885 - ubuntuone.SyncDaemon.Main - INFO - Using
>/home/ubuntu/Ubuntu One/My Files as root dir
>2009-07-17 16:29:12,885 - ubuntuone.SyncDaemon.Main - INFO - Using
>/home/ubuntu/.cache/ubuntuone/syncdaemon
.....
> 2009-07-17 16:29:12,958 - ubuntuone.SyncDaemon.EQ - DEBUG - push_event:
> SYS_STATE_CHANGED, args:(), kw:{'state': <SyncDaemonState READY_FOR_NETWORK>}
At this point the syncdaemon is fully initialized
> 2009-07-17 16:29:26,867 - ubuntuone.SyncDaemon.EQ - DEBUG - push_event:
> SYS_NET_CONNECTED, args:(), kw:{}
> 2009-07-17 16:29:26,868 - ubuntuone.SyncDaemon.State - DEBUG -
> READY_FOR_NETWORK --[SYS_NET_CONNECTED]--> READY_WITH_NETWORK
> 2009-07-17 16:29:26,868 - ubuntuone.SyncDaemon.EQ - DEBUG - push_event:
> SYS_STATE_CHANGED, args:(), kw:{'state': <SyncDaemonState READY_WITH_NETWORK>}
The last 3 logs are related to a dbus call to NetworkManager.
I'll take a look why this NetworkManager dbus call is taking so long.
Regards,
--
ubuntu one client takes too long to start
https://bugs.launchpad.net/bugs/400746
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
