Re: [Evolution] Memo seg faults Evo

[Philippe LeCavalier <support plecavalier com>]

On Wed, 2009-12-16 at 19:24 -0600, C de-Avillez wrote:
> On 12/16/2009 07:07 PM, Philippe LeCavalier wrote:
> > Hi,
> >
> > Since I upgraded to Evo 2.28 I get a seg fault when I add a memo. Here's
> > the output when run from the command line:
> >
> > plecavalier plc:~$ evolution
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> >
> > (evolution:11140): evolution-shell-WARNING **: The name
> > org.freedesktop.NetworkManager was not provided by any .service files 
> >
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> >
> > ** (evolution:11140): CRITICAL **: atk_object_set_name: assertion
> > `name != NULL' failed
> > Segmentation fault
> > plecavalier plc:~$
> >   
> Well, the stdout/stderr output does not help much -- it would be better
> with a backtrace --, but this sounds like bug 460050 [1]. Do you have it
> applied?
>
> Cheers,
>
>
> [1] https://bugs.launchpad.net/bugs/460050
Yes, you're right. Sorry.

Cheers,
Phil