just FYI, CAMEL_DEBUG=all is only for debugging the mailer at a protocol level (e.g. imap, pop, smtp, etc) and not meant for general debug output for all components of evolution
Jeff On Fri, 2005-07-29 at 12:23 -0700, Greg Tassone wrote: > More debug info below: > > On Fri, 2005-07-29 at 11:58 -0700, Greg Tassone wrote: > > I've "force-shutdown" on all Evo processes and rebooted to no effect. > > I've checked the local store and the files appear to have all the data > > within them. For some reason Evo just can't display them. No > > significant errors are being output in the normal stdout/stderr that I > > can find. > > After trying "CAMEL_DEBUG=all evolution", these are the only errors that > I receive when trying to access the Calendar: > ---------------------------- > > (evolution:9002): libecal-CRITICAL **: file e-cal.c: line 1944 > (e_cal_is_read_only): assertion `ecal && E_IS_CAL (ecal)' failed > > (evolution:9002): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > > (evolution:9002): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > > ---------------------------- > > > I wanted to see if anyone had any clues here in the list before posting > a bug report, but let me know if I should go straight there. > > Thanks. > > > _______________________________________________ > evolution maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/evolution > -- Jeffrey Stedfast Evolution Hacker - Novell, Inc. [EMAIL PROTECTED] - www.novell.com _______________________________________________ evolution maillist - [email protected] http://lists.ximian.com/mailman/listinfo/evolution
