GNOME Bugzilla – Bug 531749
crash in Evolution Mail and Calendar: Launching Evolution.
Last modified: 2008-09-23 15:34:15 UTC
What were you doing when the application crashed? Launching Evolution. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 75468800 vsize: 75468800 resident: 22269952 share: 9904128 rss: 22269952 rss_rlim: 4294967295 CPU usage: start_time: 1210083752 rtime: 55 utime: 51 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb65ee960 (LWP 4216)] [New Thread 0xb6355b90 (LWP 4217)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197035
Thread 1 (Thread 0xb65ee960 (LWP 4216))
----------- .xsession-errors (8 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) CalDAV Eplugin starting up ... ** (evolution:4039): DEBUG: mailto URL command: evolution %s ** (evolution:4039): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:4204): DEBUG: mailto URL command: evolution %s ** (evolution:4204): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 532819 has been marked as a duplicate of this bug. ***
*** Bug 532896 has been marked as a duplicate of this bug. ***
The only debug package available for Debian Testing that I didn't have installed already was libgtkhtml-3.8-dbg_3.12.3-3_i386 - I'm installed that now, but I suspect that the missing packages are going to have to be compiled with debugging on, in order to get to the bottom of this. Debug packages at present are: evolution-data-server-dbg 2.22.1-1 evolution-dbg 2.22.1-1 evolution-exchange-dbg 2.22.1.dfsg-1 gnome-panel-dbg 2.20.3-3 libc6-dbg 2.7-10 libglib1.2-dbg 1.2.10-19 libglib2.0-0-dbg 2.16.3-2 libgnomeui-0-dbg 2.20.1.1-1 libgnomevfs2-0-dbg 1:2.22.0-2 libgtk2.0-0-dbg 2.12.9-3 libgtkhtml3.14-dbg 3.18.1-1 libgtkhtml3.8-dbg 3.12.3-3 libldap-2.4-2-dbg 2.4.7-6.2 libpango1.0-0-dbg 1.20.2-2 If you need something else, let me know, and I'll go make a debug package of it. Otherwise, I'm still sitting here in the dark trying to guess what's going wrong...
*** Bug 540248 has been marked as a duplicate of this bug. ***
If you are getting crash often, can you please provide better traces. It would be really helpful, thanks.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 532844 ***