GNOME Bugzilla – Bug 480032
crash in Tasks: using Evolution
Last modified: 2007-09-25 01:58:16 UTC
Version: 2.10 What were you doing when the application crashed? using Evolution 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: 120659968 vsize: 120659968 resident: 45727744 share: 37564416 rss: 45727744 rss_rlim: 4294967295 CPU usage: start_time: 1190678364 rtime: 1088 utime: 981 stime: 107 cutime:6 cstime: 16 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 -1208169744 (LWP 2537)] [New Thread -1254106224 (LWP 2623)] [New Thread -1233126512 (LWP 2576)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165222
Thread 1 (Thread -1208169744 (LWP 2537))
----------- .xsession-errors (113 sec old) --------------------- localuser:cadman being added to access control list SESSION_MANAGER=local/oscar.math.ubc.ca:/tmp/.ICE-unix/2307 Initializing nautilus-open-terminal extension 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:2537): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2537): DEBUG: mailto URL program: evolution Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***