Ever since the Ubuntu One cloud service played an important role in Ubuntu 10.04, a new prototype of a KDE client has become available. A port to Fedora is also in the works.

Kubuntu One?

Kubuntu users are staying on track with Canonical's cloud service in more ways than one. First, there is no native client, only the GNOME applet, and second, the service might synchronize Tomboy notes and the Evolution address book, but no KDE files.

This should all change with the upcoming Lucid Lynx 10.04 release. Kubuntu developer Harald Sitter is working on a native KDE client for Ubuntu One. As he says in his blog, a first tech preview is available for download. The program is still rather buggy and is truly just a prototype not to be used on a daily basis with Ubuntu One.

The Ubuntu One client for KDE is still merely a prototype.

Once the primary support for KDE is built in, the applicable Akonadi CouchDB integration will make synchronizing with favorite KDE PIM files possible. This should make the upcoming months exciting for Kubuntu users.

Fedora too?

Independent of the Kubuntu project, Fedora developer Thomas Vander Stichele is working on an Ubuntu One client for Fedora. Because Ubuntu One is at least partially a closed code project, it creates somewhat of a challenge. The Ubuntu developers have cooperated, however, so that a corresponding patch to the original source code now makes it possible to use the basic functions with Fedora. The patch was necessary because the Ubuntu 9.10 client had a serious bug and Canonical purposefully excluded this client version on the server side from access to the Ubuntu One cloud.

The pre-patch error on accessing Ubuntu One from Fedora is misleading in that it's not the server but the client that needs updating.

Comments

Ubuntu One KDE client no longer in development

Thomi Richards

The Ubuntu One client for KDE has been removed. The download mentioned in this article no longer works. For those interested, I have written a short summary of the state of play as at Janurary 2011. Anyone who reads this article looking for a KDE client (as I did) may be interested in seeing what happened: