GNOME Bugzilla – Bug 603535
Calendar print or print preview crush evolution
Last modified: 2009-12-02 04:01:24 UTC
Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb7d19b70 (LWP 7270)] [Thread 0xb7d19b70 (LWP 7270) exited] [New Thread 0xb7d19b70 (LWP 7271)] [New Thread 0xb7518b70 (LWP 7272)] [New Thread 0xb6d12b70 (LWP 7273)] [New Thread 0xb6511b70 (LWP 7274)] [New Thread 0xb5d10b70 (LWP 7275)] [New Thread 0xb550fb70 (LWP 7276)] [New Thread 0xb450db70 (LWP 7278)] [New Thread 0xb4d0eb70 (LWP 7277)] [New Thread 0xb3d0cb70 (LWP 7279)] [New Thread 0xb2d0ab70 (LWP 7281)] [Thread 0xb2d0ab70 (LWP 7281) exited] [New Thread 0xb350bb70 (LWP 7280)] [Thread 0xb350bb70 (LWP 7280) exited] ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Thread 0xb4d0eb70 (LWP 7277) exited] [New Thread 0xb4d0eb70 (LWP 7282)] [New Thread 0xb350bb70 (LWP 7283)] [New Thread 0xb2d0ab70 (LWP 7284)] [New Thread 0xb1762b70 (LWP 7285)]
+ Trace 219410
Thread 1 (Thread 0xb7fc8b00 (LWP 7258))
** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Thread 0xb2d0ab70 (LWP 7284) exited] [Thread 0xb1762b70 (LWP 7285) exited] [New Thread 0xb1762b70 (LWP 7295)] [New Thread 0xb2d0ab70 (LWP 7296)] ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [New Thread 0xb0e75b70 (LWP 7297)] [New Thread 0xb0674b70 (LWP 7298)] ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Thread 0xb2d0ab70 (LWP 7296) exited] [Thread 0xb1762b70 (LWP 7295) exited] [New Thread 0xb1762b70 (LWP 7301)] ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Thread 0xb0e75b70 (LWP 7297) exited] [Thread 0xb0674b70 (LWP 7298) exited] [Thread 0xb1762b70 (LWP 7301) exited] [New Thread 0xb1762b70 (LWP 7303)] [Thread 0xb1762b70 (LWP 7303) exited] [New Thread 0xb1762b70 (LWP 7304)] [Thread 0xb1762b70 (LWP 7304) exited] [New Thread 0xb1762b70 (LWP 7305)] [New Thread 0xb0674b70 (LWP 7306)] ** (evolution:7258): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Thread 0xb5d10b70 (LWP 7275) exited] [Thread 0xb550fb70 (LWP 7276) exited] [Thread 0xb1762b70 (LWP 7305) exited] [Thread 0xb0674b70 (LWP 7306) exited] [Thread 0xb6511b70 (LWP 7274) exited]
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 600133 ***