GNOME Bugzilla – Bug 516919
crash in Tasks: just opened the app
Last modified: 2008-02-17 02:57:15 UTC
Version: 2.10 What were you doing when the application crashed? just opened the app 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 125288448 vsize: 125288448 resident: 34889728 share: 28487680 rss: 34889728 rss_rlim: 4294967295 CPU usage: start_time: 1203202743 rtime: 72 utime: 58 stime: 14 cutime:1 cstime: 3 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 -1208572192 (LWP 6548)] [New Thread -1240278128 (LWP 6599)] [New Thread -1229784176 (LWP 6577)] [New Thread -1219294320 (LWP 6574)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189438
Thread 1 (Thread -1208572192 (LWP 6548))
----------- .xsession-errors (6 sec old) --------------------- Java 3D WARNING : reported GLX version = 1.2 GLX version 1.3 or higher is required The reported version number may be incorrect. There is a known ATI driver bug in glXQueryVersion that incorrectly reports the GLX version as 1.2 when it really is 1.3, so Java 3D will attempt to run anyway. Unknown unit dbZ Unknown unit dbZ Unknown unit dbZ Unknown unit dbZ CalDAV Eplugin starting up ... ** (evolution:6548): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6548): 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 ***
*** This bug has been marked as a duplicate of 431459 ***