GNOME Bugzilla – Bug 343782
Evolution consumes all CPU cycles to display webcal URI warning
Last modified: 2006-08-02 07:23:37 UTC
Please describe the problem: Quite some time ago, I experimented with publishing a calendar. I do not remember what version of Evolution I was using. Now, any time I open Evolution, it consumes all available CPU cycles to output the following message to the console: ** (evolution-2.6:8412): WARNING **: Could not form the uri for webcal://example.com/not/the/real/address/ical/test.ical The preferences for calendar publishing do not show any publishing configured. Steps to reproduce: I do not know exactly how to reproduce the problem, but it's probably something like this: 1. Install an older version (I do not know which version) of Evolution. 2. Set up callendar publishing using webdav. 3. Upgrade to this version of Evolution. Actual results: Evolution starts consuming all available CPU cycles shortly after launch, and outputs ** (evolution-2.6:8412): WARNING **: Could not form the uri for webcal://example.com/not/the/real/address/ical/test.ical to the console many times every second. Expected results: I expect Evolution to launch, use a fraction of a percent of the available CPU cycles and not print warning messages to the console. Does this happen every time? Yes. Other information: I'm running Debian/Sid and I keep it fairly up to date. I think my initial experiment with calendar publishing was about a year ago. This problem started recently - about two weeks ago, I think.
Hi Zak, I guess something went wrong when saving the calendar with the older version. I've just tried this on Ubuntu Dapper and it works as expected (notices you the destination is unreachable and keeps going). What you could do is open up gconf-editor (apt-get install gconf-editor) and take a look at: /apps/evolution/calendar/sources You might erase (if there are) any traces of the bad calendar source and eventually post it here. Let me know, if it help anyhow. thanks
> What you could do is open up gconf-editor (apt-get install gconf-editor) > and take a look at: > /apps/evolution/calendar/sources > > You might erase (if there are) any traces of the bad calendar source and > eventually post it here. Let me know, if it help anyhow. Thanks for the tip - I didn't even think to try gconf-editor, though I did grep for parts of the bad URI in ~/.evolution/. There was nothing in the key you posted, but I did find and remove the URI it was complaining about from /apps/evolution/calendar/publish/uris The console messages stopped, but it still used all available CPU cycles. Next, I removed the evolution-webcal package, and CPU usage went back to normal. The evolution-webcal package was NOT installed when I first noticed the problem; I installed it before reporting this bug to see if it would fix the problem. So the workaround appears to be: delete the contents of /apps/evolution/calendar/publish/uris and uninstall evolution-webcal. This works for me since I don't need webcal.
*** This bug has been marked as a duplicate of 343991 ***