On Fri, 2010-09-10 at 19:47 +0100, Patrick Ohly wrote: > On Fri, 2010-09-10 at 17:40 +0100, Nudelzebra wrote: > > Hi. > > > > I just tried the builds (deb) and unfortunately got the same error > > (10510) as before. > > Please run "dbus-monitor >/tmp/dbus.log &" and "dbus-monitor --profile > >/tmp/profile.log" before starting syncevolution, then send me the > files. I'd like to check what the timeouts are.
Thanks for the logs. They show that the EDS calendar server dies (combination of monitor and profile log): mc 1284371457 118043 73 :1.129 /org/gnome/evolution/dataserver/calendar/1671/8 org.gnome.evolution.dataserver.calendar.Cal getObjectList method call sender=:1.129 -> dest=:1.38 serial=73 path=/org/gnome/evolution/dataserver/calendar/1671/8; interface=org.gnome.evolution.dataserver.calendar.Cal; member=getObjectList string "#t" sig 1284371457 136208 5 /org/freedesktop/DBus org.freedesktop.DBus NameOwnerChanged signal sender=org.freedesktop.DBus -> dest=(null destination) serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string "org.gnome.evolution.dataserver.Calendar" string ":1.38" string "" sig 1284371457 144230 16 /org/freedesktop/DBus org.freedesktop.DBus NameOwnerChanged signal sender=org.freedesktop.DBus -> dest=(null destination) serial=16 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.38" string ":1.38" string "" What this probably means is that 136208 - 118043 = 18ms after receiving the getObjectList() method call, the e-calendar-factory process disconnects from D-Bus. It probably crashed. That libecal turns this error into a "Message did not receive a reply (timeout by message bus)" error has been extremely helpful :-( Not! Can you verify this by stopping Evolution completely (exit GUI, evolution --force-shutdown), then running e-calendar-factory under gdb (usually installed in /usr/libexec, check with ps while Evolution runs)? While it runs, start a sync with SyncEvolution. No need for D-Buslogs, but when the gdb prompt returns, please capture the output of "thread apply all bt". Doing the same with "valgrind" instead of gdb would also be useful. Which version of Evolution do you use? -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
