GNOME Bugzilla – Bug 321039
Enhance the configuration dialog for the exchange connector
Last modified: 2010-03-25 04:06:05 UTC
Steps to reproduce: 1. Start evolution 2. 3. Stack trace: Backtrace was generated from '/opt/gnome/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1234352448 (LWP 6751)] [New Thread -1235993680 (LWP 6757)] [Thread debugging using libthread_db enabled] [New Thread -1234352448 (LWP 6751)] [New Thread -1235993680 (LWP 6757)] [Thread debugging using libthread_db enabled] [New Thread -1234352448 (LWP 6751)] [New Thread -1235993680 (LWP 6757)] 0xffffe410 in ?? ()
+ Trace 63968
Thread 1 (Thread -1234352448 (LWP 6751))
Other information: Description of the crash: History: I use evolution inside kde. We have in the office different exchange servers. I have my mailbox on exc-mch02, and use it for my OWA-Url. On exc-mch01 there are mailing groups. Domain Controller with LDAP and adress book is inf-mch01. Evolution 2.2 works. Saturday, 5 November I upgraded SuSE 9.3 to 10.0, so also evolution from 2.2 to 2.4. A first test with evo 2.4 was ok. Monday evolution didn't work no more. It suddently wants to autenticate me with exc-mch01 (not the usual exc-mch02). Probably the windows-admins are playing with the exchange configuration. I don't ask them, because they never answer my linux-related questions :-( I boot windows and do a ethereal trace. I don't understand the output in detail, but in the ip-dump there is only traffic with exc-mch02 and inf-mch01 (where the autentication seems to be done), AND NOT with exc-mch01. I start evolution with CAMEL_DEBUG=all and can see, that for some reason he wants to autenticate with NTLM with exc-mch01. And I had sometimes crashes which I didn't save because the trace was not so informative (no debuginfo yet installed). Evolution gives no chance to modify this setting (only OWA-Url is possible) so I try to modify the settings in %gconf.xml (obviously after killing gconfd): nothing. I rename the .evolution directory and start a new setup: nothing. Sometimes evolution crashes, sometimes I get two(!) dialogs to enter my password (the second dialog covers the error box of the first dialog). I did my best to feed the system with debuginfos. If some are missing, please tell me: ~> rpm -qa|grep debuginfo | sort cairo-debuginfo-1.0.0-7 contact-lookup-applet-debuginfo-0.13-5 evolution-data-server-debuginfo-1.4.0-5 evolution-debuginfo-2.4.0-3 evolution-exchange-debuginfo-2.4.0-5 evolution-galago-debuginfo-0.3.1-3 evolution-sharp-debuginfo-0.10.1-4 evolution-webcal-debuginfo-2.4.0.1-3 gal2-debuginfo-2.5.3-5 gconf2-debuginfo-2.12.0-2 glib2-debuginfo-2.8.1-3 glibc-debuginfo-2.3.5-40 gnome-libs-debuginfo-1.4.1.7-690 gnome-vfs2-debuginfo-2.12.0-9 gtk2-debuginfo-2.8.3-4 gtk2-engines-debuginfo-2.6.5-5 gtk-engines-debuginfo-0.12-965 gtkhtml2-debuginfo-3.8.0-3 kernel-smp-debuginfo-2.6.13-15 libbonobo-debuginfo-2.10.1-3 libbonoboui-debuginfo-2.10.1-3 libgnome-debuginfo-2.12.0.1-2 libopensync-plugin-evolution2-debuginfo-0.17-4 libsoup-debuginfo-2.2.6.1-3 mozilla-nss-debuginfo-3.10-12 nautilus-sendto-debuginfo-0.4-3 openssl-debuginfo-0.9.7g-2 orbit2-debuginfo-2.12.4-2 orbit-debuginfo-0.5.17-339 shared-mime-info-debuginfo-0.16-5 spamassassin-debuginfo-3.0.4-4 xorg-x11-debuginfo-6.8.2-100 yelp-debuginfo-2.12.0-3
reassigning to exchage component
Looks like migration bug from evo 2.2 to evo 2.4.
Thanks Poornima, but I don't think so. As I told, after doing the upgrade I could start evolution 2.4 correctly and have a look at my mails. The problems began two da One day evolution stopped crashing at startup, but it still toughed it out to autoenticate me wich the server exc-mch01 instead of exc-mch02 (which is in my OWA Url). Today I tried another time to modify the evolution-settings with the gconf-editor, I navigated to apps/evolution/mail and edited the key account, replacing all occurrences of exc-mch01 with exc-mch02. Halleluja, it worked! This time I finally got the question for the password of exc-mhc02 and it was accepted! I don't know what the exchange admins were sometimes doing (they don't talk with me), but there are situations (replica?) where the exchange connector acts up and dumps. Cetero censeo: Please enhance the configuration dialog for the exchange connector with some expert dialog where you can rub the servers in.
Thanks Riccardo. To enhance the configuration for exchange connector is already in discussion and it will be fixed in evolution 2.6. Confirming this bug to keep track of enahncement of configuration dialog. Changed summary as well.
Riccardo Escher, Can you test one more stuff? Can you please 1. disable your exchange account, 2. back up ~/.gconf/apps/evolution 3. recreate the account providing owa url and see if new account works for you? asking password twice problem has been fixed in 2.5.x? Is it still crashing for you?
Hello Sushma Rai, thank you for your reply. As I told in comment #3, I solved the autentication problem by editing the .gconf manually; now the connector is working without problems, up to now it is not crashing (knock on wood). I remember that onw of my tests was deactivating and reentering the owa-url, but without success. I am still using 2.4.0 (SuSE 10 with all online patches).
Thanks. I am marking it as an enhancement request bug.
UI change, moving to 2.7
Tested this on the 2.28.x and 2.30.x versions and changing the server details worked well on the latest stable versions. Enter the new details, and authenticate against it. Then it should start fetching the details from the newer configurations. I am marking this as obsolete for now since the UI has gone through some iterations of work over the past releases. Kindly reopen the bug if it still occurs for you with the 2.30.x releases.