Bug 300148 – EDS crashed while restarting evolution

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 300148 - EDS crashed while restarting evolution


Summary:	EDS crashed while restarting evolution


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:	evolution[groupwise]

Depends on:
Blocks:

Reported:	2005-04-11 06:26 UTC by Poornima
Modified:	2013-09-14 16:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Poornima 2005-04-11 06:26:17 UTC

Steps to reproduce:
1. When 'enter password popup came up' on launchin evolution
2. without typing password, did evolution --force-shutdown
3. Restarted evolution, EDS crashed

Not reproducible always


Stack trace:
(gdb) thread apply all bt

+ Trace 58008

Thread 2 (Thread 1109683120 (LWP 24849))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __lll_mutex_lock_wait
from /lib/tls/libpthread.so.0
#5 _L_mutex_lock_34
from /lib/tls/libpthread.so.0
#6 ??
#7 ??
#8 __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__
from /lib/tls/libc.so.6
#9 __malloc_initialize_hook
from /lib/tls/libc.so.6
#10 ??
#11 ??
#12 gnome_segv_handler
at server.c line 92
#13 gnome_segv_handler
at server.c line 92
#14 <signal handler called>
#15 free
from /lib/tls/libc.so.6
#16 g_free
from /opt/gnome/lib/libglib-2.0.so.0
#17 g_string_free
from /opt/gnome/lib/libglib-2.0.so.0
#18 io_cleanup
at soup-message-io.c line 89
#19 new_iostate
at soup-message-io.c line 692
#20 soup_message_io_client
at soup-message-io.c line 717
#21 soup_message_send_request
at soup-message-client-io.c line 176
#22 send_request
at soup-connection.c line 693
#23 soup_connection_send_request
at soup-connection.c line 712
#24 send_message
at soup-session-sync.c line 164
#25 soup_session_send_message
at soup-session.c line 1197
#26 e_gw_connection_send_message
#27 e_gw_connection_get_quick_messages
at e-gw-connection.c line 2150
#28 get_deltas
at e-cal-backend-groupwise.c line 227
#29 cache_init
at e-cal-backend-groupwise.c line 496
#30 g_thread_create_proxy
from /opt/gnome/lib/libglib-2.0.so.0
#31 start_thread
from /lib/tls/libpthread.so.0
#32 clone
from /lib/tls/libc.so.6




Other information:

Comment 1 Elijah Newren 2005-04-11 14:22:48 UTC

The stack trace in the thread with the signal handler matches the first thread
of your first trace in bug 300155.

Comment 2 Nagappan Alagappan 2005-05-16 10:39:59 UTC

Adding keyword

Comment 3 parthasarathi susarla 2005-07-07 13:12:10 UTC

traces suggest that its a calendar bug. Changing the component to calendar

Comment 4 Chenthill P 2005-08-09 08:18:56 UTC

This is a duplicate. It actually crashes in  libsoup.

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

Comment 5 Dan Winship 2005-10-27 14:54:55 UTC

This is not at all the same as bug 271322.

The fact that it's crashing in free() indicates some sort of memory
corruption, probably in the GW backend given that that's where all of the
duplicates of this bug occur. If this still occurs, try valgrinding.

Comment 6 Chenthill P 2005-12-20 18:30:11 UTC

Please regress this with latest evolution and EDS. I don't see this happening.

Comment 7 André Klapper 2006-04-14 21:20:42 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 8 Lucky Wankhede 2007-08-22 13:13:17 UTC

Looks same to bug320015