GNOME Bugzilla – Bug 503220
crash in Tasks: j'étais en train de déma...
Last modified: 2007-12-12 20:54:41 UTC
Version: 2.10 What were you doing when the application crashed? j'étais en train de démarrer l'application 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: 146087936 vsize: 146087936 resident: 75837440 share: 29028352 rss: 75837440 rss_rlim: 4294967295 CPU usage: start_time: 1197449041 rtime: 244 utime: 211 stime: 33 cutime:1 cstime: 5 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 -1209116960 (LWP 3299)] [New Thread -1232737392 (LWP 3401)] [New Thread -1253717104 (LWP 3400)] [New Thread -1243227248 (LWP 3366)] [New Thread -1222247536 (LWP 3363)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181638
Thread 1 (Thread -1209116960 (LWP 3299))
----------- .xsession-errors (15 sec old) --------------------- localuser:amartinie being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3069 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3299): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3299): 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 ***