GNOME Bugzilla – Bug 511248
crash in Tasks:
Last modified: 2008-01-22 17:44:59 UTC
Version: 2.10 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 126197760 vsize: 126197760 resident: 42348544 share: 34152448 rss: 42348544 rss_rlim: 4294967295 CPU usage: start_time: 1201008205 rtime: 155 utime: 136 stime: 19 cutime:1 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 -1209043232 (LWP 3377)] [New Thread -1271178352 (LWP 3391)] [New Thread -1229304944 (LWP 3381)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186315
Thread 1 (Thread -1209043232 (LWP 3377))
----------- .xsession-errors (17 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x1e0009a X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x69 QApplication::notify: Unexpected null receiver ** (galeon:3362): CRITICAL **: radio_group_set_from_value: assertion `action != NULL' failed CalDAV Eplugin starting up ... ** (evolution:3377): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3377): 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 --------------------------------------------------
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 ***