GNOME Bugzilla – Bug 492941
crash in Tasks: I clicked on a message i...
Last modified: 2007-11-03 16:18:11 UTC
Version: 2.10 What were you doing when the application crashed? I clicked on a message in the messages list. 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: aero-clone Icon Theme: LiNsta-0.3 Memory status: size: 118272000 vsize: 118272000 resident: 38912000 share: 29880320 rss: 38912000 rss_rlim: 4294967295 CPU usage: start_time: 1194074219 rtime: 193 utime: 177 stime: 16 cutime:0 cstime: 0 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 -1208387872 (LWP 3228)] [New Thread -1220977776 (LWP 3310)] [New Thread -1242190960 (LWP 3243)] [New Thread -1210487920 (LWP 3241)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174781
Thread 1 (Thread -1208387872 (LWP 3228))
----------- .xsession-errors (38 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) beryl: No GLXFBConfig for default depth, falling back on visinfo. CalDAV Eplugin starting up ... ** (evolution:3228): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3228): 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 ***