Bug 567042 – Crash in g_hash_table_lookup_node find_message at mail-stub-exchange.c line 332

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 567042 - Crash in g_hash_table_lookup_node find_message at mail-stub-exchange.c line 332


Summary:	Crash in g_hash_table_lookup_node find_message at mail-stub-exchange.c line 332


Status:	RESOLVED INCOMPLETE

Product:	Evolution Exchange
Classification:	Deprecated
Component:	Connector
Version:	2.28.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Connector Maintainer
QA Contact:	Ximian Connector QA

URL:
Whiteboard:

Duplicates:	569847 569965 588536 588578 588590 594033 (view as bug list)
Depends on:
Blocks:

Reported:	2009-01-08 16:42 UTC by dann.church
Modified:	2010-05-20 22:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description dann.church 2009-01-08 16:42:37 UTC

What were you doing when the application crashed?
Had just opened mail and deleted one email that I had just read.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.9-159.fc10.i686.PAE #1 SMP Tue Dec 16 14:59:37 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 88702976 vsize: 88702976 resident: 28438528 share: 10895360 rss: 28438528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231432758 rtime: 56 utime: 42 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb8006760 (LWP 3667)]
[New Thread 0xb7d04b90 (LWP 3676)]
0x00110424 in __kernel_vsyscall ()

+ Trace 211391

Thread 1 (Thread 0xb8006760 (LWP 3667))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 run_bug_buddy
at gnome-breakpad.cc line 223
#5 check_if_gdb
at gnome-breakpad.cc line 292
#6 bugbuddy_segv_handle
at gnome-breakpad.cc line 84
#7 <signal handler called>
#8 g_hash_table_lookup_node
at ghash.c line 135
#9 IA__g_hash_table_lookup
at ghash.c line 668
#10 find_message
at mail-stub-exchange.c line 332
#11 set_message_flags
at mail-stub-exchange.c line 2053
#12 connection_handler
at mail-stub.c line 244
#13 g_io_unix_dispatch
at giounix.c line 162
#14 g_main_dispatch
at gmain.c line 2144
#15 IA__g_main_context_dispatch
at gmain.c line 2697
#16 g_main_context_iterate
at gmain.c line 2778
#17 IA__g_main_loop_run
at gmain.c line 2986
#18 bonobo_main
at bonobo-main.c line 311
#19 main
at main.c line 278



----------- .xsession-errors (2248715 sec old) ---------------------
** (nautilus:3232): WARNING **: Unable to add monitor: Not supported
beagled will run in the background.
Use beagle-status to check progress of beagled.
For log files check /home/dchurch/.beagle/Log/current-Beagle.
** (gnome-panel:3231): WARNING **: Failed to establish a connection with GDM: No such file or directory
IO Error from X Window System.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nautilus: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
pam-panel-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
The application 'gnome-panel' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------

Comment 1 Akhil Laddha 2009-01-31 14:30:43 UTC

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

Comment 2 Akhil Laddha 2009-01-31 14:30:59 UTC

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

Comment 3 palfrey 2009-07-14 15:40:03 UTC

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

Comment 4 Fabio Durán Verdugo 2009-07-14 21:42:25 UTC

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

Comment 5 Akhil Laddha 2009-07-15 04:31:09 UTC

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

Comment 6 Akhil Laddha 2009-07-15 04:32:02 UTC

last dupe in 2.26.x

Comment 7 Akhil Laddha 2009-09-04 04:17:13 UTC

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

Comment 8 Milan Crha 2009-12-01 17:13:54 UTC

Similar downstream bug report under 2.28.0:
https://bugzilla.redhat.com/show_bug.cgi?id=543056

Comment 9 Milan Crha 2010-03-26 14:56:23 UTC

Thanks for a bug report. I'm not able to reproduce this on an actual master (~2.30.0). Could anybody of you try to reproduce this on an upcoming Evolution 2.30.0+, please? There had been done some changes in evolution-exchange architecture, there is no mail-stub-exchange.c file anymore, neither evolution-exchange-storage executable, thus the trace will be slightly different for sure. Thanks in advance.

Comment 10 Tobias Mueller 2010-05-20 21:09:16 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 11 mjs 2010-05-20 22:05:40 UTC

Just waiting for Fedora 13 to test. Will report back then.