GNOME Bugzilla – Bug 600490
crash in Evolution Mail: Bug was on system stratu...
Last modified: 2010-09-08 08:21:07 UTC
What were you doing when the application crashed? Bug was on system stratup Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: Nuvola GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 77651968 vsize: 77651968 resident: 12783616 share: 10596352 rss: 12783616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257200249 rtime: 18 utime: 14 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution/2.28/evolution-alarm-notify' [Thread debugging using libthread_db enabled] [New Thread 0xb4fc9b70 (LWP 2856)] [New Thread 0xb6024b70 (LWP 2556)] 0xb8060424 in __kernel_vsyscall ()
+ Trace 218764
Thread 1 (Thread 0xb63ab760 (LWP 2521))
A debugging session is active. Inferior 1 [process 2521] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- ** (evolution:2498): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:2498): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed console message: undefined @1: SyntaxError: Parse error ** (epiphany-browser:2529): DEBUG: NP_Initialize ** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded ** (epiphany-browser:2529): DEBUG: NP_Initialize ** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded ** (epiphany-browser:2529): DEBUG: NP_Initialize ** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded ** (epiphany-browser:2529): DEBUG: NP_Initialize ** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded ** (epiphany-browser:2529): DEBUG: NP_Initialize ** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded --------------------------------------------------
looks dupe of bug 596204
Marking this as a duplicate of a newer bug, because it contains a possible fix. *** This bug has been marked as a duplicate of bug 628635 ***