Bug 1306540
| Summary: | Evolution will not show Exchange EWS account if there was an account previously configured for that address | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Wegener <twegener> |
| Component: | evolution | Assignee: | Milan Crha <mcrha> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | extras-qa, lucilanga, matt, mbarnes, mcrha, mikhail.v.gavrilov, tpopela, twegener |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | evolution-data-server-3.22.4 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 879773 | Environment: | |
| Last Closed: | 2016-02-15 10:30:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tim Wegener
2016-02-11 09:03:55 UTC
Thanks for a bug report, or a clone, whatever. There is no problem to create both evolution-ews and evolution-mapi accounts for the same server and the same user, the only limitation is that the server supports both protocols. More important question is: when did you install the evolution-ews? By the way, the version series 3.16.x is ancient, the current stable is 3.18.4, which will be superseded with 3.18.5 release the next week, and even more importantly with 3.20.0 release in the next few weeks. If this is about the issue of installing evolution-ews, but not restarting background processes, thus the newly added modules could be loaded, then it is addresses in the 3.20.0. (In reply to Milan Crha from comment #1) ... > More important question is: when did you install the evolution-ews? IIRC, the sequence was roughly: 1. Install evolution-mapi. 2. Set up email account using MAPI. (This worked.) 3. Install evolution-ews. 4. Set up email account using EWS. (The wizard accepted everything, but the account did not show up after finishing it.) 5. Restarting evolution and trying again did not help. 6. Removing the MAPI account, clearing out the config and killing all evolution-related processes, starting evolution and adding the account using EWS worked fine. Thanks for the information. The restart of the background processes made it work. As I noted above, this will be fixed with 3.20.0, thus I'm closing this. Seems this has reappeared in 3.22.3-1 in Fedora 25? Steps to reproduce: 1. yum install evolution 2. didn't see the Exchange Web Services options, closed Evolution 3. yum install evolution-ews 4. Exchange Web Services option is now available 5. Try to add the account 3 times, no luck saving it any of those times 6. pkill evolution (which I guess killed the calendar and address book processes), launch Evolution again, my 3 previous attempts at adding the EWS account showed up (with unrelated connection errors) Maybe something in the evolution-ews package could be added to kill/restart/notify these processes in some way to avoid extra work for a new user? [mmoldva@office ~]$ ps -fe | grep evolu mmoldva 2139 1826 0 Dec19 ? 00:00:00 /usr/libexec/evolution-source-registry mmoldva 2393 1826 0 Dec19 ? 00:00:00 /usr/libexec/evolution-calendar-factory mmoldva 2441 2393 0 Dec19 ? 00:00:00 /usr/libexec/evolution-calendar-factory-subprocess --factory contacts --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2393x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2393/2 mmoldva 2489 2393 0 Dec19 ? 00:00:00 /usr/libexec/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2393x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2393/3 mmoldva 2490 1826 0 Dec19 ? 00:00:00 /usr/libexec/evolution-addressbook-factory mmoldva 2522 2490 0 Dec19 ? 00:00:00 /usr/libexec/evolution-addressbook-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2490x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2490/2 mmoldva 31230 1826 0 09:41 pts/0 00:00:00 /usr/libexec/evolution/evolution-alarm-notify mmoldva 32232 30903 0 09:50 pts/0 00:00:00 grep --color=auto evolu [mmoldva@office ~]$ sudo pkill evolution [mmoldva@office ~]$ ps -fe | grep evolu mmoldva 32263 30903 0 09:50 pts/0 00:00:00 grep --color=auto evolu That's inside the evolution-source-registry, which should (in 3.22.x for sure) load the added modules and start working. The calendar and addressbook factories are different, I think, but maybe not. It's a long time since I made those changes. I'll retest here and will let you know. Okay, you are right. The code were checking only for newly created files and moved-in files, but not for renamed files, where the package manager copies the file under a different name first, then renames it to the right name, which the code ignored. I changed it for the next releases: Created commit 664cfac in eds master (3.23.4+) [1] Created commit 71d6c78 in eds gnome-3-22 (3.22.4+) [2] [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=664cfac [2] https://git.gnome.org/browse/evolution-data-server/commit/?id=71d6c78 Awesome, thanks for the quick turn around! |