Reports in Gnucash 1.8.8 cause segmentation fault on a SuSE 9.1 Pro installation

[Linas Vepstas]

On Tue, Sep 07, 2004 at 01:18:36PM -0400, Randy Burgess was heard to remark:
> 
> GnuCash runs OK except when I try to access anything on the Reports menu 
> - in which case it crashes and brings down X with it. Looking in 
> /var/log/warn, I find only this:
> 
>    Fatal server error: Caught signal 11.  Server aborting

In principle, it should be impossible to make an x application crash
the x server.  This is a bug in the x server; just so happens that
gnucash makes it happpen.  I can only suggest trying a newer/different
x server, reporting the bug to suse (as an x bug), double checking
the device driver, disapling direct rendering and seeing if that helps,
etc.

> I've checked the hardware using the test script from 
> www.bitwizard.nl/sig11, and everything checks out OK, so I don't think 
> it's a hardware problem.

Good first step.

> conflicts ...

... gnucash has nothing to do with this bug; updating/reinstalling
gnucash or any of its libraries/deps will do nothing to make the bug 
go away (well, OK, it might by accident..but that's not the point).  
This really is an X11 Window System Server bug and/or a bug in the
graphics card device driver, and needs to be treated as such.

> Anybody have any other suggestions? Any other logs I can look at? This 

/var/log/XFree86.log


--linas

-- 
pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas at linas.org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933