GNOME Bugzilla – Bug 453228
crash in Tasks: Creating new contact
Last modified: 2007-07-02 22:32:55 UTC
Version: 2.10 What were you doing when the application crashed? Creating new contact Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 124825600 vsize: 124825600 resident: 46243840 share: 32407552 rss: 46243840 rss_rlim: 4294967295 CPU usage: start_time: 1183411635 rtime: 2234 utime: 2023 stime: 211 cutime:8 cstime: 21 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 -1208449312 (LWP 3368)] [New Thread -1229472880 (LWP 3500)] [New Thread -1218983024 (LWP 3499)] [New Thread -1239962736 (LWP 3408)] (no debugging symbols found) 0x0089c402 in __kernel_vsyscall ()
+ Trace 145346
Thread 1 (Thread -1208449312 (LWP 3368))
----------- .xsession-errors (80 sec old) --------------------- (evolution:3368): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d46140' (evolution:3368): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:3368): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:3368): e-dateedit.c-WARNING **: time_text: 6:00 PM (evolution:3368): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:3368): e-dateedit.c-WARNING **: time_text: 6:00 PM (evolution:3368): e-dateedit.c-WARNING **: time_text: 6:00 PM (evolution:3368): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426227 ***