Google Calendar ics support

Thanks for your bug. It lacks details to be useful though:
- what version of Ubuntu do you use
- do you use a webcal or import a localy stored ics file?
- "it cannot get in touch with it on the web", that doesn't look like an evolution problem if google calendar is offline, what do you mean exactly by it? "cannot resolve hostname" might a problem on your network
- do you have an example of such calendar we would try?

On 12/7/06, Sebastien Bacher <email address hidden> wrote:
> Thanks for your bug. It lacks details to be useful though:
> - what version of Ubuntu do you use

edgy eft - fully updated, bug appeared even before i install automatix2

> - do you use a webcal or import a localy stored ics file?

google calendar's online generated ics (adress example given below)

> - "it cannot get in touch with it on the web", that doesn't look like an evolution problem if google calendar is offline, what do you mean exactly by it? "cannot resolve hostname" might a problem on your network

nah, actuallly i can access the network and all, everything is fine to
that respect except for evolution unable to access the web stored
calendar. (firefox fine and all ports open in adsl router) moreover, i
had the issue on 3 different networks (my own, girlfriend's, and
school network)

> - do you have an example of such calendar we would try?

apparently any google calendar gives this problem but not the first
time... try this one.
http://www.google.com/calendar/ical/alberic.atama%40gmail.com/public/basic.ics

I'll be glad to help go further by giving more precise info. actually
the whole set of google calendars I use suffer from this problem.

I suppose this has to do with the protocol (webcal://) automatically
set by evolution. hope I may be of help.

--
Albéric CORNIERE
Please ask more if needed

I also have the same problem with Evolution not properly synching with my google calendar and have found other reportings of the same problem on the web.

Can you add links to those problems (preferrably links to bugs upstream (bugs.gnome.org) or something on gnome mailing lists) - I wasn't successful search there. Does evolution print anything in the console, if you start it from there?

I think this was missclassified as a bug. It seems to be working ok. I am
still getting an error but the calendar events are now showing up. To get
it working I used the private instead of public google calendar link
location and I will be sure to pass this solution along to other forums
reporting this as a problem. Thank you for your help.

On 12/20/06, Daniel Holbach <<email address hidden> > wrote:
>
> Can you add links to those problems (preferrably links to bugs upstream
> (bugs.gnome.org) or something on gnome mailing lists) - I wasn't
> successful search there. Does evolution print anything in the console,
> if you start it from there?
>
> --
> Google Calendar ics support
> https://launchpad.net/bugs/74070
>

indeed, the events show, but you may notice that the events you update
via the web interface of google calendar are not modified accordingly
in Evolution, thus proving the sync is not working. At least not
perfectly...

On 12/21/06, cadavg <email address hidden> wrote:
> I think this was missclassified as a bug. It seems to be working ok. I am
> still getting an error but the calendar events are now showing up. To get
> it working I used the private instead of public google calendar link
> location and I will be sure to pass this solution along to other forums
> reporting this as a problem. Thank you for your help.
>
> On 12/20/06, Daniel Holbach <<email address hidden> > wrote:
> >
> > Can you add links to those problems (preferrably links to bugs upstream
> > (bugs.gnome.org) or something on gnome mailing lists) - I wasn't
> > successful search there. Does evolution print anything in the console,
> > if you start it from there?
> >
> > --
> > Google Calendar ics support
> > https://launchpad.net/bugs/74070
> >
>
> --
> Google Calendar ics support
> https://launchpad.net/bugs/74070
>

--
Albéric CORNIERE

I am having the exact same issue on ubuntu edgy (fully updated)... evolution 2.8.1.

Here's how you should be able to recreate the error:
(1) Start evolution,
(2) Switch to the calendar window.
(3) Create a "New Calendar", with these options... Type:"On the Web", check "Copy calendar contents locally", URL: "webcal://<email address hidden>/public/basic.ics"
(This is US National Holidays public Calendar).
(4) On clicking "Ok", the calendar will work fine... even on terminating and restarting evolution, the calendar works fine.
(5) Now reboot your system and then restart evolution... switching to the calendar window should give you an error like this: "Error on webcal://www.google.com/... cannot resolve hostname."

I get six such error messages, one for each web calendar I am "subscribed" to.

I guess the one thing that's common between the 6 calendars is that they are all google calendars... so it would be good to check if this happens with non-google web calendars as well.

Here's another observation... I initially subscribed to 4 web calendars... and all 4 worked fine until I rebooted the system. Then I came to my home network (from work), and I got 4 error messages -- one for each calendar. Then I subscribed to 2 more calendars... and those worked fine. I kept getting only 4 error messages as long as I restarted evolution (without rebooting or logging off). But as soon as I rebooted the system, and started evolution (and switched to the calendar window), I got six error messages this time (still my home network).

Any insights will be appreciated.

Thanks!

-- Sid.

A brief followup:

I ran evolution from the console... nothing relevant was printed to the console.

-- Sid.

Yet another followup...

I have a second machine which runs Fedora Core 6, with evolution 2.8.2.1.

I tried to recreate this error on that machine. I *do not* get the error on that system. So, it is possible that this is fixed in the CVS, and the next release (hopefully).

-- Sid.

I also have this problem on Edgy.
Importing a calendar from Google Calendar (using the private ics address) usually works (but sometimes throws an "cannot resolve hostname" error) but it does not sync. Or, it has synced once, but that is all. And I don't get error messages.

This has been the case for evolution for a little bit now. I'm not sure if the problem exists with Google or Evolution. Can anyone get it working consistently in another iCal program?

I have the same problem on a fully updated feisty with the new 2.9.91 evolution.

I think it's this upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=364422

Same problem on a fully up to date Feisty install. I'm trying to sync to a Google Calendar (private, although this bug repeats itself with public ones too).

I'm having the same problem with ics from www.rememberthemilk.com. When I add add the calendar I get "cannot resolve hostname". I'm using evolution 2.10.1 on Feisty Fawn fully updated.

I'm also having this same issue on Feisty, fully updated, Evolution 2.10.1. When I run the program I get this on command line:

rtw@resolute:~$ evolution
CalDAV Eplugin starting up ...

(evolution-2.10:7604): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one

(evolution-2.10:7604): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution-2.10:7604): DEBUG: mailto URL command: evolution %s
** (evolution-2.10:7604): DEBUG: mailto URL program: evolution
(evolution-2.10:7604): e-data-server-DEBUG: Loading categories from "/home/rtw/.evolution/categories.xml"
(evolution-2.10:7604): e-data-server-DEBUG: Loaded 29 categories
calendar selection changed
calendar selection changed
calendar selection changed
calendar selection changed
calendar selection changed
calendar-gui-Message: Check if default client matches (1177143262.14896.3@resolute 1186434866.7604.0@resolute)
calendar selection changed
calendar selection changed
calendar selection changed
calendar selection changed
calendar selection changed
calendar selection changed

Don't think that'll be much help, but maybe it will be.

The "cannot resolve hostname" bug seems to be fixed in the latest Gutsy update. Can anyone else confirm this?

I am experiencing the same problem. I use Google Calendar, and Evolution keeps changing my "http://" to "webcal://", making it impossible to Evolution to fetch any changes I make online on Google Calendar's website.

My system is Feisty Fawn, fully updated.

That seems to be the expected behaviour, actually. Are you getting any errors as other users have mentioned above?

Yes, I get this "Error in webcall://...." "Cannot resolve hostname". One for each different calendar.

to me it all looks like evolution connects via webcal protocol but
maybe for some reason google only responds to http protocol ? has that
been tried already, or am I saying something stupid ?

On 10/7/07, Fernán González <email address hidden> wrote:
> Yes, I get this "Error in webcall://...." "Cannot resolve hostname". One
> for each different calendar.
>
> --
> Google Calendar ics support
> https://bugs.launchpad.net/bugs/74070
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Albéric CORNIERE

I was also having this problem on Gutsy, but I believe I have found the issue and a workaround. I use a laptop, and when I log in the network connection is not established. However, if I understand how Evolution works, the evolution-data-server process is already started and appears to be retaining the unconfigured network state.

If you open up a terminal and do an evolution --force-shutdown, then restart evolution while you have a network connection established, Evolution seems to be able to get to the calendars after that.

Ben Romer's suggestion worked for me. To insure that network manager starts before evolution, I used System->Preferences->Sessions under the Current Sessions tab to change the order for nm-applet to 45, and then saved the current session (under the Session Options tab, click Remember currently running applications). Evolution now consistently displays my google calendar with no error messages.

It works, thanks Steven.

I had also the problem that new entries to my google-calendar never showed up in evolution.
Ben Romer's tip worked for me too. But shouldn't the evolution-data-server process check the network-state, e.g. through listening to dbus?

I followed the instructions above (on Gutsy Gibbon) and it didn't seem to help at first. What did help was deleting an icon between webcal:// and www. Also making absolutely sure that http:// was deleted in the address when loading further calendars.

no workaround described here changes evolution's behavior for me in any way. my network connection is permanently up and has a static IP address.

do you still get the issue in hardy or intrepid?

Sorry, but at this point I'm not sure if I was using the workaround
(changing the start order of nm-applet) in hardy or not.

I'm now running intrepid (stock, no workarounds) and I'm not seeing any
problems at all.

Thanks,

Steve
--

do you still get the issue in hardy or intrepid?

** Changed in: evolution (Ubuntu)
       Status: Confirmed => Triaged

--
Google Calendar ics support
https://bugs.launchpad.net/bugs/74070
You received this bug notification because you are a direct subscriber
of the bug.

Status in The Evolution Mail & Calendaring Tool: New
Status in “evolution” source package in Ubuntu: Triaged

Bug description:
I use a Google calendar, and it cannot get in touch with it on the web. It was at least once, though, since I get an old version of it (stored locally) but for now it goes "cannot resolve hostname"

does someone now how to help with this ? I think it might be a problem with evolution trying to go webcal:// , so I'd like to try http:// , but i don't have a clue about where to change that...

I think this bug can be closed.

Google calendar is available in Evolution by adding a new Calendar of type "Google".

I disagree. I am still having issues with Evolution and Google Calendar even when using the "Google" option in Evolution. I tried all the work arounds above, and it is still not working for me.

Change status to Fix Released (see gnome-bugs)