On Thu, 2012-05-31 at 03:08 -0400, Andreas Kloeckner wrote: > On Thu, 31 May 2012 08:30:31 +0200, Tino Keitel <tino.kei...@tikei.de> wrote: > > On Wed, May 30, 2012 at 20:10:41 -0400, Andreas Kloeckner wrote: > > > Package: syncevolution > > > Version: 1.2.2-1+b1 > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > with e-d-s 3.4, syncevolution fails to work, saying that there's a > > > problem with the local database. > > > > > > Andreas > > > > Please post the whole error message. If you invoke syncevolution on the > > command line, just copy&paste your command line and the whole output. > > I use sync-ui, which says this on the console: > > ** (sync-ui:5725): WARNING **: only file:// icon uri is supported: > image://themedimage/icons/services/funambol > > (sync-ui:5725): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion > `GTK_IS_WIDGET (widget)' failed > > and this in the UI: > > There is a problem with the local database. Syncing again or rebooting > may help.
Could it be that your EDS databases are currently still empty after a fresh install? For a long time, SyncEvolution has not asked EDS to create database when opening when the database seemed to exist already. It turned out that in a fresh install, system databases seem to exist but still need to be created. 1.3 will do that: * Evolution: always create databases (PTCOM-113) Always try to create address book or calendar database, because even if there is a source there's no guarantee that the actual database was created already; the original logic for only setting this when explicitly requesting a new database therefore failed in some cases. This problem affected users who had never created anything locally and wanted to use SyncEvolution to migrate their data. Now that works without having to create dummy entries first. As a workaround you need to create dummy data via Evolution. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
