Re: [Evolution] (no subject)

[Dinbandhu <dinbandhu sprynet com>]

-----Original Message-----
> From: Patrick O'Callaghan <poc usb ve>
> Sent: Apr 29, 2009 11:09 AM
> To: Dinbandhu <dinbandhu sprynet com>
> Cc: evolution-list gnome org
> Subject: Re: [Evolution]
>
> On Wed, 2009-04-29 at 10:05 -0400, Dinbandhu wrote:
> > Patrick,
> >
> > -----Original Message-----
> > > From: Patrick O'Callaghan <poc usb ve>
> > > Sent: Apr 29, 2009 9:43 AM
> > > To: evolution-list gnome org
> > > Subject: Re: [Evolution] "MigrateEvolutionToNewComputer" did not work
> > >
> > > On Wed, 2009-04-29 at 00:35 -0400, Dinbandhu wrote:
> > > > So all the above I did, and Evolution is not opening on the new
> > > > computer. I should also state that Evolution was never used or opened
> > > > on the new computer prior to transferring over the above directories.
> > > > What went wrong, and what do I need to do to get Evo to open???
> > >
> > > Run Evo from a command line and see what the messages say.
> >
> > Here is the output:
> >
> > swarup ubuntu:~$ evolution
> >
> > (evolution:27765): camel-WARNING **: camel_exception_get_id called with NULL parameter.
> >
> > GLib-ERROR **: /build/buildd/glib2.0-2.18.2/glib/gmem.c:136: failed to allocate 31740376080 bytes
> > aborting...
> > Aborted
>
> Looks like a bug (that's a ridiculously large number to be allocating).
> You need to report this to Bugzilla (http://bugzilla.gnome.org). Post
> the BZ number here so other people can add to it if they want.

But if the procedure works on other computers, then why would we think there is a bug involved? i.e. if it 
were something systemic, then wouldn't we expect many people to be affected? This OS is 8.10, and so quite 
established. I am not using Jaunty.  Could it be something that happens when one tries to move from a 32bit 
to a 64bit system?

Thanks,
Swarup