Bug 512756 – crash in Tasks: Clicking the 'Today' ico...

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 512756 - crash in Tasks: Clicking the 'Today' ico...


Summary:	crash in Tasks: Clicking the 'Today' ico...


Status:	RESOLVED DUPLICATE of bug 451144

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-29 10:26 UTC by jdg
Modified:	2008-01-29 22:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jdg 2008-01-29 10:26:19 UTC

Version: 2.10

What were you doing when the application crashed?
Clicking the 'Today' icon


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Bluecurve

Memory status: size: 996835328 vsize: 996835328 resident: 729190400 share: 27090944 rss: 729190400 rss_rlim: 4294967295
CPU usage: start_time: 1197969366 rtime: 58586 utime: 56571 stime: 2015 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 -1208506656 (LWP 8234)]
[New Thread -1278903408 (LWP 8257)]
[New Thread -1268147312 (LWP 8241)]
[New Thread -1257239664 (LWP 8239)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187170

Thread 1 (Thread -1208506656 (LWP 8234))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_object_ref
from /lib/libgobject-2.0.so.0
#6 e_cal_model_copy_component_data
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#7 calendar_control_sensitize_calendar_commands
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#8 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#9 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#24 ??
from /lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /lib/libgobject-2.0.so.0
#26 ??
from /lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#28 g_signal_emit
from /lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#32 ??
from /lib/libgobject-2.0.so.0
#33 g_closure_invoke
from /lib/libgobject-2.0.so.0
#34 ??
from /lib/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#36 g_signal_emit
from /lib/libgobject-2.0.so.0
#37 gtk_widget_grab_focus
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#39 calendar_goto_today
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#40 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#41 ??
from /usr/lib/libbonoboui-2.so.0
#42 g_closure_invoke
from /lib/libgobject-2.0.so.0
#43 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#44 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#45 ??
from /usr/lib/libbonoboui-2.so.0
#46 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#47 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#48 Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#49 ??
from /usr/lib/libbonoboui-2.so.0
#50 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#51 ??
from /lib/libgobject-2.0.so.0
#52 g_closure_invoke
from /lib/libgobject-2.0.so.0
#53 ??
from /lib/libgobject-2.0.so.0
#54 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#55 g_signal_emit
from /lib/libgobject-2.0.so.0
#56 bonobo_ui_engine_emit_verb_on_w
from /usr/lib/libbonoboui-2.so.0
#57 ??
from /usr/lib/libbonoboui-2.so.0
#58 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#59 g_closure_invoke
from /lib/libgobject-2.0.so.0
#60 ??
from /lib/libgobject-2.0.so.0
#61 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#62 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#63 ??
from /usr/lib/libgtk-x11-2.0.so.0
#64 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#65 g_closure_invoke
from /lib/libgobject-2.0.so.0
#66 ??
from /lib/libgobject-2.0.so.0
#67 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#68 g_signal_emit
from /lib/libgobject-2.0.so.0
#69 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#70 ??
from /usr/lib/libgtk-x11-2.0.so.0
#71 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#72 ??
from /lib/libgobject-2.0.so.0
#73 g_closure_invoke
from /lib/libgobject-2.0.so.0
#74 ??
from /lib/libgobject-2.0.so.0
#75 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#76 g_signal_emit
from /lib/libgobject-2.0.so.0
#77 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#78 ??
from /usr/lib/libgtk-x11-2.0.so.0
#79 ??
from /usr/lib/libgtk-x11-2.0.so.0
#80 ??
from /lib/libgobject-2.0.so.0
#81 g_closure_invoke
from /lib/libgobject-2.0.so.0
#82 ??
from /lib/libgobject-2.0.so.0
#83 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#84 g_signal_emit
from /lib/libgobject-2.0.so.0
#85 ??
from /usr/lib/libgtk-x11-2.0.so.0
#86 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#87 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#88 ??
from /usr/lib/libgdk-x11-2.0.so.0
#89 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#90 ??
from /lib/libglib-2.0.so.0
#91 g_main_loop_run
from /lib/libglib-2.0.so.0
#92 bonobo_main
from /usr/lib/libbonobo-2.so.0
#93 main
#0 __kernel_vsyscall



----------- .xsession-errors (3606404 sec old) ---------------------
(evolution:8234): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:8234): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:8234): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:8234): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:8234): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:8234): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:8234): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Bruno Boaventura 2008-01-29 22:56:00 UTC

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