Bug 565961 – Crash with recurring all-day event

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 565961 - Crash with recurring all-day event


Summary:	Crash with recurring all-day event


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.28.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:	evolution[timezone]

Duplicates:	575103 586648 594240 604712 (view as bug list)
Depends on:
Blocks:

Reported:	2008-12-29 19:46 UTC by Dwayne Bailey
Modified:	2011-06-15 13:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Attachments
eds patch (3.42 KB, patch) 2011-06-15 13:05 UTC, Milan Crha	committed	Details \| Review

Description Dwayne Bailey 2008-12-29 19:46:08 UTC

What were you doing when the application crashed?
Nothing!  Evolution was simply running while I was using Firefox


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 227864576 vsize: 227864576 resident: 107888640 share: 27357184 rss: 107888640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1230543813 rtime: 40250 utime: 34851 stime: 5399 cutime:510 cstime: 496 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f48980 (LWP 3199)]
[New Thread 0xaf5feb90 (LWP 8268)]
[New Thread 0xb2f5ab90 (LWP 5078)]
[New Thread 0xb5cbeb90 (LWP 5077)]
[New Thread 0xb7c46b90 (LWP 3213)]
0x00110416 in __kernel_vsyscall ()

+ Trace 211146

Thread 1 (Thread 0xb7f48980 (LWP 3199))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 ??
#8 <signal handler called>
#9 pvl_head
at pvl.c line 541
#10 icaltimezone_expand_changes
at icaltimezone.c line 503
#11 icaltimezone_ensure_coverage
at icaltimezone.c line 483
#12 icaltimezone_get_utc_offset_of_utc_time
at icaltimezone.c line 965
#13 icaltimezone_convert_time
at icaltimezone.c line 774
#14 icaltime_from_timet_with_zone
at icaltime.c line 226
#15 add_instance
at e-cal.c line 3353
#16 generate_instances_for_chunk
at e-cal-recur.c line 1382
#17 e_cal_recur_generate_instances_of_rule
at e-cal-recur.c line 880
#18 generate_instances
at e-cal.c line 3621
#19 e_cal_generate_instances_for_object
at e-cal.c line 3773
#20 e_cal_view_objects_added_cb
at e-cal-model.c line 1473
#21 e_cal_view_objects_modified_cb
at e-cal-model.c line 1553
#22 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#23 IA__g_closure_invoke
at gclosure.c line 767
#24 signal_emit_unlocked_R
at gsignal.c line 3244
#25 IA__g_signal_emit_valist
at gsignal.c line 2977
#26 IA__g_signal_emit
at gsignal.c line 3034
#27 objects_modified_cb
at e-cal-view.c line 91
#28 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#29 IA__g_closure_invoke
at gclosure.c line 767
#30 signal_emit_unlocked_R
at gsignal.c line 3244
#31 IA__g_signal_emit_valist
at gsignal.c line 2977
#32 IA__g_signal_emit
at gsignal.c line 3034
#33 impl_notifyObjectsModified
at e-cal-view-listener.c line 157
#34 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalViewListener_notifyObjectsModified
at Evolution-DataServer-Calendar-common.c line 24
#35 ORBit_POAObject_invoke
at poa.c line 1148
#36 ORBit_OAObject_invoke
at orbit-adaptor.c line 340
#37 ORBit_small_invoke_adaptor
at orbit-small.c line 846
#38 ORBit_POAObject_handle_request
at poa.c line 1357
#39 ORBit_POAObject_invoke_incoming_request
at poa.c line 1427
#40 giop_thread_queue_process
at giop.c line 792
#41 giop_mainloop_handle_input
at giop.c line 482
#42 link_source_dispatch
at linc-source.c line 164
#43 g_main_dispatch
at gmain.c line 2144
#44 IA__g_main_context_dispatch
at gmain.c line 2697
#45 g_main_context_iterate
at gmain.c line 2778
#46 IA__g_main_loop_run
at gmain.c line 2986
#47 bonobo_main
at bonobo-main.c line 311
#48 main

The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug/usr/lib/gconv/KOI8-U.so.debug" does not match "/usr/lib/gconv/KOI8-U.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//lib/libnss_dns-2.9.so.debug" does not match "/lib/libnss_dns.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/lib/libnss_dns-2.9.so.debug" does not match "/lib/libnss_dns.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/BIG5.so.debug" does not match "/usr/lib/gconv/BIG5.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/gconv/BIG5.so.debug" does not match "/usr/lib/gconv/BIG5.so" (CRC mismatch).
--------------------------------------------------

Comment 1 André Klapper 2009-03-12 19:28:29 UTC

*** Bug 575103 has been marked as a duplicate of this bug. ***

Comment 2 Fabio Durán Verdugo 2009-06-22 16:25:41 UTC

*** Bug 586648 has been marked as a duplicate of this bug. ***

Comment 3 Akhil Laddha 2009-09-07 03:57:27 UTC

*** Bug 594240 has been marked as a duplicate of this bug. ***

Comment 4 Akhil Laddha 2009-09-07 03:58:15 UTC

last dupe in 2.26.x

Comment 5 Milan Crha 2009-12-01 11:21:16 UTC

Downstream bug report about the same in 2.28.0:
https://bugzilla.redhat.com/show_bug.cgi?id=542884

Comment 6 Fabio Durán Verdugo 2009-12-16 12:35:43 UTC

*** Bug 604712 has been marked as a duplicate of this bug. ***

Comment 7 Milan Crha 2010-03-26 14:50:14 UTC

Thanks for a bug report. The only thing I see is that it received a recurring event, and was trying to expand it to instances, but then it crashed in libical while it was computing a timezone offset for some reason. Does anybody of you has a calendar where it is reproducible, please? it seems to me to be pretty much data dependant. The best if you can reproduce this on an upcoming Evolution 2.30.0+, because there is not planned any update for 2.28. Thanks in advance.

Comment 8 Tobias Mueller 2010-05-20 21:38:22 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 9 Milan Crha 2011-06-15 13:02:11 UTC

I got a reproducer with help of Dan Vratil, it's when there is an all-day event which is recurring.

Comment 10 Milan Crha 2011-06-15 13:05:10 UTC

Created attachment 189981 [details] [review]
eds patch

for evolution;

The libecal passed an uninitialized memory into libical, thus it was pretty likely that the application will crash.

Comment 11 Milan Crha 2011-06-15 13:10:06 UTC

(hrm, I meant "for evolution-data-server", of course)

Created commit a60a6c2 in eds master (3.1.3+)
Created commit 8a0e80e in eds gnome-3-0 (3.0.3+)