Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 433497 ***

Sure ! I knew it wouldn't be of any help without more symbols in the tracing. I was just surprised by the new version of Bug Buddy which is asking much less question that it used to :o)

I already installed evolution-dev, and beagle-dev package on my Sid with all their dependencies. 

I can't reproduce the issue at will but if I manage to reproduce it then I will complete the bug report.

Keep up the good work
Cheers
LeTic

In order to be able to properly debug this issue if it turns up again at a later date, the packages you will need are evolution-dbg and evolution-data-server-dbg.

Yep sorry my mistake :o( Anyway it's done. I'll let you know if I re-encouter the issue...

Hey Tom,

I experience the crash once more. So here is the debug trace with the symbols :o)

Let me knowif I could me of any help
Anthony

Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-1-amd64 #1 SMP Tue Apr 24 21:10:58 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 486805504 vsize: 486805504 resident: 67731456 share: 22134784 rss: 67731456 rss_rlim: 18446744073709551615
CPU usage: start_time: 1179061345 rtime: 847 utime: 771 stime: 76 cutime:5172 cstime: 190 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47075386788880 (LWP 5614)]
[New Thread 1191504192 (LWP 5694)]
[New Thread 1199896896 (LWP 5680)]
[New Thread 1174718784 (LWP 5663)]
[New Thread 1149274432 (LWP 5662)]
[New Thread 1166059840 (LWP 5634)]
[New Thread 1183111488 (LWP 5632)]
[New Thread 1166326080 (LWP 5628)]
[New Thread 1140881728 (LWP 5624)]
[New Thread 1132489024 (LWP 5623)]
[New Thread 1107310912 (LWP 5620)]
[New Thread 1098918208 (LWP 5619)]
[New Thread 1090525504 (LWP 5618)]
[New Thread 1082132800 (LWP 5617)]
0x00002ad090f6ec9f in waitpid () from /lib/libpthread.so.0

+ Trace 133941

----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
report junk?? Re: With video
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4600055 (OpenOffice)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4600055 (OpenOffice)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** Message: drive = 0
** Message: volume = 0
process 5614: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
--------------------------------------------------

If you're willing to recompile Evolution yourself, there's some discussion regarding possible patches for this problem at bug 334966 (this bug is a duplicate of bug 433497, which is in turn a duplicate of 334966), but I think they're getting reasonably close to a fix.