GNOME Bugzilla – Bug 508063
crash in Tasks: i was trying to view my ...
Last modified: 2008-02-06 07:43:57 UTC
Version: 2.10 What were you doing when the application crashed? i was trying to view my emails Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 181493760 vsize: 181493760 resident: 55148544 share: 44261376 rss: 55148544 rss_rlim: 4294967295 CPU usage: start_time: 1199793528 rtime: 2479 utime: 1978 stime: 501 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 -1208830240 (LWP 4396)] [New Thread -1336947824 (LWP 4410)] [New Thread -1240831088 (LWP 4400)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184525
Thread 1 (Thread -1208830240 (LWP 4396))
----------- .xsession-errors (6 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x2c0006b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c0006b (evolution:4396): e-utils-CRITICAL **: e_sorter_model_to_sorted: assertion `row >= 0' failed (evolution:4396): e-utils-CRITICAL **: e_sorter_sorted_to_model: assertion `row >= 0' failed (evolution:4396): e-table-CRITICAL **: etsm_select_single_row: assertion `path != NULL' failed (evolution:4396): evolution-mail-CRITICAL **: mail_tool_uri_to_folder: assertion `uri != NULL' failed --------------------------------------------------
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 349913 ***