Tag Info

Hot answers tagged

4

Desktopcouch is part of Ubuntu One. If you want to stop that uncheck it in startup applications. And the problem you have is a bug so please login/register at launchpad and add yourself to the 'Does this bug affect you?'. That way it'll get more attention! Turning it off will probably also take care of ubuntuone-syncd


3

CouchDB can sync to other servers http://guide.couchdb.org/editions/1/en/replication.html You can use futon ('web' interface) http://guide.couchdb.org/editions/1/en/tour.html#replication Your own futon address: $HOME/.local/share/desktop-couch/couchdb.html or file:///home/{username}/.local/share/desktop-couch/couchdb.html


3

What version of Ubuntu are you using? Only being able to start desktopcouch as root sounds like this bug: 1-line "uri_file =" config fix for CouchDB 1.1.1 compatability I proposed a fix for it, but looks like there was some issue with the unit tests (I don't think related to my fix). Anyway, desktopcouch is now unmaintained and I recommend not building any ...


2

No. As the GNOME Live wiki says, dconf is a low-level configuration system. Its main purpose is to provide a backend to GSettings on platforms that don't already have configuration storage systems. https://live.gnome.org/dconf I believe the name "dconf" comes from its connection to d-bus.


2

Desktop Couch is not really any different than couchdb itself (except for the installation and the environment it runs in). If you have any usage questions, then you are better off asking at couchdb mailing lists: http://couchdb.apache.org/community/lists.html If you have some troubles with desktop couch installation, then it's probably better to fill bug ...


1

The service utility is used to control system wide services, while desktopcouch is a per-user service. There isn't currently a defined command to kill desktopcouch, but killall desktopcouch-service should do the trick. The service should be started automatically next time it is used.


1

There is a known problem with the Ubuntu One service and it's been like that since before the weekend. They're working on it and expect to have it fixed soon. In the meantime, you can follow the progress here: https://wiki.ubuntu.com/UbuntuOne/Status


1

Well, it was really quite simple; just delete the cookies from localhost. (If you have other local webuis running, you might want to manually find the one that points to _utils.) After doing so, the next time you login it will ask for a confirmation and it will remember the username, password and port to connect to.


1

Go to your init.py file and comment out the following: preferences.update(default_preferences) preferences.db_connect() preferences.load() preferences.save() And remove preferences in the following line: from yourProject_lib import set_up_logging, preferences, get_version That should do it.


1

desktopcouch-ubuntuone is no longer needed and is going to be removed in the next version. It is not used for file synchronization, but for database synchronization. It is being replaced by something else in future versions of Ubuntu One. In other words, you don't have to worry about that error message.


1

When you pair two desktopcouch instances, what happens is that the first db stores the information about the second, and syncs from it, and the second stores information about the first and syncs from that. Of course, the sync is two-way, but the point is that both will try to connect to the other. This will work as long as not both of the servers change IP ...


1

Don't install or use desktopcouch. It is no longer maintained or supported. See the EOL announcement for desktopcouch. Also, couchdb will soon be completely disabled on the Ubuntu One servers, as announced recently. It's not stated in that announcement, but notes sync was the last remaining service backed by couchdb on the server. Once it's down, there will ...



Only top voted, non community-wiki answers of a minimum length are eligible