GNOME Bugzilla – Bug 485089
crash in Tasks: I just hit the send/rece...
Last modified: 2007-10-09 18:01:41 UTC
Version: 2.10 What were you doing when the application crashed? I just hit the send/receive button. 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 113238016 vsize: 113238016 resident: 36712448 share: 29585408 rss: 36712448 rss_rlim: 4294967295 CPU usage: start_time: 1191943074 rtime: 97 utime: 89 stime: 8 cutime:0 cstime: 2 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 -1209092384 (LWP 7210)] [New Thread -1280910448 (LWP 7236)] [New Thread -1223718000 (LWP 7228)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169045
Thread 1 (Thread -1209092384 (LWP 7210))
----------- .xsession-errors (16 sec old) --------------------- variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. (nautilus:2565): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the start of an entity name; the & character begins an entit closing Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. Data Dir: /usr/share/gnome-applets/invest-applet CalDAV Eplugin starting up ... ** (evolution:7210): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:7210): DEBUG: mailto URL program: evolution --------------------------------------------------
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 364700 ***