GNOME Bugzilla – Bug 462265
crash in Tasks: selecting HTML email con...
Last modified: 2007-12-04 14:22:08 UTC
Version: 2.10 What were you doing when the application crashed? selecting HTML email content 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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: gnome-icon-theme-2.18.0 Memory status: size: 157736960 vsize: 157736960 resident: 74018816 share: 52518912 rss: 74018816 rss_rlim: 4294967295 CPU usage: start_time: 1185910330 rtime: 872 utime: 777 stime: 95 cutime:36 cstime: 12 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 -1208834336 (LWP 3613)] [New Thread -1224848496 (LWP 3828)] [New Thread -1268786288 (LWP 3688)] [New Thread -1289766000 (LWP 3640)] (no debugging symbols found) 0x0070f402 in __kernel_vsyscall ()
+ Trace 151913
Thread 1 (Thread -1208834336 (LWP 3613))
----------- .xsession-errors (54 sec old) --------------------- (evolution:3613): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xab17130' (evolution:3613): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xab17250' (evolution:3613): gtkhtml-WARNING **: No such file or directory (evolution:3613): gtkhtml-WARNING **: No such file or directory (evolution:3613): gtkhtml-WARNING **: No such file or directory (evolution:3613): gtkhtml-WARNING **: No such file or directory (evolution:3613): gtkhtml-WARNING **: No such file or directory (evolution:3613): gtkhtml-WARNING **: No such file or directory --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 440388 ***