FedoraForum.org - Fedora Support Forums and Community
Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2012
    Location
    SJ, Costa Rica
    Posts
    3

    Evolution Crash after applying today updates

    Hi everybody,

    today I apply some updates to my Fedora 17 x64, and now, when I try to start up evolution I receive the following error:

    [esanchez@sj-esanchez share]$ evolution

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

    (evolution:6879): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
    evolution: ntlm.c:38: ldap_ntlm_bind: Assertion `( (ld)->ldc->ldc_options.ldo_valid == 0x2 )' failed.
    Aborted (core dumped)
    I made a backup of my $HOME/.local/share/evolution folder, and then deleted it. The same error still appears...

    Any advice on how to resolve this?
    Best regards,
    -eduardo s.m.

    ---------- Post added at 04:35 PM ---------- Previous post was at 03:28 PM ----------

    UPDATE:

    I checked /var/log/messages and this is what I found:

    Aug 27 16:22:22 sj-esanchez abrt[8008]: Saved core dump of pid 8000 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-08-27-16:22:22-8000 (63967232 bytes)

    So I checked that dir, and a lot files are written there, the reason file says:

    Process /usr/bin/evolution was killed by signal 6 (SIGABRT)

    corebacktrace says:
    ebc779125d37b2b0595730b6d78d477fe7b6bc53 0x35925 raise libc.so.6 -
    ebc779125d37b2b0595730b6d78d477fe7b6bc53 0x370d8 abort libc.so.6 -
    ebc779125d37b2b0595730b6d78d477fe7b6bc53 0x2e6a2 __assert_fail_base libc.so.6 -
    ebc779125d37b2b0595730b6d78d477fe7b6bc53 0x2e752 __assert_fail libc.so.6 -
    5723f732892b382fddf95cb50396d376c229e30c 0x381ec ldap_ntlm_bind libexchange.so.0 -
    5723f732892b382fddf95cb50396d376c229e30c 0x26894 - libexchange.so.0 -
    5723f732892b382fddf95cb50396d376c229e30c 0x26b0d - libexchange.so.0 -
    5723f732892b382fddf95cb50396d376c229e30c 0x26ca8 - libexchange.so.0 -
    5723f732892b382fddf95cb50396d376c229e30c 0x276f7 e2k_global_catalog_lookup libexchange.so.0 -
    97e03a38e08accee785440e6b8a59a4e6ca8ea4c 0x12427 exchange_account_connect libexchange-storage.so -
    ba1a0625976d3574fb60aa801e0a0cdfa78a6277 0xe750 exchange_config_listener_authenticate liborg-gnome-exchange-operations.so -
    ba1a0625976d3574fb60aa801e0a0cdfa78a6277 0xf3c0 - liborg-gnome-exchange-operations.so -
    41d17d4a5034f12665fbcbb2c80a4beca8bb0881 0x12af4 g_cclosure_marshal_VOID__OBJECTv libgobject-2.0.so.0 -
    41d17d4a5034f12665fbcbb2c80a4beca8bb0881 0xf943 - libgobject-2.0.so.0 -
    41d17d4a5034f12665fbcbb2c80a4beca8bb0881 0x27d88 g_signal_emit_valist libgobject-2.0.so.0 -
    41d17d4a5034f12665fbcbb2c80a4beca8bb0881 0x287c2 g_signal_emit libgobject-2.0.so.0 -
    e56fb6650b2d4190d3c3e33ae068ee7cb73f30bf 0x11ff0 - libedataserver-1.2.so.16 -
    ba1a0625976d3574fb60aa801e0a0cdfa78a6277 0xdb8e - liborg-gnome-exchange-operations.so -
    8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x47695 g_main_context_dispatch libglib-2.0.so.0 -
    8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x479c8 - libglib-2.0.so.0 -
    8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x47dc2 g_main_loop_run libglib-2.0.so.0 -
    0008a6c4028b3826f8905324c770e7aa450e5d3b 0x179f75 gtk_main libgtk-3.so.0 -
    5b7178c7db7ab07be318112e4d55a02b8578ec28 0x22da main [exe] -
    Should I make a bug report?

    best regards,
    -eduardo s.m.

    ---------- Post added at 05:01 PM ---------- Previous post was at 04:35 PM ----------

    Seems there's already a bug report for this:

    https://bugzilla.redhat.com/show_bug.cgi?id=851624


    downgrading openldap solves the problem for now:

    yum downgrade openldap openldap-devel openldap-clients
    Hope this helps someone with the same problem.

    best regards,
    -eduardo s.m.

  2. #2
    Join Date
    Aug 2012
    Location
    Germany
    Posts
    1

    Re: Evolution Crash after applying today updates

    Thanks, this helped me. Downgraded openldap-.. from 2.4.32-2 to 2.4.30-2 on Fedora 17, 32 bit

    Kind Regards,
    Peter

  3. #3
    Join Date
    Jun 2012
    Location
    Seattle, WA
    Posts
    2

    Re: Evolution Crash after applying today updates

    This helped me too - thanks!

  4. #4
    Join Date
    Jun 2012
    Location
    SJ, Costa Rica
    Posts
    3

    Re: Evolution Crash after applying today updates

    If you people don't want to make the downgrade, you can download the latest build of Evolution Exchange here:

    http://koji.fedoraproject.org/koji/b...buildID=350864

    I already tried it, and it worked like a charm.

    best regards,
    -eduardo s.m.

Similar Threads

  1. Updates broke networking today
    By sonoran in forum F15 Development
    Replies: 2
    Last Post: 23rd April 2011, 08:12 AM
  2. Hello, I'm online today - did a 1,000 updates!
    By SlowJet in forum Linux Chat
    Replies: 0
    Last Post: 13th February 2011, 10:43 PM
  3. F12, Evolution 2.28.2, and Tasks Overdue and Due Today
    By jadamcraig in forum Using Fedora
    Replies: 0
    Last Post: 28th January 2010, 01:47 PM
  4. Fedora 9 Freezing Shortly After Applying Updates
    By dwhitney67 in forum Using Fedora
    Replies: 2
    Last Post: 28th May 2008, 07:46 PM
  5. Kernel Update (today) caused system crash to Fedora 6
    By jensenium in forum Using Fedora
    Replies: 4
    Last Post: 20th August 2007, 08:54 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •