GNOME Bugzilla – Bug 501697
crash in Tasks: Moved message from one f...
Last modified: 2007-12-05 10:41:02 UTC
Version: 2.10 What were you doing when the application crashed? Moved message from one folder to amother. 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 152449024 vsize: 152449024 resident: 48250880 share: 35905536 rss: 48250880 rss_rlim: 4294967295 CPU usage: start_time: 1196848754 rtime: 561 utime: 494 stime: 67 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209084192 (LWP 30456)] [New Thread -1247806576 (LWP 30524)] [New Thread -1235461232 (LWP 30510)] [New Thread -1258296432 (LWP 30483)] 0x00110402 in __kernel_vsyscall ()
+ Trace 180800
Thread 1 (Thread -1209084192 (LWP 30456))
----------- .xsession-errors (32 sec old) --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "scmre" localuser:scmre being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/30207 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:30456): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:30456): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
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 ***