Hide Forgot
I have a google account configured by gnome-online-accounts. In evolution I only use it for tasks and calendar. If I've had the wifi disabled at work and suspend/resume and forgot to turn the wifi on evolution will prompt for passwords (even if it's not running) on resume, the password is correct but it doesn't seem to detect that the reason the service can't authenticate is because there is no network available for it to do so. evolution-ews-3.4.1-1.fc17.x86_64 evolution-3.4.1-1.fc17.x86_64 evolution-NetworkManager-3.4.1-1.fc17.x86_64 evolution-mapi-3.4.0-1.fc17.x86_64 evolution-help-3.4.1-1.fc17.noarch evolution-data-server-3.4.1-1.fc17.x86_64 gnome-online-accounts-3.4.1-1.fc17.x86_64
Interesting, do they support their Tasks over CalDAV now? I thought they have it still disabled and provide only events. I'll investigate on the incorrect password prompt and let you know.
One of the libgdata bugs I follow mention they now do allow it but I'm not sure that it does or whether that's just what the dialog said, or maybe I just read it wrong.
I see. Their bug [1] is accepted, but still opened. I thought I just missed it being finally fixed. [1] http://code.google.com/p/google-caldav-issues/issues/detail?id=36
Hrm, I'm unable to reproduce the password prompt, though I'm not entirely doing the same thing, because I'm only playing either with connection as such, or with vpn connection (which is harder to spot by network manager), but it still doesn't ask me for the password. I'm afraid this will be something with the suspend, having it suspended in the middle of some operation, because if I try to Refresh the calendar while network manager is only connecting to my WiFi access point, then I receive "Host not reachable" for www.google.com, but as an error, not as the password prompt. It reminded me, the password prompt can contain also a reason, why it asks for the password. It's at the very end. Do you recall whether your password prompt had there any reason or not, and if yes, what it was? I'll move it upstream with this information, the code doesn't differ in Fedora from the upstream code.
I think it might be the gnome-shell calendar widget making something start on login if there's no network connection available. Basically I was turning off wifi in the office as there's issues with WPA-Enterprise and it kept prompting me. Arriving home and I would resume with no wifi, unlock the screen and I get this prompt before I can re-enable networking. My understanding is that NetworkManager reports "online" or "offline" states but it still prompts even in the offline state.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.