GNOME Bugzilla – Bug 564040
crash in Evolution Mail and Calendar:
Last modified: 2008-12-11 21:05:50 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26 #1 Tue Nov 25 15:51:22 CET 2008 ppc X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 121090048 vsize: 121090048 resident: 43995136 share: 26148864 rss: 43995136 rss_rlim: 4294967295 CPU usage: start_time: 1228943800 rtime: 1588 utime: 1514 stime: 74 cutime:5 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x48053170 (LWP 8181)] [New Thread 0x4a4f94b0 (LWP 8266)] [New Thread 0x4af374b0 (LWP 8255)] [New Thread 0x48a6c4b0 (LWP 8246)] (no debugging symbols found) 0x0f60b290 in waitpid () from /lib/libpthread.so.0
+ Trace 210679
Thread 1 (Thread 0x48053170 (LWP 8181))
----------- .xsession-errors (47912 sec old) --------------------- RcInitFile: parsing /etc/gnashpluginrc RcInitFile: couldn't open file: /home/manuel/.gnashpluginrc Forked successfully, child process PID is 5438 Main loop ended, cleaning up Any segfault past this message is likely due to improper threads cleanup. Player request channel hang up Shutting down Child process exited with status 0 plugin instance destruction shutting down input chan 0x1be751b8 NS_PluginInitialize call --------------------------------------------------- xEmbed supported in this browser GTK2 supported in this browser NOTE: NPAPI plugin set GNASHRC to /etc/gnashpluginrc:/home/manuel/.gnashpluginrc:/etc/gnashpluginrc:/home/manuel/.gnashpluginrc:/etc/gnashpluginrc:/home/manuel/.gnashpluginrc:/etc/gnashpluginrc:/home/ ...Too much output, ignoring rest... --------------------------------------------------
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 335618 ***