If I want to create a new Address Database in OpenOffice-bin-3.1.1 using the "Adressdatenquelle-Assistent" there is no way to connect to the Evolution addressbook. I just compilied app-office/openoffice-3.1.1 there you can choose the Evolution Adressbook. But you get in trouble with templates. (http://bugs.gentoo.org/show_bug.cgi?id=283687). So I changed back to app-office/openoffice-bin-3.1.1. Now I can see the datbase by pressing F4 in OpenOffice writer. If I click on tables (Tabellen) I get an error message: "Die Verbindung zur Datenquelle "Adressen" konnte nicht hergestellt werden. Die Verbindung zur externen Datenquelle konnte nicht hergestellt werden. Es wurde kein SDBC-Treiber für die angegebene URL gefunden." At the botton "Zusätze" I can see 3 more Error messages: "Die Verbindung zur Datenquelle "Adressen" konnte nicht hergestellt werden." "SQL-Status: HY000 Die Verbindung zur externen Datenquelle konnte nicht hergestellt werden. Es wurde kein SDBC-Treiber für die angegebene URL gefunden." "A connection for the following URL was requested: sdbc:address:evolution:local" Reproducible: Always Steps to Reproduce: see above Evolution-Data-Server is working. There is a library for evolution: /usr/lib/openoffice/basis3.1/program
I can confirm this one; I've just spent an afternoon re-installing openoffice-bin and trying to get the evolution connection to work again. Does anyone know what the openoffice-bin build flags are, vs. the full package? Will
(In reply to comment #1) > Does anyone know what the openoffice-bin build flags > are, vs. the full package? eix openoffice * app-office/openoffice Available versions: 3.1.1 {aqua bash-completion binfilter cups dbus debug eds elibc_FreeBSD gnome gstreamer gtk java kde kdeenablefinal ldap linguas_af linguas_ar linguas_as_IN ...... [I] app-office/openoffice-bin Available versions: 3.1.1!s ~3.2.0!s {gnome java kde linguas_af linguas_ar linguas_as linguas_as_IN .....
This aint easy to fix. Duping this against the rework as with rpms there is nothing we can do to fix it. *** This bug has been marked as a duplicate of bug 361695 ***
