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 304483 - Exchange Server connectivity - OWM contact
Exchange Server connectivity - OWM contact
Status: RESOLVED DUPLICATE of bug 301396
Product: evolution
Classification: Applications
Component: Shell
unspecified
Other other
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-05-17 09:40 UTC by ricahrd
Modified: 2005-06-05 20:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description ricahrd 2005-05-17 09:40:35 UTC
Distribution: Debian 3.1
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Exchange Server connectivity - OWM contact
Bugzilla-Product: Evolution
Bugzilla-Component: Shell
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
At the end of the Exchange component, after entering the OWM address and
hitting th 'forward' button application crashed

Steps to reproduce the crash:
1. first time
2. 
3. 

Expected Results:
didn't know, figured Evolution would try to contact OWM server

How often does this happen?
first time

Additional Information:
I don't think Uuniversity of Virginia supports OWM via any other mode
except web browser.



Debugging Information:

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229451136 (LWP 9367)]
[New Thread -1247814736 (LWP 16620)]
[New Thread -1230955600 (LWP 9368)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in ?? ()

Thread 3 (Thread -1230955600 (LWP 9368))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-17 09:40 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was ricahrd@cvilleweb.net.

Comment 1 Nagappan Alagappan 2005-05-17 11:40:54 UTC
Richard: Thanks for the bug report. Unfortunately, that stack trace is not very
useful in determining the cause of the crash. Can you get us one with debugging
symbols? Please see http://live.gnome.org/GettingTraces for more information on
how to do so.
Comment 2 Sebastien Bacher 2005-06-05 20:47:44 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

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