GNOME Bugzilla – Bug 491330
crash in Tasks: Opening received mail
Last modified: 2007-10-30 11:25:55 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: 168128512 vsize: 168128512 resident: 41791488 share: 33501184 rss: 41791488 rss_rlim: 4294967295 CPU usage: start_time: 1193655141 rtime: 159 utime: 141 stime: 18 cutime:50 cstime: 14 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 -1209129248 (LWP 5320)] [New Thread -1324917872 (LWP 5343)] [New Thread -1263539312 (LWP 5329)] [New Thread -1251132528 (LWP 5327)] [New Thread -1240507504 (LWP 5323)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173630
Thread 5 (Thread -1240507504 (LWP 5323))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x1400111 CalDAV Eplugin starting up ... ** (evolution:5320): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5320): 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 ***
*** Bug 491660 has been marked as a duplicate of this bug. ***