Bug 579617 – crash in Evolution Mail and Calendar: I was trying to adjust t...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 579617 - crash in Evolution Mail and Calendar: I was trying to adjust t...


Summary:	crash in Evolution Mail and Calendar: I was trying to adjust t...


Status:	RESOLVED DUPLICATE of bug 482360

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-04-20 14:48 UTC by info
Modified:	2009-04-20 15:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description info 2009-04-20 14:48:40 UTC

What were you doing when the application crashed?
I was trying to adjust the recurrence of an entry (I wanted to change the end date), but none of the instances in the calender belonging to the entry had an active recurrence section (pale colour). Going through the instances from the very first entry, when I arrived at the fourth or fifth instance, the bug reporting tool addressed me.


Distribution: Debian 5.0.1
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 116862976 vsize: 116862976 resident: 48054272 share: 21524480 rss: 48054272 rss_rlim: 4294967295
CPU usage: start_time: 1240235045 rtime: 4319 utime: 4062 stime: 257 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb661f6d0 (LWP 3155)]
[New Thread 0xb5cbdb90 (LWP 3268)]
[New Thread 0xb2cbdb90 (LWP 3266)]
[New Thread 0xb3cbfb90 (LWP 3189)]
0xb7f92424 in __kernel_vsyscall ()

+ Trace 214635

Thread 1 (Thread 0xb661f6d0 (LWP 3155))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 segv_redirect
at main.c line 519
#7 <signal handler called>
#8 IA__g_object_ref
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gobject.c line 1718
#9 e_cal_model_copy_component_data
at e-cal-model.c line 2107
#10 calendar_control_sensitize_calendar_commands
at calendar-commands.c line 422
#11 gcal_calendar_focus_change_cb
at calendar-commands.c line 522
#12 IA__g_cclosure_marshal_VOID__BOOLEAN
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gmarshal.c line 111
#13 IA__g_closure_invoke
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gclosure.c line 490
#14 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2440
#15 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2199
#16 IA__gtk_signal_emit
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtksignal.c line 360
#17 calendar_focus_change_cb
at gnome-cal.c line 1082
#18 _gtk_marshal_BOOLEAN__BOXED
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkmarshalers.c line 84
#19 IA__g_closure_invoke
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gclosure.c line 490
#20 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2440
#21 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2209
#22 IA__g_signal_emit
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2243
#23 gtk_widget_event_internal
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkwidget.c line 4695
#24 do_focus_change
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkwindow.c line 5048
#25 _gtk_window_set_is_active
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkwindow.c line 8074
#26 gtk_window_focus_in_event
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkwindow.c line 5070
#27 _gtk_marshal_BOOLEAN__BOXED
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkmarshalers.c line 84
#28 g_type_class_meta_marshal
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gclosure.c line 567
#29 IA__g_closure_invoke
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gclosure.c line 490
#30 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2478
#31 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2209
#32 IA__g_signal_emit
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gsignal.c line 2243
#33 gtk_widget_event_internal
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkwidget.c line 4695
#34 IA__gtk_main_do_event
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkmain.c line 1534
#35 gdk_event_dispatch
at /tmp/buildd/gtk+2.0-2.12.12/gdk/x11/gdkevents-x11.c line 2351
#36 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2012
#37 g_main_context_iterate
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2645
#38 IA__g_main_loop_run
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
#39 bonobo_main
from /usr/lib/libbonobo-2.so.0
#40 main
at main.c line 793
#0 __kernel_vsyscall



----------- .xsession-errors (6 sec old) ---------------------
(evolution:3155): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `start < add_event_data->day_view->upper' failed
(evolution:3155): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `start < add_event_data->day_view->upper' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
(evolution:3155): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `start < add_event_data->week_view->day_starts[num_days]' failed
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-04-20 15:46:59 UTC

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 482360 ***