** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: ubuntuone-client (Ubunt
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntuone-client
Status: Fix Committed => Fix Released
--
The client gets stuck into STANDOFF state
https://bugs.launchpad.net/bugs/487257
You received this bug notification because you ar
** Changed in: ubuntuone-client (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: ubuntuone-client
Status: Triaged => Fix Committed
--
The client gets stuck into STANDOFF state
https://bugs.launchpad.net/bugs/487257
You received this bug notification because you are a member
This can be also seen when there is some kind of network issue with
uplink but NM does not detect that there is some kind of interruption
(i.e. it actually can't do that, physically link is still present).
--
The client gets stuck into STANDOFF state
https://bugs.launchpad.net/bugs/487257
You rec
** Branch linked: lp:~facundo/ubuntuone-client/states-refactor
--
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@l
** Tags added: aq-connection-lost
--
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
** Tags added: chicharra
--
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.c
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
Hi, I think that I have the same problem here. It get stuck in STANDOFF state,
the last lines of the log are this ones:
2010-02-10 10:44:32,940 - ubuntuone.SyncDaemon.Main - NOTE - MARK (state:
STANDOFF_WAITING_WITH_NETWORK_WITH_BOTHQ; queues: metadata: 151; content: 83;
hash: 0, fsm-cache:
1. Start ubuntuone, verify that it is working and it is ready for file uploads
2. Put file to the directory, wait until it is picked up for upload.
3. Verify that upload is started by u1sdtool --current-transfers.
4. Before upload compeltes, suspend the system.
5. drink some tea
6. Unsuspend the sy
** Changed in: ubuntuone-client (Ubuntu)
Importance: Undecided => High
--
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
ub
** Summary changed:
- UbuntuOne does not sync properly and sometimes not at all
+ The client gets stuck into STANDOFF state
--
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 sub
12 matches
Mail list logo
