GNOME Bugzilla – Bug 562609
crash in Evolution Mail and Calendar:
Last modified: 2009-02-21 19:05:29 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.21.1 #1 PREEMPT Sun May 13 15:54:09 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 111722496 vsize: 111722496 resident: 35221504 share: 23482368 rss: 35221504 rss_rlim: 4294967295 CPU usage: start_time: 1227898324 rtime: 3182 utime: 3000 stime: 182 cutime:11 cstime: 26 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234806080 (LWP 5322)] [New Thread -1309340784 (LWP 5402)] [New Thread -1275524208 (LWP 5352)] 0xb7b07f91 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 210316
Thread 1 (Thread -1234806080 (LWP 5322))
----------- .xsession-errors (32 sec old) --------------------- Could not read Pidgin buddy list file: Could not find a part of the path "/home/eric/.purple/blist.xml". Could not read Pidgin buddy list file: Could not find a part of the path "/home/eric/.purple/blist.xml". Could not read Pidgin buddy list file: Could not find a part of the path "/home/eric/.purple/blist.xml". Could not read Pidgin buddy list file: Could not find a part of the path "/home/eric/.purple/blist.xml". Could not read Pidgin buddy list file: Could not find a part of the path "/home/eric/.purple/blist.xml". (evolution:5322): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed RSS Plugin enabled (evolution 2.22, evolution-rss 0.1.0) new dimensions = (48,48) initial setting of an image. no scaling scale = 1 new dimensions = (48,48) we need to scale up scale = 1 RSS: cleaning all remaining sessions ...done --------------------------------------------------
Thanks for taking the time to report this bug. This trace indicates that Mozilla (which was being used by the program) was responsible for the crash, or alternatively that the program was compiled against a different version of Mozilla. Make sure the program was built against the most recent mozilla, and if you can duplicate the crash in mozilla itself, report the bug to https://bugzilla.mozilla.org/
In fact it's not necessarily a Mozilla issue.
*** This bug has been marked as a duplicate of 550674 ***