Bug 338070 – EDS Crash While Auto-Completing An Email

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 338070 - EDS Crash While Auto-Completing An Email


Summary:	EDS Crash While Auto-Completing An Email


Status:	RESOLVED DUPLICATE of bug 338815

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

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Devashish Sharma
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	339612 343918 351750 (view as bug list)
Depends on:
Blocks:

Reported:	2006-04-11 12:43 UTC by David Richards
Modified:	2006-08-21 17:45 UTC

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

Description David Richards 2006-04-11 12:43:21 UTC

Steps to reproduce:
I was auto-completing an address when eds crashed.  Possible that it was doing
something else in another thread, but my UI interaction at the time was typing
into the To: field.


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 1085556288 (LWP 30941)]
[New Thread 1103109040 (LWP 785)]
[Thread debugging using libthread_db enabled]
[New Thread 1085556288 (LWP 30941)]
[New Thread 1103109040 (LWP 785)]
[Thread debugging using libthread_db enabled]
[New Thread 1085556288 (LWP 30941)]
[New Thread 1103109040 (LWP 785)]
[New Thread 1101007792 (LWP 30983)]
[New Thread 1091963824 (LWP 30942)]
0xffffe410 in ?? ()

+ Trace 67565

Thread 2 (Thread 1103109040 (LWP 785))

#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/libsoup-2.2.so.8
#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 soup_message_queue_next
at soup-message-queue.c line 164
#16 soup_message_queue_first
at soup-message-queue.c line 104
#17 soup_message_queue_remove_message
at soup-message-queue.c line 216
#18 message_finished
at soup-session.c line 1227
#19 g_cclosure_marshal_VOID__VOID
from /opt/gnome/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /opt/gnome/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#24 soup_message_finished
at soup-message.c line 558
#25 soup_message_io_finished
at soup-message-io.c line 153
#26 io_read
at soup-message-io.c line 697
#27 io_write
at soup-message-io.c line 532
#28 soup_message_io_client
at soup-message-io.c line 780
#29 soup_message_send_request_internal
at soup-message-client-io.c line 185
#30 send_request
at soup-connection.c line 769
#31 soup_connection_send_request
at soup-connection.c line 788
#32 send_message
at soup-session-sync.c line 177
#33 soup_session_send_message
at soup-session.c line 1320
#34 e_gw_connection_send_message
at e-gw-connection.c line 561
#35 e_gw_connection_get_items
at e-gw-connection.c line 861
#36 book_view_thread
at e-book-backend-groupwise.c line 2215
#37 g_thread_create_full
from /opt/gnome/lib/libglib-2.0.so.0
#38 start_thread
from /lib/tls/libpthread.so.0
#39 clone
from /lib/tls/libc.so.6



Other information:

Comment 1 Chenthill P 2006-04-11 14:44:35 UTC

Assigning to devashish.

Comment 2 Christian Kirbach 2006-04-11 16:38:03 UTC

unqiue trace

looks valuable, confirming report.

Comment 3 Devashish Sharma 2006-04-21 09:20:26 UTC

Dave The fix for this is there in the last build we gave to you.
Closing this is as fixed, please reopen if you see something similar again.

Comment 4 André Klapper 2006-05-10 01:16:41 UTC

reopening because of bug 339612

Comment 5 André Klapper 2006-05-10 01:16:44 UTC

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

Comment 6 Elijah Newren 2006-06-05 15:09:31 UTC

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

Comment 7 Devashish Sharma 2006-06-07 10:09:21 UTC


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

Comment 8 Chenthill P 2006-08-21 17:45:15 UTC

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