GNOME Bugzilla – Bug 595623
crash in Evolution Mail and Calendar: nothing
Last modified: 2009-09-19 04:05:02 UTC
What were you doing when the application crashed? nothing Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.29-fermat #1 SMP PREEMPT Sat Jun 13 00:45:42 CEST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 943714304 vsize: 943714304 resident: 287326208 share: 12607488 rss: 287326208 rss_rlim: 18446744073709551615 CPU usage: start_time: 1253302420 rtime: 31360 utime: 25277 stime: 6083 cutime:4 cstime: 31 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7ff96bb3e950 (LWP 13915)] [New Thread 0x7ff960ff0950 (LWP 13914)] [New Thread 0x7ff95a7fe950 (LWP 13913)] [New Thread 0x7ff969975950 (LWP 13912)] [New Thread 0x7ff961ffb950 (LWP 13002)] [New Thread 0x7ff96c33f950 (LWP 12923)] [New Thread 0x7ff96cb40950 (LWP 12922)] [New Thread 0x7ff96d5ac950 (LWP 12918)] [New Thread 0x7ff96ddad950 (LWP 12916)] 0x00007ff97d32c28f in __libc_waitpid (pid=14005, stat_loc=0x7fff903badb0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 217677
Thread 5 (Thread 0x7ff969975950 (LWP 13912))
Current language: auto; currently c The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (1120 sec old) --------------------- 41 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetMIMEDescription GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetMIMEDescription return GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue: returning plugin name. GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue return GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue: returning plugin description. GCJ PLUGIN: thread 0x7f3f21c30780: NP_GetValue return [09-18 19:17:03] Torbutton NOTE: Conflict between noncrashed and normal_exit states.. Assuming crash but no session restore.. [09-18 19:17:03] Torbutton NOTE: Crash detected, attempting recovery [09-18 19:17:03] Torbutton NOTE: Restoring cookie status [09-18 19:17:03] Torbutton NOTE: Loading non-tor jar after crash [09-18 19:17:04] Torbutton NOTE: Restoring tor state [SmartNamer] updateEntry() --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of bug 588588 ***