Re: [Evolution] calendar won't load after upgrade

[John Stile <john stilen com>]

On Sat, 2011-06-18 at 16:01 +0100, Pete Biggs wrote:
> On Fri, 2011-06-17 at 08:34 -0700, John Stile wrote:
> > After my last gentoo update (gnome-2.32.1 updated)
> > when I launch evolution everything is fine, and I can see email and
> > contacts, yet when I click on the calendar, I get errors.
> > ~/.xsession-errors shows:
>
> It looks like you have a problem with either dbus or e-calendar-factory
> - are they running on your system?
Yes, dbus and e-addressbook-factory are running.

Since I don't get an error with a new calender makes me think the
problem is with my calender file.

I tried starting e-calendar-factory in debug mode an then load my
calender, but didn't show anything useful from what I can see:

gdb /usr/libexec/e-calendar-factory --ex r --ex "t a a bt" --ex c --ex q 
                                    
GDB OUTPUT:
GNU gdb (Gentoo 7.2 p1) 7.2 
Copyright (C) 2010 Free Software Foundation, Inc. 
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html> 
This is free software: you are free to change and redistribute it. 
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying" 
and "show warranty" for details. 
This GDB was configured as "i686-pc-linux-gnu". 
For bug reporting instructions, please see: 
<http://bugs.gentoo.org/>... 
Reading symbols from /usr/libexec/e-calendar-factory...(no debugging
symbols found)...done. 
Starting program: /usr/libexec/e-calendar-factory 
[Thread debugging using libthread_db enabled] 
e-data-server-Message: adding type `ECalBackendContactsEventsFactory' 
e-data-server-Message: adding type `ECalBackendFileJournalFactory' 
e-data-server-Message: adding type `ECalBackendFileEventsFactory' 
e-data-server-Message: adding type `ECalBackendFileTodosFactory' 
e-data-server-Message: adding type `ECalBackendWeatherEventsFactory' 
e-data-server-Message: adding type `ECalBackendGroupwiseJournalFactory' 
e-data-server-Message: adding type `ECalBackendGroupwiseEventsFactory' 
e-data-server-Message: adding type `ECalBackendGroupwiseTodosFactory' 
e-data-server-Message: adding type `ECalBackendCalDAVMemosFactory' 
e-data-server-Message: adding type `ECalBackendCalDAVTodosFactory' 
e-data-server-Message: adding type `ECalBackendCalDAVEventsFactory' 
e-data-server-Message: adding type `ECalBackendExchangeTodosFactory' 
e-data-server-Message: adding type `ECalBackendExchangeEventsFactory' 
e-data-server-Message: adding type `ECalBackendHttpMemosFactory' 
e-data-server-Message: adding type `ECalBackendHttpEventsFactory' 
e-data-server-Message: adding type `ECalBackendHttpTodosFactory' 
[New Thread 0xb2bb8b70 (LWP 26115)] 
[New Thread 0xb21ffb70 (LWP 26116)] 
Server is up and running... 

Program received signal SIGSEGV, Segmentation fault. 
0xb7b5ce6b in ?? () from /lib/libc.so.6 

Thread 3 (Thread 0xb21ffb70 (LWP 26116)): 
#0  0xb7fe1424 in __kernel_vsyscall () 
#1  0xb7ca2274 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
from /lib/libpthread.so.0 
#2  0xb7cb2f46 in ?? () from /usr/lib/libgthread-2.0.so.0 
#3  0x0006c2d5 in ?? () 
#4  0x00000002 in ?? () 
#5  0x08096ad0 in ?? () 
Backtrace stopped: previous frame inner to this frame (corrupt stack?) 

Thread 2 (Thread 0xb2bb8b70 (LWP 26115)): 
#0  0xb7fe1424 in __kernel_vsyscall () 
#1  0xb7b0bbac in poll () from /lib/libc.so.6 
#2  0xb7bed3fc in g_poll () from /usr/lib/libglib-2.0.so.0 
#3  0x00000003 in ?? () 
#4  0xffffffff in ?? () 
#5  0xb7c95ff4 in ?? () from /usr/lib/libglib-2.0.so.0 
Backtrace stopped: previous frame inner to this frame (corrupt stack?) 

Thread 1 (Thread 0xb32cf850 (LWP 26112)): 
#0  0xb7b5ce6b in ?? () from /lib/libc.so.6 
#1  0xb607a964 in icaltimezone_get_builtin_timezone_from_tzid ()
from /usr/lib/libical.so.0 
#2  0xbfffc6c0 in ?? () 
Backtrace stopped: previous frame inner to this frame (corrupt stack?) 
---Type <return> to continue, or q <return> to quit--- 
Continuing. 
[Thread 0xb2bb8b70 (LWP 26115) exited] 
[Thread 0xb21ffb70 (LWP 26116) exited] 

Program terminated with signal SIGSEGV, Segmentation fault. 
The program no longer exists.