GNOME Bugzilla – Bug 488963
crash in Tasks: Clicked the close button...
Last modified: 2007-10-22 23:14:13 UTC
Version: 2.10 What were you doing when the application crashed? Clicked the close button on Evolution. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 156577792 vsize: 156577792 resident: 61456384 share: 35430400 rss: 61456384 rss_rlim: 4294967295 CPU usage: start_time: 1193051954 rtime: 2120 utime: 1660 stime: 460 cutime:166 cstime: 391 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208772896 (LWP 2589)] [New Thread -1257731184 (LWP 3497)] [New Thread -1278710896 (LWP 2613)] [New Thread -1247241328 (LWP 2610)] [New Thread -1236358256 (LWP 2609)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171907
Thread 2 (Thread -1257731184 (LWP 3497))
----------- .xsession-errors (637 sec old) --------------------- (evolution:2589): e-dateedit.c-WARNING **: time_text: 6:30 AM (evolution:2589): e-dateedit.c-WARNING **: time_text:07:30 AM (evolution:2589): e-dateedit.c-WARNING **: time_text:07:30 AM (evolution:2589): e-dateedit.c-WARNING **: time_text: 4:00 PM (evolution:2589): e-dateedit.c-WARNING **: time_text: 6:30 AM (evolution:2589): e-dateedit.c-WARNING **: time_text: 4:00 PM (evolution:2589): e-dateedit.c-WARNING **: time_text: 4:00 PM (evolution:2589): Gtk-CRITICAL **: gtk_window_set_transient_for: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 455329 ***