Bug 327747 – ESD Crash while calendar starting to load

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 327747 - ESD Crash while calendar starting to load


Summary:	ESD Crash while calendar starting to load


Status:	RESOLVED DUPLICATE of bug 334065

Product:	evolution-data-server
Classification:	Platform
Component:	Calendar
Version:	1.6.x (obsolete)
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-01-19 19:54 UTC by David Richards
Modified:	2013-09-14 16:49 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description David Richards 2006-01-19 19:54:51 UTC

Please describe the problem:
Evolution started, the monthly view of the calendar displayed and then it was
sitting like it normally does while it brings down webcal, weather, local and GW
calendar information.  After about 2 seconds, EDS crashed

Backtrace was generated from '/opt/gnome/libexec/evolution-data-server-1.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 14540)]
[New Thread -1311786064 (LWP 14613)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 14540)]
[New Thread -1311786064 (LWP 14613)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 14540)]
[New Thread -1311786064 (LWP 14613)]
[New Thread -1278215248 (LWP 14612)]
[New Thread -1303393360 (LWP 14567)]
[New Thread -1224066128 (LWP 14542)]
0xffffe410 in ?? ()

+ Trace 65374

Thread 2 (Thread -1311786064 (LWP 14613))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __lll_mutex_lock_wait
from /lib/tls/libpthread.so.0
#5 _L_mutex_lock_33
from /lib/tls/libpthread.so.0
#6 ??
#7 ??
#8 ??
from /lib/tls/libc.so.6
#9 ??
#10 __libc_ptyname1
from /lib/tls/libc.so.6
#11 ??
#12 gnome_segv_handler
at server.c line 97
#13 gnome_segv_handler
at server.c line 97
#14 <signal handler called>
#15 getenv
from /lib/tls/libc.so.6
#16 tzset_internal
from /lib/tls/libc.so.6
#17 tzset
from /lib/tls/libc.so.6
#18 timelocal
from /lib/tls/libc.so.6
#19 icaltime_as_timet_with_zone
at icaltime.c line 420
#20 e_cal_recur_generate_instances_of_rule
at e-cal-recur.c line 778
#21 e_cal_recur_generate_instances
at e-cal-recur.c line 655
#22 func_occur_in_time_range
at e-cal-backend-sexp.c line 386
#23 e_sexp_term_eval
at e-sexp.c line 710
#24 term_eval_and
at e-sexp.c line 255
#25 e_sexp_term_eval
at e-sexp.c line 700
#26 e_sexp_eval
at e-sexp.c line 1304
#27 e_cal_backend_sexp_match_comp
at e-cal-backend-sexp.c line 1045
#28 e_cal_backend_sexp_match_object
at e-cal-backend-sexp.c line 1081
#29 e_data_cal_view_object_matches
at e-data-cal-view.c line 516
#30 e_cal_backend_notify_object_created
at e-cal-backend.c line 1121
#31 cache_init
at e-cal-backend-groupwise.c line 676
#32 g_thread_create_full
from /opt/gnome/lib/libglib-2.0.so.0
#33 start_thread
from /lib/tls/libpthread.so.0
#34 clone
from /lib/tls/libc.so.6



Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:

Comment 1 Chenthill P 2006-03-20 07:33:36 UTC


*** This bug has been marked as a duplicate of 334065 ***