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 537773 - Crash in renew_cb at e2k-context.c line 2526
Crash in renew_cb at e2k-context.c line 2526
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
3.0.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2008-06-11 12:15 UTC by Reid Thompson
Modified: 2013-07-23 14:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Reid Thompson 2008-06-11 12:15:28 UTC
What were you doing when the application crashed?
Revision: 35625
starting up after building


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.2 2008-06-02 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r8 #1 SMP PREEMPT Tue May 13 08:35:55 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: marble-look
Icon Theme: gnome

Memory status: size: 85909504 vsize: 85909504 resident: 29863936 share: 10067968 rss: 29863936 rss_rlim: 4294967295
CPU usage: start_time: 1213186405 rtime: 283 utime: 249 stime: 34 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb63976e0 (LWP 6820)]
[New Thread 0xb60e2b90 (LWP 6821)]
0xb7f74410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb63976e0 (LWP 6820))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at ../../../glib/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at ../../../glib/glib/gspawn.c line 694
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 ??
  • #10 g_hash_table_insert_internal
    at ../../../glib/glib/ghash.c line 118
  • #11 renew_cb
    at ../../../../../evolution-data-server/servers/exchange/lib/e2k-context.c line 2526
  • #12 final_finished
    at ../../../libsoup/libsoup/soup-session-async.c line 203
  • #13 IA__g_cclosure_marshal_VOID__VOID
    at ./gmarshal.c line 77
  • #14 IA__g_closure_invoke
    at ../../../glib/gobject/gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at ../../../glib/gobject/gsignal.c line 2510
  • #16 IA__g_signal_emit_valist
    at ../../../glib/gobject/gsignal.c line 2199
  • #17 IA__g_signal_emit
    at ../../../glib/gobject/gsignal.c line 2243
  • #18 soup_message_finished
    at ../../../libsoup/libsoup/soup-message.c line 837
  • #19 soup_message_io_finished
    at ../../../libsoup/libsoup/soup-message-io.c line 172
  • #20 IA__g_cclosure_marshal_VOID__VOID
    at ./gmarshal.c line 77
  • #21 IA__g_closure_invoke
    at ../../../glib/gobject/gclosure.c line 490
  • #22 signal_emit_unlocked_R
    at ../../../glib/gobject/gsignal.c line 2440
  • #23 IA__g_signal_emit_valist
    at ../../../glib/gobject/gsignal.c line 2199
  • #24 IA__g_signal_emit
    at ../../../glib/gobject/gsignal.c line 2243
  • #25 socket_read_watch
    at ../../../libsoup/libsoup/soup-socket.c line 1049
  • #26 g_io_unix_dispatch
    at ../../../glib/glib/giounix.c line 162
  • #27 IA__g_main_context_dispatch
    at ../../../glib/glib/gmain.c line 2063
  • #28 g_main_context_iterate
    at ../../../glib/glib/gmain.c line 2696
  • #29 IA__g_main_loop_run
    at ../../../glib/glib/gmain.c line 2919
  • #30 bonobo_main
    at bonobo-main.c line 311
  • #31 main
    at ../../../evolution-exchange/storage/main.c line 278
  • #0 __kernel_vsyscall


----------- .xsession-errors (55185 sec old) ---------------------
NetExtender connected successfully. Type "Ctrl-c" to disconnect...
env is null
Saving profiles...
Opening /home/rthompso/.netextender
closing
Done.
JNI: disconnectNX: sending SIGINT to netExtender (PID = 24135)
Disconnecting NetExtender...
SSL-VPN logging out...
SSL-VPN connection is terminated.
Exiting NetExtender client
JNI: LaunchNX: Exiting LaunchNX, returning (1)
Loading saved profiles...
Loaded profile: hatch.ateb.com
Done.
--------------------------------------------------
Comment 1 Akhil Laddha 2010-09-14 09:06:25 UTC
This bug was reported against a GNOME version that is now not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

The current stable GNOME and Evolution version is 2.30.2.
Please check if the problem you reported here still occurs with a recent version of GNOME by reporting back which exact version you tested against

Thank you for reporting this bug and we are sorry it could not be fixed for your version.
Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 2 Milan Crha 2011-06-15 06:18:32 UTC
Reopening, I just got a downstream bug report about the same in 2.32.2:
https://bugzilla.redhat.com/show_bug.cgi?id=713081

executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.12-90.fc14.i686
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11
(SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: happens when trying to pull a name from the company address
list

Core was generated by `/usr/libexec/e-addressbook-factory'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 0xb7760730 (LWP 2492))

  • #0 renew_cb
    at e2k-context.c line 2554
  • #1 process_queue_item
    at soup-session-async.c line 383
  • #2 run_queue
    at soup-session-async.c line 418
  • #3 idle_run_queue
    at soup-session-async.c line 443
  • #4 g_idle_dispatch
    at gmain.c line 4254
  • #5 g_main_dispatch
    at gmain.c line 2149
  • #6 g_main_context_dispatch
    at gmain.c line 2702
  • #7 g_main_context_iterate
    at gmain.c line 2780
  • #8 g_main_loop_run
    at gmain.c line 2988
  • #9 main
    at e-data-book-factory.c line 619

Comment 3 Milan Crha 2011-08-03 06:54:19 UTC
Downstream bug report from 3.0.2:
https://bugzilla.redhat.com/show_bug.cgi?id=727126

Thread 1 (Thread 0xb4ffeb70 (LWP 9704))

  • #0 g_hash_table_lookup_node_for_insertion
    at ghash.c line 386
  • #1 g_hash_table_insert_internal
    at ghash.c line 978
  • #2 renew_cb
    at e2k-context.c line 2633
  • #3 process_queue_item
    at soup-session-async.c line 383
  • #4 run_queue
    at soup-session-async.c line 418
  • #5 idle_run_queue
    at soup-session-async.c line 441
  • #6 g_idle_dispatch
    at gmain.c line 4558
  • #7 g_main_dispatch
    at gmain.c line 2441
  • #8 g_main_context_dispatch
    at gmain.c line 3014
  • #9 g_main_context_iterate
    at gmain.c line 3092
  • #10 g_main_loop_run
    at gmain.c line 3300
  • #11 e2k_context_soup_thread
    at e2k-context.c line 406
  • #12 g_thread_create_proxy
    at gthread.c line 1955
  • #13 start_thread
    at pthread_create.c line 305
  • #14 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133

Comment 4 André Klapper 2012-09-20 14:53:58 UTC
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers.

If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible).

There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX.
Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
Comment 5 André Klapper 2013-07-23 14:34:13 UTC
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago.

evolution-exchange is now deprecated and not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.

Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported.
Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.