On 20 June 2010 04:39, Raphael Hertzog <hert...@debian.org> wrote: > > gwibber uses desktopcouch to store messages, and desktopcouch starts a > local couchdb instance... the question is why doesn't it work as it > should? > > Here it managed to start the local couchdb but apparently the port number > that has been allocated has never been communicated back to the client > application through dbus. > > In your cases it rather looks like that the server was no longer there > (or do you have firewalling that could forbid it?). >
I think there is a permissions problem in /etc/couchdb/ giving permissions to read and execute directories recursively solved launching the ubuntu version of the package. So I installed gwibber, gwibber-service and gwibber-themes from lucid and changed permissions in /etc/couchdb/ as # chmod -R o+rX /etc/couchdb/ And then I could launch gwibber 2.30.0.1 regards, -- Dionisio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
