GNOME Bugzilla – Bug 451080
crash in Calendar: nothing to do
Last modified: 2007-09-29 00:08:04 UTC
Version: 2.10 What were you doing when the application crashed? nothing to do Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 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: 594677760 vsize: 594677760 resident: 44863488 share: 32866304 rss: 44863488 rss_rlim: 18446744073709551615 CPU usage: start_time: 993510583 rtime: 86 utime: 74 stime: 12 cutime:54 cstime: 12 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 46912743836448 (LWP 2839)] [New Thread 1147169104 (LWP 2910)] [New Thread 1105209680 (LWP 2880)] (no debugging symbols found) 0x00002aaaad89d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 143708
Thread 1 (Thread 46912743836448 (LWP 2839))
----------- .xsession-errors --------------------- Creating backend ... Loading x11 FrontEnd module ... SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2615 GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2839): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2839): 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. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 ***