Bug 475650 – crash in Tasks: double clicking to open ...

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 475650 - crash in Tasks: double clicking to open ...


Summary:	crash in Tasks: double clicking to open ...


Status:	RESOLVED DUPLICATE of bug 468193

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:	2007-09-10 22:52 UTC by erony1
Modified:	2007-12-04 18:05 UTC

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

Description erony1 2007-09-10 22:52:13 UTC

Version: 2.10

What were you doing when the application crashed?
double clicking to open a calendar entry	


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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 568909824 vsize: 568909824 resident: 62128128 share: 29503488 rss: 62128128 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189432972 rtime: 2610 utime: 2426 stime: 184 cutime:4 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496361616 (LWP 24609)]
[New Thread 1115965776 (LWP 24803)]
[New Thread 1084496208 (LWP 24630)]
[New Thread 1084229968 (LWP 24629)]
(no debugging symbols found)
0x00000031a480d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 161915

Thread 1 (Thread 46912496361616 (LWP 24609))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_object_ref
from /lib64/libgobject-2.0.so.0
#4 e_cal_model_copy_component_data
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#5 calendar_control_sensitize_calendar_commands
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#6 ??
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 ??
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 gtk_signal_emit
from /usr/lib64/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 ??
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#23 ??
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit
from /lib64/libgobject-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#30 ??
from /lib64/libglib-2.0.so.0
#31 g_main_loop_run
from /lib64/libglib-2.0.so.0
#32 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#33 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (17 sec old) ---------------------
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:24609): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
--------------------------------------------------

Comment 1 palfrey 2007-12-04 18:05:01 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 468193 ***