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 274029 - Connector 2.2.1: crash every time on start up
Connector 2.2.1: crash every time on start up
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.1
Other All
: Normal major
: 2.3
Assigned To: Connector Maintainer
Ximian Connector QA
: 300448 301507 301629 302818 303316 303917 304503 305448 306011 306319 307797 308645 308969 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-23 20:59 UTC by Raul Acevedo
Modified: 2005-07-22 04:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Attached patch should fix this problem. (1.33 KB, patch)
2005-03-30 06:01 UTC, Sushma Rai
none Details | Review
Valgrind output running exchange-storage and then setting up exchange account first time (20.65 KB, text/plain)
2005-03-31 21:42 UTC, Raul Acevedo
  Details
After prior output, I quit evolution, and run valgrind on exchange-storage and it crashes right away using my newly created exchange account (20.27 KB, text/plain)
2005-03-31 21:45 UTC, Raul Acevedo
  Details

Description Raul Acevedo 2005-03-23 20:59:27 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
I start evolution with a completely new setup and create an exchange
account.  While the initial account creation is fine, once I actually get
to the main evolution window, evolution-exchange-storage immediately
crashes.  It then crashes every time I start evolution-exchange-storage.

Steps to reproduce the problem:
1. Create new exchange account within evolution.

Actual Results:
Evolution-exchange-storage crashes immediately after I create the account,
every time evolution starts, or every time I start it from the command line.

Expected Results:
Shouldn't crash.

How often does this happen? 
Every time.

Additional Information:
I ran it with E2K_DEBUG=4, here's the last thing it spit out before it died:

GC: looking up info for racevedo@foo.com

GC: Connecting to ldap://sfdc01.ad.foo.com:3268/
GC: connected

GC: dn = CN=Raul Acevedo,CN=Users,DC=ad,DC=foobiz,DC=com

GC: displayName Raul Acevedo
GC: mail racevedo@foo.com
GC: legacyExchangeDN /o=Foo/ou=FOOBIZ/cn=Recipients/cn=racevedo
GC: mDBUseDefaults TRUE
GC: Using global mailbox store limits

Here's the gdb stack trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222363680 (LWP 2231)]
0xb72e87ab in g_type_check_instance_is_a () from
/home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
(gdb) thread apply all bt

Thread 1 (Thread -1222363680 (LWP 2231))

  • #0 g_type_check_instance_is_a
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #1 e_source_peek_uid
    from /home/garnome/2.10.0.1/lib/libedataserver-1.2.so.4
  • #2 add_esource
  • #3 add_sources
  • #4 g_cclosure_marshal_VOID__OBJECT
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #5 g_type_class_meta_marshal
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #10 gconf_accounts_changed
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #11 e_account_list_construct
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #12 idle_construct
  • #13 g_idle_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #14 g_main_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /home/garnome/2.10.0.1/lib/libbonobo-2.so.0
  • #19 main

Comment 1 Raul Acevedo 2005-03-29 01:28:19 UTC
I tried building Connector against an NTLM-patched OpenLDAP 2.2.24,
but I still get a crash. 

I've noticed that I get different crashes every time I run
evolution-exchange-storage.  The E2K_DEBUG output is the same every
time... I get a ton of output showing that basic connectivity to the
server is probably ok, but then it displays the same GC output and
then it crashes.  Here's one stack trace I just got, this crash was in
e_source_peek_uid:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222363680 (LWP 29063)]
0xb75730e7 in e_source_peek_uid () from
/home/garnome/2.10.0.1/lib/libedataserver-1.2.so.4
(gdb) thread apply all bt

Thread 1 (Thread -1222363680 (LWP 29063))

  • #0 e_source_peek_uid
    from /home/garnome/2.10.0.1/lib/libedataserver-1.2.so.4
  • #1 add_esource
  • #2 add_sources
  • #3 g_cclosure_marshal_VOID__OBJECT
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #4 g_type_class_meta_marshal
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #5 g_closure_invoke
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #6 signal_emit_unlocked_R
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #9 gconf_accounts_changed
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #10 e_account_list_construct
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #11 idle_construct
  • #12 g_idle_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #13 g_main_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #15 g_main_context_iterate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #17 bonobo_main
    from /home/garnome/2.10.0.1/lib/libbonobo-2.so.0
  • #18 main

Comment 2 Raul Acevedo 2005-03-29 01:30:34 UTC
Here's another.... again, all the E2K_DEBUG output gets to the "GC"
output stuff, and then a crash, this time in fast_validate:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222363680 (LWP 29079)]
0xb7289d2d in fast_validate () from
/home/garnome/2.10.0.1/lib/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 1 (Thread -1222363680 (LWP 29079))

  • #0 fast_validate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #1 g_utf8_validate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #2 gconf_value_list_from_primitive_list
    from /home/garnome/2.10.0.1/lib/libgconf-2.so.4
  • #3 gconf_engine_set_list
    from /home/garnome/2.10.0.1/lib/libgconf-2.so.4
  • #4 gconf_client_set_list
    from /home/garnome/2.10.0.1/lib/libgconf-2.so.4
  • #5 add_esource
  • #6 add_sources
  • #7 g_cclosure_marshal_VOID__OBJECT
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #8 g_type_class_meta_marshal
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #10 signal_emit_unlocked_R
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #13 gconf_accounts_changed
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #14 e_account_list_construct
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #15 idle_construct
  • #16 g_idle_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #17 g_main_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #19 g_main_context_iterate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /home/garnome/2.10.0.1/lib/libbonobo-2.so.0
  • #22 main

Comment 3 Sushma Rai 2005-03-29 10:00:44 UTC
I am not able to reproduce this crash.
But fixed a problem in the code to add e-sources.
and that should fix this crash.

Fix committed to both cvs head and gnome-2-10 branch.
Comment 4 Raul Acevedo 2005-03-29 19:25:50 UTC
Can you include the patch with this bug report so I can try it?  I
miss being able to run Connector...
Comment 5 Sushma Rai 2005-03-30 06:01:58 UTC
Created attachment 45035 [details] [review]
Attached patch should fix this problem.
Comment 6 Raul Acevedo 2005-03-30 19:39:17 UTC
Applied patch, recreated exchange account, exact same problem still
happens.  :(
Comment 7 Raul Acevedo 2005-03-30 22:42:04 UTC
Ok, so somehow this bug is related to bug 274099.  I thought I had
deleted my exchange account, but due to 74099 some settings stayed
around.  After applying this patch, and then manually editing the old
settings out of all the gconf keys, now finally connector works.

So I don't know what fixed this problem: the patch, completely
removing the old gconf settings due to 74099, or both.  Either way,
connector is now finally working. 
Comment 8 Raul Acevedo 2005-03-30 23:10:15 UTC
Ok, I take it back.  It ran once successfully, but was acting weirdly
(wouldn't mark a message unread, had a problem correctly looking at a
meeting request), so I restarted, and now it's back to crashing every
time, even if I completely manually remove the exchange account and
recreate it.

I'm getting slightly different backtraces though.  Here's two of them,
both of them within the e_source_group_peek_source_by_name call:

(evolution-exchange-storage:12805): GLib-GObject-WARNING **: invalid
uninstantiatable type `gdouble' in cast to `ESource'

(evolution-exchange-storage:12805): e-data-server-CRITICAL **:
e_source_peek_name: assertion `E_IS_SOURCE (source)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224186400 (LWP 12805)]
0x44383478 in strcmp () from /lib/tls/libc.so.6
(gdb) thread apply all bt

Thread 1 (Thread -1224186400 (LWP 12805))

  • #0 strcmp
    from /lib/tls/libc.so.6
  • #1 e_source_group_peek_source_by_name
    from /home/garnome/2.10.0.1/lib/libedataserver-1.2.so.4
  • #2 add_esource
  • #3 add_sources
  • #4 g_cclosure_marshal_VOID__OBJECT
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #5 g_type_class_meta_marshal
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #10 gconf_accounts_changed
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #11 e_account_list_construct
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #12 idle_construct
  • #13 g_idle_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #14 g_main_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /home/garnome/2.10.0.1/lib/libbonobo-2.so.0
  • #19 main

Thread 1 (Thread -1224186400 (LWP 12820))

  • #0 g_type_check_instance_cast
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #1 e_source_group_peek_source_by_name
    from /home/garnome/2.10.0.1/lib/libedataserver-1.2.so.4
  • #2 add_esource
  • #3 add_sources
  • #4 g_cclosure_marshal_VOID__OBJECT
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #5 g_type_class_meta_marshal
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /home/garnome/2.10.0.1/lib/libgobject-2.0.so.0
  • #10 gconf_accounts_changed
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #11 e_account_list_construct
    from /home/garnome/2.10.0.1/lib/evolution/2.2/libeutil.so.0
  • #12 idle_construct
  • #13 g_idle_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #14 g_main_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /home/garnome/2.10.0.1/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /home/garnome/2.10.0.1/lib/libbonobo-2.so.0
  • #19 main

Comment 9 Raul Acevedo 2005-03-31 21:42:58 UTC
Created attachment 45047 [details]
Valgrind output running exchange-storage and then setting up exchange account first time
Comment 10 Raul Acevedo 2005-03-31 21:45:01 UTC
Created attachment 45048 [details]
After prior output, I quit evolution, and run valgrind on exchange-storage and it crashes right away using my newly created exchange account
Comment 11 Kjartan Maraas 2005-04-22 13:06:09 UTC
*** Bug 301507 has been marked as a duplicate of this bug. ***
Comment 12 Raul Acevedo 2005-04-28 23:06:35 UTC
This has been fixed in 2.3.1.  Yay!
Comment 13 Elijah Newren 2005-05-13 04:54:23 UTC
*** Bug 303917 has been marked as a duplicate of this bug. ***
Comment 14 Nagappan Alagappan 2005-05-16 10:58:59 UTC
*** Bug 300448 has been marked as a duplicate of this bug. ***
Comment 15 Nagappan Alagappan 2005-05-17 12:03:41 UTC
*** Bug 304503 has been marked as a duplicate of this bug. ***
Comment 16 Elijah Newren 2005-06-01 04:46:44 UTC
*** Bug 305448 has been marked as a duplicate of this bug. ***
Comment 17 Poornima 2005-06-10 06:20:05 UTC
*** Bug 306011 has been marked as a duplicate of this bug. ***
Comment 18 C Shilpa 2005-06-10 10:24:18 UTC
*** Bug 306319 has been marked as a duplicate of this bug. ***
Comment 19 Poornima 2005-06-15 05:07:21 UTC
*** Bug 303316 has been marked as a duplicate of this bug. ***
Comment 20 Poornima 2005-06-17 04:41:03 UTC
*** Bug 301629 has been marked as a duplicate of this bug. ***
Comment 21 Poornima 2005-06-25 18:29:23 UTC
*** Bug 308969 has been marked as a duplicate of this bug. ***
Comment 22 Poornima 2005-06-25 19:06:17 UTC
*** Bug 302818 has been marked as a duplicate of this bug. ***
Comment 23 Sebastien Bacher 2005-07-09 14:14:11 UTC
*** Bug 307797 has been marked as a duplicate of this bug. ***
Comment 24 Poornima 2005-07-22 04:57:28 UTC
*** Bug 308645 has been marked as a duplicate of this bug. ***