GNOME Bugzilla – Bug 604030
crash in Evolution Mail and Calendar: Отмечала прочитанные соо...
Last modified: 2009-12-08 01:10:49 UTC
What were you doing when the application crashed? Отмечала прочитанные сообщения Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (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: Amaranth Icon Theme: Wasp GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 211783680 vsize: 211783680 resident: 33521664 share: 22056960 rss: 33521664 rss_rlim: 18446744073709551615 CPU usage: start_time: 1260224324 rtime: 1194 utime: 1065 stime: 129 cutime:24 cstime: 40 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xac866b70 (LWP 18578)] [New Thread 0xb1203b70 (LWP 18059)] [New Thread 0xb0a1eb70 (LWP 18057)] [New Thread 0xab063b70 (LWP 17916)] [New Thread 0xab864b70 (LWP 17913)] [New Thread 0xae1f1b70 (LWP 17791)] [New Thread 0xaea0fb70 (LWP 17789)] [New Thread 0xaf21bb70 (LWP 17788)] [New Thread 0xafa1cb70 (LWP 17787)] [New Thread 0xb021db70 (LWP 17786)] [New Thread 0xb1a20b70 (LWP 17783)] [New Thread 0xb5256b70 (LWP 17776)] [New Thread 0xb5a57b70 (LWP 17774)] 0xb80e0424 in __kernel_vsyscall ()
+ Trace 219487
Thread 1 (Thread 0xb63b6760 (LWP 17759))
A debugging session is active. Inferior 1 [process 17759] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ----------- .xsession-errors (57 sec old) --------------------- ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:17759): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed --------------------------------------------------
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 bug 557613 ***