GNOME Bugzilla – Bug 486738
crash in Tasks: just opened application,...
Last modified: 2007-10-22 22:21:31 UTC
Version: 2.10 What were you doing when the application crashed? just opened application, with active Search filter 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.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 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: 128991232 vsize: 128991232 resident: 39948288 share: 32530432 rss: 39948288 rss_rlim: 4294967295 CPU usage: start_time: 1192429452 rtime: 66 utime: 59 stime: 7 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 -1209112864 (LWP 2892)] [New Thread -1238369392 (LWP 2898)] [New Thread -1226429552 (LWP 2895)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170270
Thread 1 (Thread -1209112864 (LWP 2892))
----------- .xsession-errors --------------------- Minor opcode: 6 Resource id: 0x1400140 CalDAV Eplugin starting up ... ** (evolution:2892): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2892): 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: 158 Minor opcode: 6 Resource id: 0x6f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x6f --------------------------------------------------
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 ***