GNOME Bugzilla – Bug 632198
crash in Evolution:
Last modified: 2010-10-19 06:32:55 UTC
What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.35.2 #1 SMP Tue Aug 17 15:59:47 CEST 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 1259364352 vsize: 1259364352 resident: 341413888 share: 11223040 rss: 341413888 rss_rlim: 18446744073709551615 CPU usage: start_time: 1286356693 rtime: 239807 utime: 197758 stime: 42049 cutime:40 cstime: 72 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f46d6dfa710 (LWP 11502)] [New Thread 0x7f46d5df8710 (LWP 11501)] [New Thread 0x7f46d55f7710 (LWP 11497)] [New Thread 0x7f46e0db4710 (LWP 13635)] [New Thread 0x7f46d77fe710 (LWP 13634)] [New Thread 0x7f46ef4d1710 (LWP 5589)] [New Thread 0x7f46e2dd5710 (LWP 5355)] [New Thread 0x7f46f4e71710 (LWP 5354)] [New Thread 0x7f46f5672710 (LWP 5270)] [New Thread 0x7f46f5e73710 (LWP 5269)] [New Thread 0x7f46f689d710 (LWP 5261)] [New Thread 0x7f46f7539710 (LWP 5253)] 0x00007f470462db4d in __libc_waitpid (pid=11503, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 224158
Thread 3 (Thread 0x7f46d5df8710 (LWP 11501))
Inferior 1 [process 5146] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** calendar-gui **: ecmt_value_at: assertion `row >= 0 && row < e_table_model_row_count (etm)' failed ** GdkPixbuf **: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed ** GdkPixbuf **: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed ----------- .xsession-errors (762775 sec old) --------------------- FTS: -> watchWindow for: http://localhost:9000/dossiers/chargelogosvg?dosid=133&size=16px, context: 28562 FTS: context: 28562, window in context: http://localhost:9000/application/index FTS: context: 28562, window in context: http://localhost:9000/dossiers/chargelogosvg?dosid=189&size=16px FTS: context: 28562, window in context: http://localhost:9000/dossiers/chargelogosvg?dosid=200&size=16px FTS: context: 28562, window in context: http://localhost:9000/dossiers/chargelogosvg?dosid=167&size=16px FTS: context: 28562, window in context: http://localhost:9000/dossiers/chargelogosvg?dosid=180&size=16px ...Too much output, ignoring rest... --------------------------------------------------
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 bug 574940 ***