Re: [Evolution] Evo Seg Fault on Meeting Request

2010-07-06 Thread Philippe LeCavalier
On Tue, 2010-07-06 at 11:15 +0530, Akhil Laddha wrote: On Fri, 2010-07-02 at 15:26 -0400, Philippe LeCavalier wrote: On Fri, 2010-07-02 at 15:15 -0400, Adam Tauno Williams wrote: Does Google support use CALDAV or something else? I have no idea. If it uses CALDAV setting the

Re: [Evolution] Evo Seg Fault on Meeting Request

2010-07-06 Thread Philippe LeCavalier
On Tue, 2010-07-06 at 09:35 -0400, Philippe LeCavalier wrote: On Tue, 2010-07-06 at 11:15 +0530, Akhil Laddha wrote: On Fri, 2010-07-02 at 15:26 -0400, Philippe LeCavalier wrote: On Fri, 2010-07-02 at 15:15 -0400, Adam Tauno Williams wrote: Does Google support use CALDAV or

Re: [Evolution] Evo Seg Fault on Meeting Request

2010-07-05 Thread Akhil Laddha
On Fri, 2010-07-02 at 15:26 -0400, Philippe LeCavalier wrote: On Fri, 2010-07-02 at 15:15 -0400, Adam Tauno Williams wrote: Does Google support use CALDAV or something else? I have no idea. If it uses CALDAV setting the CALDAV_DEBUG variable might expose something. I'm 90% certain it's

[Evolution] Evo Seg Fault on Meeting Request

2010-07-02 Thread Philippe LeCavalier
Hi, I use Google Calendars to coordinate with various ppl including clients and as of late, when I click on the invite Evo seg faults. I ran Evo from console and all I get is segmentation fault. What else can I do to provide more info? Phil ___

Re: [Evolution] Evo Seg Fault on Meeting Request

2010-07-02 Thread Adam Tauno Williams
On Fri, 2010-07-02 at 14:06 -0400, Philippe LeCavalier wrote: I use Google Calendars to coordinate with various ppl including clients and as of late, when I click on the invite Evo seg faults. I ran Evo from console and all I get is segmentation fault. What else can I do to provide more info?

Re: [Evolution] Evo Seg Fault on Meeting Request

2010-07-02 Thread Philippe LeCavalier
On Fri, 2010-07-02 at 15:15 -0400, Adam Tauno Williams wrote: Does Google support use CALDAV or something else? I have no idea. If it uses CALDAV setting the CALDAV_DEBUG variable might expose something. I'm 90% certain it's CALDAV however... Run CALDAV_DEBUG=1 evolution Shows: