GNOME Bugzilla – Bug 489054
crash in Tasks:
Last modified: 2007-10-23 11:58:55 UTC
Version: 2.10 What were you doing when the application crashed? 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.21.1.emp9 #1 SMP PREEMPT Tue Jul 31 10:01:40 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 173363200 vsize: 173363200 resident: 71618560 share: 56094720 rss: 71618560 rss_rlim: 4294967295 CPU usage: start_time: 1193066561 rtime: 1172 utime: 1097 stime: 75 cutime:0 cstime: 0 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 -1208944928 (LWP 10314)] [New Thread -1363289200 (LWP 10509)] [New Thread -1297155184 (LWP 10324)] [New Thread -1239385200 (LWP 10317)] (no debugging symbols found) 0xb7f45410 in __kernel_vsyscall ()
+ Trace 171973
Thread 1 (Thread -1208944928 (LWP 10314))
----------- .xsession-errors (25 sec old) --------------------- fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 (evolution:10314): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub fixme:heap:RtlCompactHeap stub --------------------------------------------------
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 464159 ***