The thing it that in the middle of syncronization it gets stucked in the standoff state without notifying of this. Before getting stucked, it looses the connection. 2010-02-10 16:29:17,751 - ubuntuone.SyncDaemon.ActionQueue - WARNING - connection lost: Connection was closed cleanly. 2010-02-10 16:29:20,599 - ubuntuone.SyncDaemon.ActionQueue - INFO - Protocol version OK 2010-02-10 16:29:51,505 - ubuntuone.SyncDaemon.ActionQueue - WARNING - connection lost: Connection was closed cleanly. 2010-02-10 16:30:05,870 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: START_STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ---- 2010-02-10 16:32:05,870 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: START_STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 634; content: 1076; hash: 0, fsm-cache: hit=106467 miss=1420) ----
-- The client gets stuck into STANDOFF state https://bugs.launchpad.net/bugs/487257 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
