Bug 348037 – evolution crash accessing exchange server

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 348037 - evolution crash accessing exchange server


Summary:	evolution crash accessing exchange server


Status:	RESOLVED DUPLICATE of bug 344196

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-07-19 18:41 UTC by Herbert Carl Meyer
Modified:	2006-07-19 19:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Herbert Carl Meyer 2006-07-19 18:41:42 UTC

Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution crash accessing exchange server
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
I turned an exchange account back on to see if it had been fixed.
apparently not

Steps to reproduce the crash:
1. work for cheezy outfit using exchange server.
2. ask incompetent droids in systems at cheezy outfit for enough info to
use IMAP protocol to access echange server. Request greeted with
resounding ? Huh ? whatsa IMAP ?
3. wait for exchange connector to be fixed. (do not hold breath).

Expected Results: exchange connector fixed. So far, no joy.


How often does this happen? Every time I turn the exchange account back
on.


Additional Information: Further sarcasm not needed.



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 -1209100608 (LWP 2726)]
[New Thread -1342190688 (LWP 2825)]
[New Thread -1331700832 (LWP 2821)]
[New Thread -1321210976 (LWP 2815)]
[New Thread -1310721120 (LWP 2814)]
[New Thread -1298142304 (LWP 2790)]
[New Thread -1285960800 (LWP 2775)]
[New Thread -1287652448 (LWP 2772)]
[New Thread -1253672032 (LWP 2756)]
[New Thread -1243182176 (LWP 2755)]
[New Thread -1232282720 (LWP 2753)]
(no debugging symbols found)
0x00ccf402 in __kernel_vsyscall ()

+ Trace 69448

Thread 2 (Thread -1342190688 (LWP 2825))

#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-07-19 18:41 -------

Comment 1 André Klapper 2006-07-19 19:38:30 UTC

Thanks for the bug report, it was a pleasure to read it. :-)
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 344196 ***