RE: California-0.1.2 Segfault

[Jim Nelson <jim yorba org>]

The segfault you sent in a separate email is occurring inside of libical, the standard library for decoding iCalendar data.  libical is being called by libecal-1.2, which is the Evolution Data Server calendaring library, which is the back-end for California:

#0 0x00007ffff20165c1 in ?? () from /lib/libc.so.6

#1 0x00007ffff6061c1f in ?? () from /usr/local/lib/libical.so.1

#2 0x00007ffff6063955 in icaltimezone_get_utc_timezone () from /usr/local/lib/libical.so.1

#3 0x00007ffff62b0877 in ?? () from /usr/local/lib/libecal-1.2.so.16

#4 0x00007ffff286583e in g_type_create_instance () from /usr/local/lib/libgobject-2.0.so.0

#5 0x00007ffff286a750 in ?? () from /usr/local/lib/libgobject-2.0.so.0

#6 0x00007ffff286ab61 in g_object_new_valist () from /usr/local/lib/libgobject-2.0.so.0

#7 0x00007ffff286af09 in g_object_new () from /usr/local/lib/libgobject-2.0.so.0

#8 0x00007ffff62aeabc in e_cal_client_connect () from /usr/local/lib/libecal-1.2.so.16

#9 0x00000000005352bb in california_backing_eds_calendar_source_open_async_co (_data_=0xa01910)

    at /home/jim/git/california/src/backing/eds/backing-eds-calendar-source.vala:105

The root cause appears to be in libc.  Without debug symbols installed, there's no way to know what exactly libc is doing here or what symbol in libc was called.  I would suggest installing debug symbols for all of the above libraries.

None of this is due to California, at least directly.  California is merely attempting to open EDS.  Since this is initialization, libical is probably attempting to initialize itself.  In particular, it loads timezone information from a zone.tab.  There are a couple of compile-time options for determining where libical should look for that information.  You'll need to consult the libical source and READMEs for more details.

California also uses D-Bus to fetch timezone information from timedated, but that's not the issue here.

-- Jim

On Tue, Jul 22, 2014 at 12:24 AM, John Frankish <j-frankish slb com> wrote:

-----Original Message----- From: John Frankish Sent: Monday, 21 July, 2014 10:05 To: 'california-list gnome org' Subject: California-0.1.2 Segfault California-0.1.2 segfaults when trying to start - is this because it's looking for systemd, which is not present on my system? Regards John

In fact California works OK on a different machine that I thought was set-up identically (neither have systemd). What exactly is California looking for in terms of locale and timezone? Regards John _______________________________________________ california-list mailing list california-list gnome org https://mail.gnome.org/mailman/listinfo/california-list