GNOME Bugzilla – Bug 480336
crash in Tasks:
Last modified: 2007-09-26 17:40:42 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 132939776 vsize: 132939776 resident: 39931904 share: 33247232 rss: 39931904 rss_rlim: 4294967295 CPU usage: start_time: 1190746630 rtime: 84 utime: 77 stime: 7 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 -1208707360 (LWP 2982)] [New Thread -1238942832 (LWP 3024)] [New Thread -1227932784 (LWP 3004)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165438
Thread 1 (Thread -1208707360 (LWP 2982))
----------- .xsession-errors --------------------- localuser:gouret1 being added to access control list SESSION_MANAGER=local/pc2004:/tmp/.ICE-unix/2708 seahorse nautilus module initialized error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again ** Message: <info> Vous êtes connecté au réseau sans fil « FON_linksys ». ** Message: <info> Vous êtes connecté au réseau sans fil « Wanadoo_d0e9 ». CalDAV Eplugin starting up ... ** (evolution:2982): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2982): 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 431459 ***