GNOME Bugzilla – Bug 518813
crash in Tasks:
Last modified: 2008-02-26 13:13:39 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 134459392 vsize: 134459392 resident: 40550400 share: 33386496 rss: 40550400 rss_rlim: 4294967295 CPU usage: start_time: 1204022483 rtime: 66 utime: 60 stime: 6 cutime:0 cstime: 1 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 -1208330528 (LWP 19147)] [New Thread -1250956400 (LWP 19167)] [New Thread -1228457072 (LWP 19164)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190487
Thread 1 (Thread -1208330528 (LWP 19147))
----------- .xsession-errors --------------------- CalDAV Eplugin starting up ... ** (evolution:15841): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:15841): DEBUG: mailto URL program: evolution (gnome-terminal:3682): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3682): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3682): Vte-WARNING **: No handler for control sequence `device-control-string' defined. CalDAV Eplugin starting up ... ** (evolution:18809): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:18809): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:19147): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:19147): 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 ***