Re: [Denemo-devel] Chord symbols / dead lilypond processes

[Richard Shann]

On Sun, 2013-05-05 at 09:03 +0100, Richard Shann wrote:
> On Sun, 2013-05-05 at 08:51 +0200, Andreas Schneider wrote:
> > Am 04.05.2013 21:05, schrieb Richard Shann:
> > > On Sat, 2013-05-04 at 20:34 +0200, Andreas Schneider wrote:
> > >> It seems that when I use the chord staff, denemo (current git version)
> > >> accumulates dead lilypond processes. Here is the output from "ps afx" on
> > >> my Debian Linux system after I added some notes and chords in the
> > >> IndependentChordSymbols example:
> > > 
> > > Is this happening if you take an empty score and just enter some notes?
> > > Is LilyPond succeeding in typesetting what you have entered?
> > 
> > According to my test, this is also happening if I take an empty score
> > and enter some notes (I didn't notice that before). The print preview
> > shows the correctly typeset score, which means that lilypond must succeed.
> 
> Ah - I see this too. The defunct lilypond processes all exit when you
> exit denemo. Can some Unix expert comment on what could be going wrong?
> We are getting the process-finished callback (which is what triggers the
> display of the pdf that lilypond has generated) we are using
> g_child_watch_add() for that.

I see the problem - the call to lilypond to get the installed lilypond
version is using g_spawn_async but not waiting for the process, it is
just working by accident and leaving the zombie. I have disabled this as
we are moving to packaging lilypond with denemo anyway. But we are
currently hardwiring the version in print.c where it should be given by
the gub build system.
Fixed in git.
Richard