GNOME Bugzilla – Bug 494011
crash in Calendar: 发送,接收
Last modified: 2007-11-07 21:48:37 UTC
Version: 2.10 What were you doing when the application crashed? 发送,接收 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 143732736 vsize: 143732736 resident: 40374272 share: 32972800 rss: 40374272 rss_rlim: 4294967295 CPU usage: start_time: 1194350669 rtime: 136 utime: 119 stime: 17 cutime:98 cstime: 7 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 -1208240416 (LWP 3071)] [New Thread -1289245808 (LWP 3124)] [New Thread -1228506224 (LWP 3094)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175618
Thread 1 (Thread -1208240416 (LWP 3071))
----------- .xsession-errors (20 sec old) --------------------- Checking for XSync extension : passed Checking Screen 0 ... Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (2048x2048) No framebuffer_object support! (only simple Blur aviable). CalDAV Eplugin starting up ... ** (evolution:3071): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3071): 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 ***