GNOME Bugzilla – Bug 475662
crash in Calendar: send/receive
Last modified: 2007-10-11 17:05:33 UTC
Version: 2.10 What were you doing when the application crashed? send/receive 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 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 603004928 vsize: 603004928 resident: 51695616 share: 36200448 rss: 51695616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189467370 rtime: 104 utime: 92 stime: 12 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912741530048 (LWP 30442)] [New Thread 1094719824 (LWP 30486)] [New Thread 1115699536 (LWP 30484)] [New Thread 1084229968 (LWP 30466)] (no debugging symbols found) 0x00002aaaad8be97f in waitpid () from /lib64/libpthread.so.0
+ Trace 161923
Thread 1 (Thread 46912741530048 (LWP 30442))
----------- .xsession-errors (18 sec old) --------------------- Smart Common Input Method 1.4.5 Error: Bad annotation destination Error: Bad annotation destination Error: Bad annotation destination Error: Bad annotation destination Error: Bad annotation destination Error: Bad annotation destination Error: Bad annotation destination CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:30442): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:30442): 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 364700 ***