GNOME Bugzilla – Bug 485631
crash in Tasks: Opening received mail
Last modified: 2007-10-11 19:17:44 UTC
Version: 2.10 What were you doing when the application crashed? Opening received mail 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 168726528 vsize: 168726528 resident: 42680320 share: 33611776 rss: 42680320 rss_rlim: 4294967295 CPU usage: start_time: 1192086185 rtime: 219 utime: 191 stime: 28 cutime:64 cstime: 15 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 -1209116960 (LWP 12806)] [New Thread -1324422256 (LWP 12834)] [New Thread -1262490736 (LWP 12818)] [New Thread -1272980592 (LWP 12816)] [New Thread -1240421488 (LWP 12812)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169424
Thread 5 (Thread -1240421488 (LWP 12812))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x14002cb CalDAV Eplugin starting up ... ** (evolution:12806): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:12806): 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 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x45 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x45 --------------------------------------------------
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 339602 ***