GNOME Bugzilla – Bug 469669
crash in Tasks: I had prepared a linux "...
Last modified: 2007-09-21 18:52:04 UTC
Version: 2.10 What were you doing when the application crashed? I had prepared a linux "tar" file to send and then prepared another file to warn the recipient that the next file was 475 MB. When I tried to send the warning file, the crash occured. 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 144502784 vsize: 144502784 resident: 61849600 share: 40493056 rss: 61849600 rss_rlim: 4294967295 CPU usage: start_time: 1187881146 rtime: 2415 utime: 1996 stime: 419 cutime:31 cstime: 13 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 -1209071904 (LWP 7029)] [New Thread -1230685296 (LWP 7086)] [New Thread -1261270128 (LWP 7085)] [New Thread -1219785840 (LWP 7063)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157426
Thread 1 (Thread -1209071904 (LWP 7029))
----------- .xsession-errors (411 sec old) --------------------- (evolution:7029): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a3c138' (evolution:7029): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a3c258' (evolution:7029): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) (evolution:7029): camel-WARNING **: No from set for message (evolution:7029): camel-WARNING **: No from set for message (evolution:7029): camel-WARNING **: No from set for message (evolution:7029): camel-WARNING **: Could not find key entry for word 'xxxxxxxxxxxxxxxxx': Success --------------------------------------------------
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 433573 ***