Bug 338780 – Crash During Initial 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 338780 - Crash During Initial Startup


Summary:	Crash During Initial Startup


Status:	RESOLVED DUPLICATE of bug 338815

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-04-17 12:51 UTC by David Richards
Modified:	2006-05-02 16:37 UTC

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

Description David Richards 2006-04-17 12:51:53 UTC

Steps to reproduce:
I was not interacting with Evo when this happened.   I opened it up and was
doing something else and it crashed.  I think it was probably downloading
calendar information which sometimes takes a few seconds to complete.

Stack trace:
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 30745)]
[New Thread -1251918928 (LWP 881)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 30745)]
[New Thread -1251918928 (LWP 881)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 30745)]
[New Thread -1251918928 (LWP 881)]
[New Thread -1242563664 (LWP 880)]
[New Thread -1260311632 (LWP 30833)]
[New Thread -1224057936 (LWP 30748)]
0xffffe410 in ?? ()

+ Trace 67661

Thread 3 (Thread -1242563664 (LWP 880))

#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/libgobject-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 ??
#16 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /opt/gnome/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#20 soup_message_finished
at soup-message.c line 558
#21 soup_message_io_finished
at soup-message-io.c line 153
#22 io_read
at soup-message-io.c line 697
#23 io_write
at soup-message-io.c line 532
#24 soup_message_io_client
at soup-message-io.c line 780
#25 soup_message_send_request_internal
at soup-message-client-io.c line 185
#26 send_request
at soup-connection.c line 769
#27 soup_connection_send_request
at soup-connection.c line 788
#28 send_message
at soup-session-sync.c line 177
#29 soup_session_send_message
at soup-session.c line 1320
#30 e_gw_connection_send_message
at e-gw-connection.c line 561
#31 e_gw_connection_read_cursor
at e-gw-connection.c line 2304
#32 populate_cache
at e-cal-backend-groupwise.c line 167
#33 cache_init
at e-cal-backend-groupwise.c line 649
#34 g_thread_create_full
from /opt/gnome/lib/libglib-2.0.so.0
#35 start_thread
from /lib/tls/libpthread.so.0
#36 clone
from /lib/tls/libc.so.6



Other information:

Comment 1 Chenthill P 2006-05-02 16:37:05 UTC


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