GNOME Bugzilla – Bug 691293
Claim old resources in offline mode
Last modified: 2014-11-06 13:44:33 UTC
When connecting a new account to an Exchange 2007 server, all functions operate as expected. After some time of use, the default exchange calendar disappears from view. The exchange account is not listed under Calendars. It is possible to add a new calendar, this shows up on the server as expected but it is empty. Not being able to view the default calendar is a serious issue (IMHO) as it removes part of the core functionality. If a meeting invite update is received, evolution complains that it can't find the calendar.
My 3.6.2 shows me the EWS Calendar, but I see the git master doesn't have it, thus I agree there is some flaw in the code which causes the Calendar disappear, which it should not.
Hmm, my git master Calendar is back. I tried several tests here, read the code and I see this: - The available calendars/books/memo lists/task lists are recognized within evolution-source-registry process - At its (each) start, it fetches all available folders on the server and then adds sources based on the folder type - After that a usual folder synchronization is done, which means that the source registry module asks the Exchange server only for changes since the last test This works fine as long as the source registry process got correct EWS account password. If it didn't, then no Calendar sources are shown in evolution for the EWS account. The thing is that entering password in evolution is not enough, because these two are separate processes, thus to be re-prompted for the EWS account password within source registry process one needs to restart it. Could you run the source registry process from a terminal, which will replace the current running process, with debugging on, please? It may tell us what it does for you. The command is like this: $ EWS_DEBUG=2 /usr/libexec/evolution-source-registry &>log.txt Note with the EWS_DEBUG=2 all the traffic between evolution and your exchange server is logged, thus be careful about the log. You can run the source registry process even without EWS_DEBUG=2, then the log will only show what the source registry logs about, which is useful too. I would try the command as is first too, to check whether the server returns the Calendar (just search for the word "Calendar" (quotes for clarity only) in it, and you may hit one with that DisplayName).
I have a similar issue every time I log in to GNOME. I'm not connected to the VPN yet (obviously) so evolution-source-registry *can't* talk to the EWS server. And thus I get no calendars at all until I manually kill evolution-source-registry. If it can't communicate with the server (due to bad password or other issues), it shouldn't assume that all the calendars are *gone*. It should continue to list the same ones it knew about before. Surely?
(In reply to comment #3) > If it can't communicate with the server (due to bad password or other issues), > it shouldn't assume that all the calendars are *gone*. It should continue to > list the same ones it knew about before. Surely? Yes, I agree, but it wasn't my decision, see bug #678466.
Aha, thanks. That was the bug I was looking for and couldn't find :) mbarnes?
*** Bug 687238 has been marked as a duplicate of this bug. ***
Hmm, I do not recall when I faced this issue the last time. My Calendars view shows me EWS calendars with no problem. This is with git master, but it might be pretty much the same as 3.8.5. David, Andrew, do you see this in 3.8.x too, please?
Using 3.8.5 and having changed my exchange password lateley, I can confirm that evolution (after a few "wrong password" dialogues and unsuccessful retries) didn't display the exchange default calendar anymore. Adding new calendars using evolution worked, but there was no way to re-add the default calendar. Exiting evolution and starting evolution-source-registry on command line helped - all the calendars were available again.
I still have this bug on Fedora 20 (evolution-3.10.4-4.fc20.x86_64 and evolution-ews-3.10.4-1.fc20.x86_64). When I reboot my laptop and start evolution before my network connection fully comes up, EWS calendar disappears from list of calendars along with tasks in top-bar applet. My workaround is: kill `ps ax | grep evolution | grep -v grep | awk '{print $1}'`
There were couple issues, like the source-registry's backend didn't always pay attention to the online state changes of the EBackend. Then few other issues, which I tried to address in the below change. After the change, the sources are also claimed when the account is enabled, which didn't work before. Created commit 96be82f in ews master (3.13.8+) [1] Created commit b6c9d2a in ews evolution-ews-3-12 (3.12.8+) [1] https://git.gnome.org/browse/evolution-ews/commit/?id=96be82f