GNOME Bugzilla – Bug 490498
crash in Tasks: closing the mail box
Last modified: 2007-10-26 14:49:47 UTC
Version: 2.10 What were you doing when the application crashed? closing the mail box 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: 167686144 vsize: 167686144 resident: 41394176 share: 33501184 rss: 41394176 rss_rlim: 4294967295 CPU usage: start_time: 1193402511 rtime: 160 utime: 141 stime: 19 cutime:51 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 -1208719648 (LWP 31563)] [New Thread -1324344432 (LWP 31586)] [New Thread -1262490736 (LWP 31572)] [New Thread -1272980592 (LWP 31570)] [New Thread -1240097904 (LWP 31566)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173019
Thread 5 (Thread -1240097904 (LWP 31566))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x14041fb CalDAV Eplugin starting up ... ** (evolution:31563): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:31563): 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 490499 has been marked as a duplicate of this bug. ***