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 329580 - evolution exchange connector
evolution exchange connector
Status: RESOLVED DUPLICATE of bug 316313
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other other
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-02-02 10:52 UTC by rob.verduijn
Modified: 2006-02-02 13:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description rob.verduijn 2006-02-02 10:52:03 UTC 
Distribution: suse 10.0
Package: bug-buddy
Severity: major
Version: GNOME2.12.2 2.12.x
Gnome-Distributor: SUSE
Synopsis: evolution exchange connecter
Bugzilla-Product: bug-buddy
Bugzilla-Component: general
Bugzilla-Version: 2.12.x
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
The evolution exchange connector keeps crashing the
evolution-exchange-storage service, or it refuses to connect to it, in
general it's highly unstable.
I am unable to get more details or logging since I don't know how to do
this, all I get is this annoying popup that keeps telling me it cannot
connect or that the service has crashed.
I cannot give you the exact text since bug buddy has frozen the screen
without any text on it.
Evolution works, the exchange connector crashes at random intervals

Steps to reproduce the crash:
1. configure evolution for use with an exchange server
2. make sure the agenda's filled with some appointments reminders etc
3. restart evolution a couple times, I count myself lucky if I manage to
start it 3 times without the exchange connector crashing
4. If that doesn't do it, try filling your agenda with appointments
dates, or your address book with addresses, make sure they are not local
but on the exchange server

Expected Results:


How often does this happen?
It happens at least once every hour, if I use exchange address book or
agenda almost every time, I count myself lucky if I get to view my
agenda for ten minutes.

Additional Information:



Debugging Information:

Backtrace was generated from
'/opt/gnome/libexec/evolution-exchange-storage'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1099494304 (LWP 13395)]
[New Thread 1103334320 (LWP 14355)]
[Thread debugging using libthread_db enabled]
[New Thread 1099494304 (LWP 13395)]
[New Thread 1103334320 (LWP 14355)]
[Thread debugging using libthread_db enabled]
[New Thread 1099494304 (LWP 13395)]
[New Thread 1103334320 (LWP 14355)]
[New Thread 1101233072 (LWP 13396)]
0xffffe410 in ?? ()

+ Trace 65849

Thread 1 (Thread 1099494304 (LWP 13395))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 memmove
    from /lib/tls/libc.so.6
  • #8 ??
  • #9 soup_socket_get_remote_address
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #10 soup_socket_read_until
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #11 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #12 soup_message_io_pause
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #13 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 soup_socket_disconnect
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #19 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #20 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #21 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #22 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #23 soup_message_io_pause
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #24 soup_message_send_request_internal
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #25 soup_connection_last_used
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #26 send_request
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #27 soup_connection_send_request
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #28 soup_session_async_new_with_options
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #29 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #31 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #34 soup_message_finished
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #35 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #36 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #37 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #38 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #39 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #40 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #41 soup_socket_get_remote_address
    from /opt/gnome/lib/libsoup-2.2.so.8
  • #42 g_vasprintf
    from /opt/gnome/lib/libglib-2.0.so.0
  • #43 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #44 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #45 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #46 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #47 main
  • #0 ?? 




------- Bug created by bug-buddy at 2006-02-02 10:52 -------


Bugreport moved from bug-buddy / general
  to Connector / Connector
Unknown version 2.12.x in product Connector.  Setting version to "unspecified".
Comment 1 Sushma Rai 2006-02-02 13:59:40 UTC 
this is libsoup issue which is fixed in 
libsoup-2.2.7

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