GNOME Bugzilla – Bug 482744
crash in Tasks:
Last modified: 2007-10-05 10:00:44 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.22.9-91.fc7PAE #1 SMP Thu Sep 27 22:29:07 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: 143802368 vsize: 143802368 resident: 45514752 share: 36737024 rss: 45514752 rss_rlim: 4294967295 CPU usage: start_time: 1191359851 rtime: 117 utime: 110 stime: 7 cutime:1 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 -1208736032 (LWP 4796)] [New Thread -1255150704 (LWP 4820)] [New Thread -1232684144 (LWP 4817)] (no debugging symbols found) 0x00110410 in __kernel_vsyscall ()
+ Trace 167242
Thread 1 (Thread -1208736032 (LWP 4796))
----------- .xsession-errors (6 sec old) --------------------- closing Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Initializing nautilus-flac-converter extension seahorse nautilus module initialized CalDAV Eplugin starting up ... ** (evolution:4176): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4176): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:4447): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4447): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:4796): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4796): 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 ***