I have been having the same issue since the initial upgrade to Natty.
After following the recommended steps, Evolution still has an empty
address book, but the error message is a bit different than before.
"DBus.Error.NoReply: Message did not receive a reply (timeout by message
bus)"
...and the terminal window is displaying:
~$ /usr/lib/evolution/e-addressbook-factory
e-data-server-Message: adding type `EBookBackendCouchDBFactory'
e-data-server-Message: adding type `EBookBackendGalFactory'
e-data-server-Message: adding type `EBookBackendExchangeFactory'
e-data-server-Message: adding type `EBookBackendVCFFactory'
e-data-server-Message: adding type `EBookBackendLDAPFactory'
e-data-server-Message: adding type `EBookBackendGroupwiseFactory'
e-data-server-Message: adding type `EBookBackendWebdavFactory'
e-data-server-Message: adding type `EBookBackendGoogleFactory'
e-data-server-Message: adding type `EBookBackendFileFactory'
Migrating cached backend data
Migrating local backend data
rmdir /home/ccerghed/.evolution
FAILED: Directory not empty (contents follows)
tasks
Server is up and running...
** (e-addressbook-factory:13563): WARNING **: Could not get CouchDB
database info: Bad Request
** (e-addressbook-factory:13563): WARNING **: Could not create
'contacts' database: Bad Request
Segmentation fault (core dumped)
On Tue, 2011-04-05 at 22:57 +0000, Felix Lawrence wrote:
> Thanks Rodrigo, those instructions worked for me. I had to do the
> process twice - the first time, I think I got Jono's timeout message,
> and in the terminal I got the usual "Could not get OAuth tokens from
> keyring" message.
>
> Things seem to be working as they should now - however if I look in the
> terminal, e-addressbook-factory is giving me lots of CRITICAL messages:
>
> felix@camelbuntu:~$ /usr/lib/evolution/e-addressbook-factory
> e-data-server-Message: adding type `EBookBackendWebdavFactory'
> e-data-server-Message: adding type `EBookBackendVCFFactory'
> e-data-server-Message: adding type `EBookBackendGroupwiseFactory'
> e-data-server-Message: adding type `EBookBackendCouchDBFactory'
> e-data-server-Message: adding type `EBookBackendGoogleFactory'
> e-data-server-Message: adding type `EBookBackendFileFactory'
> e-data-server-Message: adding type `EBookBackendGalFactory'
> e-data-server-Message: adding type `EBookBackendExchangeFactory'
> e-data-server-Message: adding type `EBookBackendLDAPFactory'
> Server is up and running...
>
> (e-addressbook-factory:18091): Json-CRITICAL **:
> json_object_get_object_member: assertion `node != NULL' failed
>
> (e-addressbook-factory:18091): Json-CRITICAL **:
> json_object_get_object_member: assertion `node != NULL' failed
>
> (e-addressbook-factory:18091): Json-CRITICAL **:
> json_object_get_object_member: assertion `node != NULL' failed
>
> this last message is repeated lots and lots of times. Might be a
> separate issue though, and appears symptomless at the moment.
>
I have been having the same issue since the initial upgrade to Natty. NoReply: Message did not receive a reply (timeout by message evolution/ e-addressbook- factory server- Message: adding type `EBookBackendCo uchDBFactory' server- Message: adding type `EBookBackendGa lFactory' server- Message: adding type `EBookBackendEx changeFactory' server- Message: adding type `EBookBackendVC FFactory' server- Message: adding type `EBookBackendLD APFactory' server- Message: adding type `EBookBackendGr oupwiseFactory' server- Message: adding type `EBookBackendWe bdavFactory' server- Message: adding type `EBookBackendGo ogleFactory' server- Message: adding type `EBookBackendFi leFactory' .evolution
After following the recommended steps, Evolution still has an empty
address book, but the error message is a bit different than before.
"DBus.Error.
bus)"
...and the terminal window is displaying:
~$ /usr/lib/
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
Migrating cached backend data
Migrating local backend data
rmdir /home/ccerghed/
FAILED: Directory not empty (contents follows)
tasks
Server is up and running...
** (e-addressbook- factory: 13563): WARNING **: Could not get CouchDB
database info: Bad Request
** (e-addressbook- factory: 13563): WARNING **: Could not create
'contacts' database: Bad Request
Segmentation fault (core dumped)
On Tue, 2011-04-05 at 22:57 +0000, Felix Lawrence wrote: factory is giving me lots of CRITICAL messages: evolution/ e-addressbook- factory server- Message: adding type `EBookBackendWe bdavFactory' server- Message: adding type `EBookBackendVC FFactory' server- Message: adding type `EBookBackendGr oupwiseFactory' server- Message: adding type `EBookBackendCo uchDBFactory' server- Message: adding type `EBookBackendGo ogleFactory' server- Message: adding type `EBookBackendFi leFactory' server- Message: adding type `EBookBackendGa lFactory' server- Message: adding type `EBookBackendEx changeFactory' server- Message: adding type `EBookBackendLD APFactory' factory: 18091): Json-CRITICAL **: get_object_ member: assertion `node != NULL' failed factory: 18091): Json-CRITICAL **: get_object_ member: assertion `node != NULL' failed factory: 18091): Json-CRITICAL **: get_object_ member: assertion `node != NULL' failed
> Thanks Rodrigo, those instructions worked for me. I had to do the
> process twice - the first time, I think I got Jono's timeout message,
> and in the terminal I got the usual "Could not get OAuth tokens from
> keyring" message.
>
> Things seem to be working as they should now - however if I look in the
> terminal, e-addressbook-
>
> felix@camelbuntu:~$ /usr/lib/
> e-data-
> e-data-
> e-data-
> e-data-
> e-data-
> e-data-
> e-data-
> e-data-
> e-data-
> Server is up and running...
>
> (e-addressbook-
> json_object_
>
> (e-addressbook-
> json_object_
>
> (e-addressbook-
> json_object_
>
> this last message is repeated lots and lots of times. Might be a
> separate issue though, and appears symptomless at the moment.
>