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 345987 - Evolution crash while experiencing the exchange-data-server hang
Evolution crash while experiencing the exchange-data-server hang
Status: RESOLVED DUPLICATE of bug 344196
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other other
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-06-26 22:01 UTC by Jack Woychowski
Modified: 2006-06-27 06:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Jack Woychowski 2006-06-26 22:01:30 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution Exchange [Was: Connector]
Severity: normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crash while experiencing the exchange-data-server hang
Bugzilla-Product: Evolution Exchange [Was: Connector]
Bugzilla-Component: Connector
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
While going through the pain of the exchange-data-server "hang" the GUI
hung
and crashed.

Steps to reproduce the crash:
1. Start evolution
2. Experience woe while waiting for multiple refreshes, etc. to
eventually hang
3. evolution crashed.

Expected Results:

Well, not a crash; perhaps just the usual "lost connection to exchange
backend process" message.

How often does this happen?

The crash happens about 15% of the time; the backend hang happens all
the time.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208633664 (LWP 13973)]
[New Thread -1292362848 (LWP 13992)]
[New Thread -1281479776 (LWP 13990)]
[New Thread -1270989920 (LWP 13989)]
[New Thread -1260500064 (LWP 13987)]
[New Thread -1235584096 (LWP 13986)]
[New Thread -1225094240 (LWP 13985)]
[New Thread 155618208 (LWP 13984)]
[New Thread 145128352 (LWP 13983)]
[New Thread 109452192 (LWP 13981)]
(no debugging symbols found)
0x00a0f402 in __kernel_vsyscall ()

Thread 8 (Thread 155618208 (LWP 13984))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 camel_exchange_store_connected
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #11 camel_object_trigger_event
    from /usr/lib/libcamel-1.2.so.0
  • #12 camel_stub_send
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #13 start_thread
    from /lib/libpthread.so.0
  • #14 clone
    from /lib/libc.so.6




------- Bug created by bug-buddy at 2006-06-26 22:01 -------

Comment 1 Sushma Rai 2006-06-27 06:31:18 UTC

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