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 329601 - Exchange password dialog comes up before the shell
Exchange password dialog comes up before the shell
Status: RESOLVED INCOMPLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other Linux
: Normal minor
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
evolution[passwords]
Depends on:
Blocks: 323345
 
 
Reported: 2006-02-02 12:35 UTC by Sushma Rai
Modified: 2012-02-02 14:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sushma Rai 2006-02-02 12:35:24 UTC 
When an exchange account is configured and password is not
remembered, while invoking evolution, first the 
password prompt dialog comes up and after a few seconds delay
shell comes up.

Ideally shell should come up first and later the password dialog.
Comment 1 Matthew Barnes 2008-03-11 00:52:02 UTC 
Bumping version to a stable release.
Comment 2 André Klapper 2012-01-04 11:11:22 UTC 
Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages.

This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) by reporting back and providing both your version and the package that you use? Thanks in advance!
Comment 3 André Klapper 2012-02-02 14:38:06 UTC 
Closing this bug report as no updated information has been provided.

Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment.

Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.