Bug 334019 – EDS Crash At Startup

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 334019 - EDS Crash At Startup


Summary:	EDS Crash At Startup


Status:	RESOLVED DUPLICATE of bug 331146

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-03-09 13:42 UTC by David Richards
Modified:	2006-03-20 07:32 UTC

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

Description David Richards 2006-03-09 13:42:39 UTC

Please describe the problem:
Lots of reports from beta testers....unknown if this is a dupe, but really bad
for us.  

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 15470)]
[New Thread -1320158288 (LWP 15535)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 15470)]
[New Thread -1320158288 (LWP 15535)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 15470)]
[New Thread -1320158288 (LWP 15535)]
[New Thread -1310700624 (LWP 15509)]
[New Thread -1224066128 (LWP 15472)]
0xffffe410 in ?? ()

+ Trace 66805

Thread 2 (Thread -1320158288 (LWP 15535))

#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 /opt/gnome/lib/libglib-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 gnome_segv_handler
at server.c line 97
#13 gnome_segv_handler
at server.c line 97
#14 <signal handler called>
#15 g_str_hash
from /opt/gnome/lib/libglib-2.0.so.0
#16 g_hash_table_lookup
from /opt/gnome/lib/libglib-2.0.so.0
#17 check_dup_uid
at e-cal-backend-file.c line 409
#18 add_component
at e-cal-backend-file.c line 478
#19 scan_vcalendar
at e-cal-backend-file.c line 603
#20 open_cal
at e-cal-backend-file.c line 679
#21 e_cal_backend_file_open
at e-cal-backend-file.c line 898
#22 e_cal_backend_sync_open
at e-cal-backend-sync.c line 186
#23 _e_cal_backend_open
at e-cal-backend-sync.c line 662
#24 e_cal_backend_open
at e-cal-backend.c line 616
#25 impl_Cal_open
at e-data-cal.c line 81
#26 _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_open
at Evolution-DataServer-Calendar-common.c line 44
#27 IOP_profile_dump
from /opt/gnome/lib/libORBit-2.so.0
#28 ORBit_OAObject_invoke
from /opt/gnome/lib/libORBit-2.so.0
#29 ORBit_small_invoke_adaptor
from /opt/gnome/lib/libORBit-2.so.0
#30 ORBit_recv_buffer_return_sys_exception
from /opt/gnome/lib/libORBit-2.so.0
#31 ORBit_recv_buffer_return_sys_exception
from /opt/gnome/lib/libORBit-2.so.0
#32 giop_thread_queue_process
from /opt/gnome/lib/libORBit-2.so.0
#33 giop_init
from /opt/gnome/lib/libORBit-2.so.0
#34 g_thread_pool_push
from /opt/gnome/lib/libglib-2.0.so.0
#35 g_thread_create_full
from /opt/gnome/lib/libglib-2.0.so.0
#36 start_thread
from /lib/tls/libpthread.so.0
#37 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:32:08 UTC


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