GNOME Bugzilla – Bug 666038
Two Problems with the Google Calendar
Last modified: 2012-08-06 15:17:46 UTC
Problem #1: I use the Google Calendar in Evolution since a few months (already with GNOME 2.30). However, I always have had two parallel Google Calendars in Evolution and now I can't add a new appointment to one of these calendars: When I want to save the calendar, I'll get the messagebox "Kalenderobjekt kann nicht angelegt werden: Not loaded" (engl.: "cannot create calendar object: not loaded"). Problem #2: However, the second calendar (at the same time!) started to have a strange behaviour too: When I click on "save" after filling out the form for a new appointment, nothing will happen. I have to click the "save" button multiple times. Afterwards I get the message "Ereignis kann nicht gespeichert werden. »« ist ein schreibgeschützter Kalender. Wechseln Sie zur Kalenderansicht und wählen Sie einen Kalender aus, der Termine akzeptieren kann." (engl.: cannot save since calandar is write-protected. please choose another non-write-protected calendar instead."). However, the calendar is *not* write-protected and never was. Evolution even displays the saved appointment after I clicked away the error message. Summary: I now have two broken Google Calendars in Evolution. Each of them is broken on it's own way. It never made problems with the old 2.x evolution ... However, my "personal calendar" (the local one) works fine but that is not what I need.
PS. Problem #1 also occurs when I add the CalDav entry by hand instead of choosing a "Google Calendar". In both cases, I can see all existing appointments but can't add new ones.
Restarted Evolution about 10 times (no success for the problems). Just ran evolution --debug=log.txt. Everything worked. I have no idea, why. Logfile log.txt is empty. Now, Evolution needs ages to exit, have to run evolution --force-shutdown that finally seems to send SIGKILL since Evolution does not respond.
Thanks for a bug report. Is this still applicable, please? Also, what is your exact evolution version, please? I suggest to try with version 3.2.3, which is the most up-to-date in 3.2 development branch. I do not recall any similar bug report, there are some about google calendars, but not about this issue. It seems like the calendar is opening too slowly for you. Any google calendar uses CalDAV at the background, which makes it almost the same whether you use Google group or CalDAV group (calendar type). If it's still applicable, then I would try to run e-calendar-factory process with CalDAV debugging, to see what server returns and possibly what is going wrong. You can do it with steps like these: a) close evolution and any other evolution-related processes, like evolution-alarm-notification, e-calendar-factory, e-addressbook-factory b) run a terminal window where you'll start the e-calendar-factory: $ CALDAV_DEBUG=all /usr/libexec/e-calendar-factory -k Note the path can be different for your Linux distribution. c) run evolution from another terminal d) move to Calendar view and choose one of your Google calendars There should be some new output on the e-calendar-factory console (it can alternatively write the output already, when the Calendar view realizes it requires the calendar data). Maybe it'll be better to remove all your google calendars first, and create a new one when you'll have the factory running with debugging turned on.
cdp_doomed, can you please provide requested information as per comment#3 ?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!