GNOME Bugzilla – Bug 484699
crash in Tasks: i was trying to open the...
Last modified: 2007-11-29 06:22:26 UTC
Version: 2.10 What were you doing when the application crashed? i was trying to open the inbox folder 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.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 165564416 vsize: 165564416 resident: 70340608 share: 49262592 rss: 70340608 rss_rlim: 4294967295 CPU usage: start_time: 1191840497 rtime: 7584 utime: 6801 stime: 783 cutime:4 cstime: 24 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208183072 (LWP 5096)] [New Thread -1256199280 (LWP 5150)] [New Thread -1224332400 (LWP 5148)] [New Thread -1234822256 (LWP 5117)] (no debugging symbols found) 0x00a8e402 in __kernel_vsyscall ()
+ Trace 168750
Thread 1 (Thread -1208183072 (LWP 5096))
----------- .xsession-errors (8 sec old) --------------------- (evolution:5096): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed (evolution:5096): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5096): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed (evolution:5096): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed (evolution:5096): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed (evolution:5096): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 479007 ***