Sergei,
Looking at the logs from comment #9 it looks like that computer is connecting 
to U1 file sync server.

2010-09-27 16:38:51,138 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK
(state: <State: 'QUEUE_MANAGER'  (queues IDLE  connection 'With User
With Network')>; queues: metadata: 0; content: 0; hash: 0, fsm-cache:
hit=9022 miss=13697) ----

'With User With Network' means you are connected. You can get this
status by running the following command in a Terminal:

u1sdtool -s

queues:IDLE means it currently has no files to sync. You should be able
to drop a test file into your Ubuntu  One folder and it should sync to
the cloud and appear at https://one.ubuntu.com/files

Tomboy Notes Sync works separately from the Ubuntu One file sync. So File Sync 
can work while Note Sync does not, and vice-versa. To debug the note sync, 
first lets make sure you have followed these steps to authorize the note sync. 
https://wiki.ubuntu.com/UbuntuOne/Tutorials/Notes

NOTE: Even though you may have done this already for setting up file
sync you need to do this again for Tomboy. It's helpful to put "Tomboy"
in the name in order to identify this entry as being for notes sync.

If you have followed those steps and Tomboy still will not sync you can get 
debug info with the following steps.
1. Quit Tomboy
2. Applications->Accessories->Terminal, and run:

     tomboy --debug > ~/tomboy_debug.log

3.Try to reproduce the bug and then attach ~/tomboy_debug.log to a bug
report


On the second computer that started to spike the CPU, is this computer also 
running Ubuntu(Lucid) 10.04?
Some things to look for:

1. check the permissions of the file and make sure you are the
group:owner and not root:

ls -la Ubuntu\
One/Java/examples/ch06/fig06_09_10/.CrapsTest.java~.XuCZs6

2.check  whether   /tmp has enough space...

3. Copy and paste the contents of the file to another file and remove it

Let us know how it goes.

thank you,
duanedesign

-- 
U1 does not connect or connects erratically
https://bugs.launchpad.net/bugs/638858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to