GNOME Bugzilla – Bug 514873
crash in Tasks: selecting icons on the l...
Last modified: 2008-02-07 07:52:39 UTC
What were you doing when the application crashed? selecting icons on the left side of Evolution Preferences Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 142962688 vsize: 142962688 resident: 28745728 share: 17100800 rss: 28745728 rss_rlim: 4294967295 CPU usage: start_time: 1202304303 rtime: 1562 utime: 1415 stime: 147 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 -1208351008 (LWP 2848)] [New Thread -1271932016 (LWP 12972)] [New Thread -1249072240 (LWP 2871)] [New Thread -1250952304 (LWP 2868)] [New Thread -1238176880 (LWP 2867)] (no debugging symbols found) 0x00225402 in __kernel_vsyscall ()
+ Trace 188347
Thread 1 (Thread -1208351008 (LWP 2848))
----------- .xsession-errors --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x1a16c6f (evolution:2848): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed (evolution:2848): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:2848): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x992a248' (evolution:2848): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x992a368' X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x187 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 449996 ***