http://bugs.meego.com/show_bug.cgi?id=4026
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING FOR UPSTREAM |NEEDINFO --- Comment #8 from pohly <[email protected]> 2010-09-14 07:42:20 PDT --- Some more information based on information provided by nuzeb: From: Patrick Ohly <[email protected]> Reply-to: [email protected] To: Nudelzebra <[email protected]> Cc: SyncEvolution <[email protected]> Subject: sync fails with error "(timeout by message bus)" (MBC #4026 was Re: [SyncEvolution] SyncEvolution 1.1 pre-release) Date: Mon, 13 Sep 2010 14:19:41 +0200 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)? -------------------------------------------------------------------------- It turned out that e-calendar-factory did not crash; it simply leaves main() with a return code of 1: [New Thread 0xb612db70 (LWP 2068)] Server is up and running... [Thread 0xb612db70 (LWP 2068) exited] Program exited with code 01. .... With a break point in exit(): (gdb) thread apply all bt Thread 2 (Thread 0xb612db70 (LWP 2087)): #0 0xb7fe1416 in __kernel_vsyscall () #1 0xb7eebde6 in __poll (fds=0xb7f83ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb7bc025b in g_poll () from /lib/libglib-2.0.so.0 #3 0xb7bb2bfc in ?? () from /lib/libglib-2.0.so.0 #4 0xb7bb3367 in g_main_loop_run () from /lib/libglib-2.0.so.0 #5 0xb7a7ca64 in ?? () from /usr/lib/libgio-2.0.so.0 #6 0xb7bd9eef in ?? () from /lib/libglib-2.0.so.0 #7 0xb7f8dcc9 in start_thread (arg=0xb612db70) at pthread_create.c:304 #8 0xb7efa6ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb7584720 (LWP 2084)): #0 exit (status=0) at exit.c:100 #1 0xb7e40cef in __libc_start_main (main=0x804b030, argc=1, ubp_av=0xbffff434, init=0x804ba80, fini=0x804ba70, rtld_fini=0xb7ff0b80 <_dl_fini>, stack_end=0xbffff42c) at libc-start.c:258 #2 0x08049ff1 in ?? () No idea what this means. I'll ask the EDS developers. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
