GNOME Bugzilla – Bug 463808
crash in Tasks: opening evolution
Last modified: 2007-10-11 17:02:52 UTC
Version: 2.10 What were you doing when the application crashed? opening evolution 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.1-33.fc7 #1 SMP Mon Jul 23 16:59:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 563023872 vsize: 563023872 resident: 40267776 share: 31977472 rss: 40267776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1186355548 rtime: 43 utime: 38 stime: 5 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496488592 (LWP 4044)] [New Thread 1105209680 (LWP 4067)] [New Thread 1084229968 (LWP 4064)] (no debugging symbols found) 0x00000038f9e0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 153056
Thread 1 (Thread 46912496488592 (LWP 4044))
----------- .xsession-errors --------------------- alarm-queue.c:522 (load_alarms) alarm-queuCalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4044): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4044): 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: 0x64 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
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 ***