Playing Around with Ubuntu One (Pt. 2)

In the first post of my tests regarding Ubuntu One, I described a bit how the general principle of Ubuntu One works and what I’ve experienced while setting it up on one Ubuntu client. Now, I got a bit deeper into the service by cloning the Ubuntu machine and also authorizing the second Ubuntu client for the Ubuntu One service.

As I’ve written, moving the application-folders into the cloud seems to be working pretty good on one client. Now I’ve tested, how it is when using two clients and pulled the information contained in the cloud (from client A) down to client B. Each of the three applications worked in general, Pidgin started with the account configured on client A, Evolution started with the Inbox configure in client A but asked me for the password to access the mail-server (what’s clear, because I did not synchronize the key-rings) and Firefox displayed with the preferences configured, but prepended a message box that said:

Could not initialize the application’s security component. The most likely cause is problems with files in your application’s profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.

This confused me a bit, especially since the actual browser ran without any more problems. However, I’ve been to lazy to track down this permission problem.

After I’ve checked, if “one-after-another” synchronization worked, I tried out the simultaneous usage of both machines, while being connected and synced with the cloud on each of them. As I’ve expected, I ran into some problems: Suddenly, some more folder (thumbnail) appeared within the client B’s Ubuntu One folder, that contained his app-information. The folders remained until the actual Home folder finished receiving the data from within the cloud, then they just disappeared. I don’t know, if those have been merged or just deleted – it just worked afterwards.

Ubuntu One seems to be using “semaphores”, in a similar way token-ring was using: At first, client A is allowed to sync his data with the cloud. When this is finished, client B is allowed to sync. Then, it’s client A’s turn again – and so on. Theoretically, this is good. But in practice, Ubuntu One unfortunately seems to overwrite locale changes when pulling data down from the cloud. In comparison: MobileMe asks the user and merges the data, as good as possible.

In the end, simultaneous usage was unable to sync both machines in a way, so that data was kept consistent. Either one machine lost information, or the other. Especially when adding a new Pidgin account on client B, waiting for the sync, closing Pidgin on client A (which then seems to save a final account-info) and waiting for the sync there, you will be surprised your account not to be available when re-launching Pidgin on client A.

Of course, synchronization always is a tricky feature, but I guess, Ubuntu One lacks of an SVN-like back-end, that keeps track of all changes and makes merging possible. I’m really interested in how Ubuntu One will continue to evolve and I’ll try to keep tack of its development status. This could really kick ass someday, as soon as everything works seamless and simultaneous.