gnucash crashes on open due to missing custom report

[Jeff Hinrichs - DM&T]

On Jan 6, 2008 4:58 PM, Andrew Sackville-West <ajswest at mindspring.com> wrote:
> On Sun, Jan 06, 2008 at 04:49:53PM -0600, Jeff Hinrichs - DM&T wrote:
> > On Jan 6, 2008 4:20 PM, Andrew Sackville-West <ajswest at mindspring.com> wrote:
> > > /me tries to veer this collision  into useful discussion...
> > >
> > > On Sun, Jan 06, 2008 at 10:50:43AM -0500, Derek Atkins wrote:
> > > > Hi,
> > > >
> > > > Quoting Jeff Hinrichs - DM&T <jeffh at dundeemt.com>:
> > > >
> > > > > I just encountered the following situation and want to know if I
> > > > > should file a bug?
> > > >
> > > > no...
> > >
> > > this bug already exists in bugzilla.
> > >
> > > >
> > > > > 1) create a custom report, save it, close gnucash **with the report open**
> > > > > 2) edit saved-reports-2.0 and remove the custom report definition
> > > > > 3) start gnucash and watch it die
> > >
> ...
> > > I'll fix this up and commit shortly.
> > >
>
> >
> > cool.  Thanks!
>
> note though that it will just drop an open report for which there no
> longer is a saved (or system) report. I'll probably stick in a warning
> dialog, I guess, but the report itself will just vanish.
>
> A
That would be a justifiable course, since the report is no longer
defined.  The warning/info is also a plus to not let the condition go
by silently.

-Jeff
"Errors should never pass silently",  zen of python
...