GNOME Bugzilla – Bug 581646
crash in Evolution Mail and Calendar: Clicked on 'EDIT' toolba...
Last modified: 2009-05-07 04:23:26 UTC
What were you doing when the application crashed? Clicked on 'EDIT' toolbar as Evolution was opening. Distribution: Debian 5.0.1 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-2-amd64 #1 SMP Fri Mar 27 04:02:59 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 675667968 vsize: 675667968 resident: 53866496 share: 27090944 rss: 53866496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1241640051 rtime: 84 utime: 76 stime: 8 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fc1fddf9700 (LWP 5763)] [New Thread 0x43df6950 (LWP 5828)] [New Thread 0x42df4950 (LWP 5827)] [New Thread 0x425f3950 (LWP 5796)] [New Thread 0x40d72950 (LWP 5788)] 0x00007fc1f96d75ef in waitpid () from /lib/libpthread.so.0
+ Trace 215189
Thread 1 (Thread 0x7fc1fddf9700 (LWP 5763))
----------- .xsession-errors (10 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) component_id:OAFIID:GNOME_Evolution_RSS:2.22 (evolution:5457): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (evolution:5457): GLib-GObject-WARNING **: invalid (NULL) pointer instance (evolution:5457): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed RSS: cleaning all remaining sessions ...done CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:5763): DEBUG: mailto URL command: evolution %s ** (evolution:5763): DEBUG: mailto URL program: evolution --------------------------------------------------
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 523463 ***