GNOME Bugzilla – Bug 578413
crash in Evolution Mail and Calendar: I was trying to open a m...
Last modified: 2009-04-09 03:53:37 UTC
What were you doing when the application crashed? I was trying to open a mail. Nothing else was running in the computer at this moment. Distribution: Debian squeeze/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.24.2 System: Linux 2.6.29 #1 SMP PREEMPT Tue Mar 24 22:14:40 CET 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 659476480 vsize: 659476480 resident: 42471424 share: 23592960 rss: 42471424 rss_rlim: 18446744073709551615 CPU usage: start_time: 1239217234 rtime: 191 utime: 170 stime: 21 cutime:21 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f7dc11687f0 (LWP 623)] [New Thread 0x7f7da6dd9950 (LWP 634)] 0x00007f7dbc54931f in waitpid () from /lib/libpthread.so.0
+ Trace 214299
Thread 1 (Thread 0x7f7dc11687f0 (LWP 623))
----------- .xsession-errors --------------------- ** (nautilus:32589): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:32589): WARNING **: Can not get _NET_WORKAREA ** (nautilus:32589): WARNING **: Can not determine workarea, guessing at layout /usr/bin/compiz.real (snow) - Info: Loaded Texture snowflake.png ** (evolution:623): DEBUG: mailto URL command: evolution %s ** (evolution:623): 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 (evolution:623): evolution-mail-WARNING **: VFolder of VFolders not supporting. Ignoring loading this vfolder as a subfolder warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 0000000000000120 --------------------------------------------------
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 568332 ***