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 664016 - Password prompt for Notes, Tasks, etc. on login
Password prompt for Notes, Tasks, etc. on login
Status: RESOLVED FIXED
Product: evolution-mapi
Classification: Applications
Component: miscellaneous
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-14 09:08 UTC by Milan Crha
Modified: 2011-11-15 12:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ema patch (3.2.2) (6.54 KB, patch)
2011-11-14 18:55 UTC, Milan Crha
committed Details | Review
evo patch (6.45 KB, patch)
2011-11-15 12:50 UTC, Milan Crha
committed Details | Review

Description Milan Crha 2011-11-14 09:08:43 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=753383

I access company's Exchange 2007 server via evolution-mapi. Since I work from
home primarily, I need establish the VPN first before I can connect to the
exchange server. The problem is when I'm offline, I will be kept prompted for
the passwords for Evolution Notes, Tasks, etc. 

Version-Release number of selected component (if applicable):
Fedora 16
Gnome 3.2(?) comes with Fedora 16
evolution-mapi-3.2.1-1.fc16.x86_64
evolution-NetworkManager-3.2.1-2.fc16.x86_64
evolution-3.2.1-2.fc16.x86_64
evolution-help-3.2.1-2.fc16.noarch
evolution-data-server-3.2.1-1.fc16.x86_64

How reproducible:
Log in to the system without establish the VPN which is required to connect to
the Exchange server.

Steps to Reproduce:
1. Configure the Evolution to connect to the Exchange server.
2. Log into the system without establish the VPN

Actual results:
I'm kept prompted for the password for the Evolution Notes, Tasks, etc.

Expected results:
Either I won't be prompted at all, system make an intelligent decision when
detects there is connectivity issue to the Exchange server, or at least be
offered the choice to stay "offline mode" so I'm only prompted once.
Comment 1 Milan Crha 2011-11-14 18:46:00 UTC
Moving to evolution-mapi and confirming.
Comment 2 Milan Crha 2011-11-14 18:55:19 UTC
Created attachment 201394 [details] [review]
ema patch (3.2.2)

for evolution-mapi;

There is an issue with OpenChange [1] about not providing accurate errors when the destination server is not reachable. This patch adds a workaround for the issue and mimics certain parts of the openchange code and sets MAPI_E_NETWORK_ERROR when the server is unreachable. The patch is applicable to 3.2.2 of evolution-mapi, and I'm committing a similar patch to git master as well (it also contains a new translation string). The patch also makes sure that other than event sources are not marked for alarm notifications, because evolution-alarm-notify (the process which asks for a password) is checking for alarms each source, though evolution itself supports alarm on event sources only. I think it's a feature, thus change only in evolution-mapi.

The disadvantage is that if the server is unreachable on alarm notify process start, the calendar is skipped and never checked for availability again (never, except of changes like in Preferences for alarm notifications). I'm not sure how to check for network availability, because periodical checking might not be the best option here.

[1] http://tracker.openchange.org/issues/372
Comment 3 Milan Crha 2011-11-14 18:58:14 UTC
Created commit a577ac5 in ema master (3.3.2+)
Created commit af66c96 in ema gnome-3-2 (3.2.3+)
Comment 4 Milan Crha 2011-11-15 12:50:44 UTC
Created attachment 201432 [details] [review]
evo patch

for evolution;

Thinking of it, the change in evolution-mapi doesn't worth it without change like this in evolution, because evo-mapi only makes alarms ignored from unreachable MAPI accounts.

This patch makes evolution-alarm-notify process try to reconnect each 5 minutes for sources which report repository-offline error. Thus the alarms might not be older than 5 minutes after successful login into vpn.
Comment 5 Milan Crha 2011-11-15 12:53:26 UTC
Created commit 5fc51b9 in evo master (3.3.2+)
Created commit 02eceb2 in evo gnome-3-2 (3.2.3+)