segfaults when running graphical reports
janssens-geert at telenet.be
Thu Apr 24 08:14:23 EDT 2014
Thank you for digging deeper into this issue.
I hadn't been following this thread in detail but the attached patch
caught my (maintainer's) attention.
Personally I'm not too fond of adding this workaround into gnucash. Your
conversation with the readline upstream indicates this is not an issue
that originates in gnucash.
The way I understand your message is that GnuCash receives a SIGTTOU
signal and halts. It receives this signal because it wants to write to
standard output while being backgrounded.
Some googling got me to this page:
The answer explains that SIGTTOU is emitted depending on the settings of
the current terminal.
You can test this for your terminal with the command
and check if tostop is set.
I could reproduce his halt by running
in my bash session on Fedora 20 (which uses readline 6.2). In my case it
did halt when "Finance::Quote" was displayed in the splash screen.
Did your upgrade to gnucash 2.6.3 happen around the same time of a zsh
On Monday 21 April 2014 23:38:47 Thomas Klausner wrote:
> On Sun, Apr 13, 2014 at 09:35:11AM +0200, Thomas Klausner wrote:
> > The first: If I start gnucash without a terminal or in the
> > background, it doesn't finish startup. When started in the
> > background, I see (with>
> > zsh):
> > > gnucash &
> >  7303
> >  + suspended (tty output) gnucash
> > When I put it in the foreground again, it continues starting
> > successfully. This seems to happen during the splash screen, the
> > last
> > thing that's displayed in the progress text at the bottom is
> > "gnucash/python". Perhaps this is a problem with a python module,
> > but
> > how do I find out which?
> I contacted the readline upstream about it, and while they didn't find
> anything they saw as changed on their side (i.e., readline behaviour
> has always been this way), they pointed me in the direction of a
> simple fix: just ignoring the SIGTTOU signal.
> Using the attached patch makes gnucash start in the background again.
> Even if for some reason noone else has had this problem yet, I hope
> it's uncontroversial enough to be accepted?
More information about the gnucash-devel