My google calendar is failing to work. On debugging, I find an endless stream of > OPTIONS /calendar/dav/dwmw2%40infradead.org/events/ HTTP/1.1 > Soup-Debug-Timestamp: 1361977379 > Soup-Debug: SoupSessionSync 1 (0x2302000), SoupMessage 2 (0x7fa40c0101e0), SoupSocket 39 (0x7fa40c213210), restarted > Host: www.google.com > User-Agent: Evolution/3.6.3 > Connection: close > Authorization: Basic [dwmw2:********] < HTTP/1.1 401 Unauthorized < Soup-Debug-Timestamp: 1361977379 < Soup-Debug: SoupMessage 2 (0x7fa40c0101e0) < WWW-Authenticate: GoogleLogin realm="https://www.google.com/accounts/ClientLogin", service="cl" < Content-Type: text/html; charset=UTF-8 < Date: Wed, 27 Feb 2013 15:02:59 GMT < Expires: Wed, 27 Feb 2013 15:02:59 GMT < Cache-Control: private, max-age=0 < X-Content-Type-Options: nosniff < X-Frame-Options: SAMEORIGIN < X-XSS-Protection: 1; mode=block < Server: GSE < Connection: close < < Invalid Credentials At no point does Evolution ask me for a new password. Even if I delete all relevant passwords using seahorse, and restart evo-calendar-factory and evolution, it's still doing this same repeated request.
Killing evolution-source-factory *and* evolution-calendar-factory and restarting evolution was sufficient to make it stop, for now. There is something seriously wrong here.
The source registry is responsible for providing passwords. Why it didn't ask you, but returned an old one (probably?), I do not know, but I agree that there's something wrong. Let me try to reproduce, and then decide what to do next (by the way, this doesn't seem to be fedora specific issue, hence it might come to upstream bugzilla).
I'm moving this to libsoup, after testing it it doesn't work well with Google server (with other server it does, interestingly), and libsoup falls in some cycle not involving password prompts.
Created attachment 703884 [details] test2.c This is a minimal test program which exhibits the issue. I tried with both libsoup-2.40.3 and libsoup-2.40.1, but both are doing this wrong for some reason.
fixed in git. are people ok with CLOSED NEXTRELEASE?
I think, if you could patch the Fedora 18 version, then it'll help. When I was testing this then it was in 2.40.1 too, thus not introduced in a version I "forced" you to release :) If you think that people will move to Fedora 19 soon, then probably doesn't matter much. (In other words, it would be nice to have it fixed in Fedora 18 too, but I've no strong opinion on that myself.)
Please don't leave this unfixed in Fedora 18. I have machines I've only *just* updated from Fedora 16 to Fedora 18, and they're likely to stay that way for almost another year before F18 is EOL. Not everyone upgrades *every* machine aggressively. Although having said that, Evolution in Fedora 18 is already fairly broken with my EWS calendars disappearing due to source registry bugs, so perhaps there's an argument that if the Google one breaks at least that's consistent. /me frowns at mbarnes... :)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.