Hey Sushma, On Thu, 2006-08-17 at 18:52 +0530, Sushma Rai wrote:
I wish I could get THAT far. I'm still hosed up by the whole ssl thing. Latest update at least had my mailbox correct (instead of some global list I happen to own on the exchange server) so that's major improvement. But it still refuses to use SSL (non-ssl is prohibited here - not up for discussion and I agree with the management on that point 1000 percent) even though I can authenticate using SSL. The account edit always shows http: for the OWA URL (even though it even says "use_ssl=always" in the gconf registry for that account) and I can't authenticate against that. Change it to "https:" and I can authenticate, but then then Ok button is grayed out and nothing I do will re-enable that button. I have no choice but to cancel and then I can't authenticate because non-ssl is prohibited (it can't even connect to an non-ssl port so it bitches that the URL may be bad). Last version where I was even able to get this two work was ages ago when the dialog had a "use_ssl" option you could set to "always" and THAT worked. Hasn't worked since that dialog object disappeared. Downgrading to 2.6.0 won't resolve that (and downgrading far enough to resolve the ssl problem would break in-line gpg which is even worse for me).
Please try using 2.6.3 and don't try changing the gconf flags. Disable the account you are already having and try creating a new account using "https://"; in URL and if you fail to authenticate please file a bug report in bugzilla.gnome.org, specifying the error you are getting and also E2K_DEBUG traces for Evolution.
I've been trying 2.6.3 since it came bubbling out of Fedora Core
updates a couple of days ago.
No joy.
In fact, I've seen a return of the problem where I end up with
"pgp-keys" instead of "mhw" in my OWA URL after running
ximian-connector-setup-2.6. I thought that problem had gone away with
the last 2.6.2 update, but I guess not.
I'll try filing one or more bugzilla reports but I think we've got more
than one problem here and I'm not sure how to file it or what to call
it. I can't add an Exchange account at all from within Evolution
(Forward button is never enabled after Authenticate),
ximian-connector-setup-2.6 seems to screw up the auto-configuration
(unless I'm very specific on that OWA URL to include my mailbox), it
drops the https back to http when I try and edit the account added by
ximian-connector-setup-2.6, and I can't correct the OWA URL back to
https by editing the account (OK is never enabled after Authenticate
when editing the "Receiving Mail" tab).
for getting debug traces, set E2K_DEBUG=4 in a console and run Evolution See http://www.gnome.org/projects/evolution/bugs.shtml for more details.
Ok... Sooo.... Attached to this message are several files...
evolution.steps The step by step process I've taken.
evo.log The log file from the first run
(attempted to add the account)
evo_con.log Log file from ximian-connector-setup
evo-2.log Log file from second run
(attempted to edit account)
evo-3.log Log file from third run
(prompted for password twice)
accounts.xml gconf-tool dump of evolution accounts
gconftool-2 -g /apps/evolution/mail/accounts
(last one is the Exchange account)
So, how many bugs do I have here? I think I can count several. Do you
want me to file this as one bugzilla report or many?
1.) Can't add the exchange account from within evolution
2.) https: from connector setup gets changed to http:
3.) Wrong mailbox gets selected by connector setup autoconfigure
4.) Can't edit or correct OWA account information
5.) Sporatic multiple password prompts and dialogs
I THINK #1 and #4 are tightly related. For some reason, the
"authenticate" process seems to be succeeding but is NOT reenabling the
button to continue on. IMNSHO, those buttons should never be disabled
in the first place. If the information entered is wrong, and the button
is enabled, then the user gets an error, which is no worse than now (and
maybe better, since he should get an intelligent error message which is
sorely lacking at this point since there is no indication of WHY the
button is gray and no way to determine why the button is gray). If the
information is correct, then we should just accept it and not depend on
the enable switching logic (which appears to be faulty here).
Some of this may be due to some plugin conflict or some sort of upgrade
version skew. I recently had a Scalix connector installed and found
that I couldn't even add ANY accounts after upgrade Evolution. That I
solved by disabling the Scalix plugin and I've since removed it
entirely. But this problem has been present since long before I tried
playing with Scalix (basically all 2.6 version have been busted in this
way). If there is some piece or plugin leftover from some previous
version, that could be part of it. I've been playing with different
versions and doing straight update since 2.0 days. Is there a
possibility that it's an install vs upgrade problem? I'm strongly
tempted to totally uninstall evolution and reinstall. But, would I also
have to blow away all my account information as well?
Here are the plugins which are installed and enabled:
Mark All Read
Itip Formatter
Disable Account
Subject Threading
Groupwise Account Setup
Copy tool
Exchange Operations
Local Address Books
Import to Calendar
Default Sources
Startup wizard
Calendar Publishing
Mailing List Actions
Automatic Contacts
Default Mail Client
Weather Calendars
Print Message
Hula Account Setup
HTTP Calendars
New Mail Notification
Select one source
Save Selected
Mail to task
Groupwise Features
CalDAV sources
Mark calendar offline
Local Calendars
Spamassassin junk plugin
Seems to me this was working (somewhat, at least) in the 2.2 / 2.4
version. What ever versions still had the "SSL_Always" selection option
seemed to work for me. But I was forced to upgrade to 2.6 in order to
get the PGP Inline feature which was vital to me. I have NOTHING in
the /usr/lib/evolution/2.[24]/plugins directories, however.
Sooo... Thoughts? How many bug reports does it appear I need to file
for this? Is there anything else I can gather to include with the bug
reports?
Thanks, Sushma.
Regards,
Mike
P.S. Couple more comments in-line below...
On Fri, 2006-06-09 at 17:15 -0400, Michael H. Warfield wrote:On Fri, 2006-06-09 at 22:39 +0530, Harish Krishnaswamy wrote:Can you get the exchange hackers the relevant crash dumps ? Is there a bug report in bugzilla.gnome.org ?The only way I've been able to get Evolution to talk to our exchange server lately (as in JUST lately today with this latest bug fix for the dain bramaged mailbox bug) is with a major butt-ugly hacking using
The "dain bramaged mailbox bug" was the thing with "pgp-keys" showing
up as my mailbox, instead of "mhw". I guess the workaround for that is
to insure my mailbox is fully specified to ximian-connector-setup-2.6 in
the OWA URL.
stunnel on my local machine and jacking around with the local static /etc/hosts file to redirect the exchange server name to a loopback address on the local system and then through stunnel to the actual exchange server. Gag... With that hack, I can, once again, browse my folders on Exchange. We'll see if anything crashes but how do you debug something when you have to work with such a hack to make it work in the first place?
Correction to my above comment. The stunnel hack worked to "browse"
the folders but I was never able to "open" a folder.
Sushma/Sankar : Can you follow this up, please ?--Harish On Fri, 2006-06-09 at 12:05 -0400, kar wrote:I'm having issues after upgrading with yum too. Anyone know how to roll back to the previous version? On Fri, 2006-06-09 at 06:46 -0700, Shawn Badger wrote:I have similar problems with evolution. My exchange connector was working ok with a few crashes every other day, until I installed 2.6.2. After that the exchange portion didn't crash, but maybe that was because every time I clicked into an exchange folder evolution would crash. I did a yum install evolution* out of desperation and installed all the debug and dev packages. So far no problems other than I can't seem to be able to open any bodies shared calenders yet. On Fri, 2006-06-09 at 14:34 +0200, Ãyvind Gjerstad wrote:On 6/9/06, Pete Biggs <pete biggs org uk> wrote:On Thu, 2006-06-08 at 13:53 -0700, Paul Lemmons wrote:<violin> When I upgraded to Fedora Core 5 I got Evolution 2.6.1. The exchange-connector was broken. Actually it was libsoup that was broken. I stuck with it anyway, though. I found that if I restarted Evolution often enough that it would eventually come up. It was very frustrating. Several days ago libsoup was fixed and life was finally good! No more crashes! On that same day 2.6.2 was also released but it had trouble installing due to dependencies. My global address book was still broken so I looked forward to the dependencies being resolved in hopes that not only would it be stable but it would work like it used to before the upgrade. Well 2.6.2 went on and everything has gone down the drain again. Right now, my machine is running at 100% busy doing what appears to be nothing. If that were not the case then I would see it either filtering or downloading and stalling forever. Attempts to close the application gracefully fail. It simply ignores the fact that I click on the "X". I want to scream. It has gone from extremely bad to pretty good to absolutely unusable. The progression should be from really good towards excellent. Not this rollercoaster ride at the bottom end of acceptability. Is there not some way to keep this from happening? I am a devoted user but this is becoming intolerable.It might be that you've got miss-matched versions of evolution and its backend components after the upgrade (i.e. the backends are still the ones running from 2.6.1). Try doing 'evolution --force-shutdown' in a terminal and restarting evo to see if it's any better.I upgraded my FC5 installation with yum update (to evo 2.6.2) . I'm also using exchange connector, and now I don't get any new mails! To be more precise, the folder (Inbox) lists unread messages, but they do not appear in the message pane. If I quit evolution and restart I get those mails, but mails that arrive after that are just listed in the number behind Inbox. As fas as I can tell all my Evolution components are 2.6.2. I have also restarted everything (and also rebooted). How do I debug this?_______________________________________________ Evolution-list mailing list Evolution-list gnome org http://mail.gnome.org/mailman/listinfo/evolution-list_______________________________________________ Evolution-list mailing list Evolution-list gnome org http://mail.gnome.org/mailman/listinfo/evolution-list
-- Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw WittsEnd com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
Attachment:
evo.log
Description: Text Data
Attachment:
evo-2.log
Description: Text Data
Attachment:
evo-3.log
Description: Text Data
Attachment:
evo_con.log
Description: Text Data
Attachment:
accounts.xml
Description: application/xml
Attachment:
evolution.steps
Description: Text document
Attachment:
signature.asc
Description: This is a digitally signed message part