GNOME Bugzilla – Bug 607428
crash in Evolution: did nothing - program wa...
Last modified: 2010-02-16 15:18:06 UTC
What were you doing when the application crashed? did nothing - program was idle Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 18:09:19 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Unity Icon Theme: yasis GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 781385728 vsize: 781385728 resident: 29220864 share: 12972032 rss: 29220864 rss_rlim: 18446744073709551615 CPU usage: start_time: 1263810768 rtime: 5508 utime: 4646 stime: 862 cutime:4 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f9792052910 (LWP 32287)] [New Thread 0x7f979ce79910 (LWP 32286)] [New Thread 0x7f97954a9910 (LWP 32252)] [New Thread 0x7f9795caa910 (LWP 32251)] [New Thread 0x7f9796ffd910 (LWP 32250)] [New Thread 0x7f97977fe910 (LWP 32247)] [New Thread 0x7f979d8a3910 (LWP 32244)] [New Thread 0x7f979e0a4910 (LWP 32243)] 0x00007f97b31ca51d in waitpid () from /lib/libpthread.so.0
+ Trace 220145
Thread 1 (Thread 0x7f97b85737f0 (LWP 32234))
A debugging session is active. Inferior 1 [process 32234] 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 (1013638 sec old) --------------------- ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3871): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml2, gtk2 and glib2 (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Even not 100% sure, then I'm pretty sure it's bug #587321. Please install missing debug info packages any way, to get better traces next time. Thanks. *** This bug has been marked as a duplicate of bug 587321 ***