Can you tell me what kind of non-Google calendars you're loading?  (Is it Exchange, for example?)

No... There are NO non google calendars. I only have google calendars for now. They work in Evolution and gnome-shell (the little calendar in the top bar). California lists them in the calendar list, but they show up empty.

I just pushed a change that improves the debug log a bit by listing which property is causing the error.  Can you pull latest master and tell me what it prints now?

I picked up the most recent daily build from launchpad, but no noticeable change - unless I'm missing something... One thing to note may be the fact that I'm not in a US timezone - I'm in Europe...

You should see a slightly different debug message in the log -- it should list what property was being accessed when the error occurred.  Can you copy-and-paste that here?

** (california:9821): DEBUG: calendar-system.vala:135: Local zone: Europe/Paris
(california:9821): Gtk-DEBUG: Connecting to session manager
** (california:9821): DEBUG: backing-store.vala:33: EDS Source Registry: added Birthdays & Anniversaries
** (california:9821): DEBUG: backing-eds-store.vala:138: Unable to open Calendar: Unable to connect to 'Calendar': Cannot open calendar: Failed to obtain an access token for 'Calendar': GDBus.Error:org.gnome.OnlineAccounts.Error.NotAuthorized: No credentials found in the keyring
** (california:9821): DEBUG: backing-store.vala:33: EDS Source Registry: added HD Temp
** (california:9821): DEBUG: backing-store.vala:33: EDS Source Registry: added IFI
** (california:9821): DEBUG: backing-store.vala:33: EDS Source Registry: added Personal
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE
** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE

----------------------------------------------

** (california:9821): DEBUG: backing-eds-calendar-source-subscription.vala:166: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_DURATION_VALUE

---------------------------------------

the debug message repeats... presumably for every event it finds...

I couldn't find an actual log file, this is just the console output.

Hope it helps though.

Since nothing has been posted since, am I to assume that this information is useless? 
/var/log/messages doesn't contain anything  and as I said, there's no log anywhere (that I found). 
The same text is in the console now even though I've picked up later versions...

No, the information is useful, I'm just quite busy at the moment and stumped why this is happening.

iCalendar has a DTSTAMP field that is supposed to be in a DATE-TIME format.  For some reason, all of yours are in a DURATION format (i.e. "30 minutes" instead of "2:30pm, 30 July 2014").  That's a problem.

There's this in your log too:

backing-eds-store.vala:138: Unable to open
Calendar: Unable to connect to 'Calendar': Cannot open calendar: Failed to
obtain an access token for 'Calendar':
GDBus.Error:org.gnome.OnlineAccounts.Error.NotAuthorized: No credentials found
in the keyring

This might be the root of the problem.  It looks like the credentials (username/password) for your primary Calendar are not stored in your system.  California's error handling is not robust right now, so it's merely logging this problem for now.

I would be curious if you opened Evolution what happened.  It might query you for a username and password.  If not, right-click on the Calendar in the Evolution sidebar and choose Refresh.  Then try right-click -> Properties.

The key here is to force Evolution to store your username and password.  Then try reloading California and see if that corrects the problem.

Sorry for the delay, I'm away for a couple of weeks... Evolution doesn't ask for a password. The first google calendar is handled by Gnome online accounts. Evolution picks it up automatically... I can refresh it "sort of"... Sometimes it doesn't actually refresh unless I restart evolution data server, but that's a different issue. The point is probably that evolution gets the calendar/credentials from GOA. And doesn't keep them... I can try to doable the calendar and re-add it as a user calendar from within Evolution if you think that would help, but I can't get rid of the original unless I delete the gmail account from Gnome.

Now this sounds like a completely different problem, with storing credentials.  One thing that comes to mind: have you added the same calendar twice?  Another user reported a few problems due to this.  For example, if you have Google Calendar available through GNOME Online Accounts, then Evolution will add it.  It looks like you can still manually add that Google Calendar to Evolution and it will appear as a separate calendar.  This can cause a lot of confusion.

I'm experiencing the same problem.

Running G_MESSAGES_DEBUG=all california shows:

---

G_MESSAGES_DEBUG=all california
** (california:18127): DEBUG: calendar-system.vala:174: Local zone: Europe/Paris
** (california:18127): DEBUG: calendar-system.vala:245: Date ordering: DMY, separator: / (formatted=03/04/2001)
** (california:18127): DEBUG: calendar-system.vala:250: Using _NL_TIME_FIRST_WEEKDAY for system first of week
** (california:18127): DEBUG: calendar-system.vala:301: System first day of week: lundi

** (california:18127): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(california:18127): Gtk-DEBUG: Connecting to session manager
** (california:18127): DEBUG: backing-store.vala:33: EDS Source Registry: added Dates de naissance et anniversaires
** (california:18127): DEBUG: backing-store.vala:33: EDS Source Registry: added Personnel

(california:18127): GLib-GObject-WARNING **: The property GtkMisc:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): GLib-GObject-WARNING **: The property GtkMisc:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(california:18127): GLib-GObject-WARNING **: The property GtkWidget:margin-left is deprecated and shouldn't be used anymore. It will be removed in a future version.

(california:18127): GLib-GObject-WARNING **: The property GtkWidget:margin-right is deprecated and shouldn't be used anymore. It will be removed in a future version.

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: /build/gtk+3.0-NeOhpP/gtk+3.0-3.13.9/./gtk/gtkwidget.c:8537: widget not within a GtkWindow

(california:18127): Gtk-WARNING **: Symbolic icon edit-symbolic-ltr is not in an icon theme directory
(california:18127): libgdata-DEBUG: XML content type detected.
(california:18127): libgdata-DEBUG: XML content type detected.
(california:18127): libgdata-DEBUG: Unhandled XML in GDataCalendarCalendar: <gd:where valueString=""/>
** (california:18127): DEBUG: google-calendar-list-pane.vala:171: Subscribing to https://www.google.com/calendar/dav/myaccount%40gmail.com/events
** (california:18127): DEBUG: backing-store.vala:33: EDS Source Registry: added myaccount@gmail.com
** (california:18127): DEBUG: backing-eds-calendar-source-subscription.vala:190: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_TRIGGER_VALUE


---
 The last output (subscription.vala:190)repeats many times.

I cleared the .config/evolution/sources/ directory before I did that and added my google account.
Nothing appears in California but when I add an event with California it appears in my Google calendar.
My google accounts used to show up in California, but I don't know in which release.


I hope it helps.

This is even stranger.  iCal is reporting DTSTAMP as an alarm trigger value.  Something fundamental is amiss here.

Two things.  First, can you see your events in Evolution?

Second, I've added some additional debugging to master.  In your case, it will most likely spit out a lot of text.  You might want to redirect to a file.

If you could pull master, rebuild, and either post that debug here or (since it might contain personal information) send it to jim@yorba.org, that would help a lot.

I often add a reminder (alarm) to my events for my mobile.

I can see the events in Evolution.

I sent you the new debug output from last master build.

jc.sid, this helps and doesn't help in some ways.  Looking at the debug output your events look perfectly normal (in other words, DTSTAMP is a date/time, like it should be, and not a trigger value).  This means something is really wrong here, like corrupt data structures or something.

What version of libical are you using?  I believe there's only one version (1.0), but I need to check.

$ pkg-config --modversion libical

I've added a little more debugging to California for this issue.  It would help me if you could run it again as before and send me the debug output to jim@yorba.org.

Hi,

libical is libical1 1.0-1

I sent you the last California debug

ok... sorry I've been away from bugzilla. The original problem seems to have disappeared in the 0.1.4 release - or something else in opensuse fixed it... 
I haven't tested everything, but I can now see my calendars properly...
I'll test more and post if I have similar reminder problems to JC.

Thanks

*** Bug 739342 has been marked as a duplicate of this bug. ***

*** Bug 739570 has been marked as a duplicate of this bug. ***

Horde is serving my calendar (CALdav). Have been using California since 4 months or so without problem. This occured since last update to 0.2.

Tim, if you run California from the console:

$ G_MESSAGES_DEBUG=all california

do you see the error messages reported earlier, or something different?

*** Bug 739738 has been marked as a duplicate of this bug. ***

With every event i get the following error.

** (california:1883): DEBUG: backing-eds-calendar-source-subscription.vala:190: Unable to process added event: ICAL_DTSTAMP_PROPERTY not a DATE/DATE-TIME value: ICAL_X_VALUE (DTSTAMP:20141124T234604Z)

I've pushed a candidate fix for this problem to master: commit fadd2c.  I would appreciate it if people seeing this problem could pull the latest and try it out.  (It should be on our Daily Build PPA within the next 24 hours.)

If it doesn't work, as before, a log file would be helpful.

It's solved for me with the last master build with the Archlinux AUR package california-git.

I can confirm events are shown again for commit fadd2c0

All right.  Thanks to everyone for your patience.  I'm going to close this for now.  If people continue to see the problem, please re-open.