Re: [Denemo-devel] Mac print issues

[Richard Shann]

On Thu, 2013-04-25 at 15:12 -0500, Jeremiah Benham wrote:
> On Apr 24, 2013 10:56 AM, "Richard Shann" <address@hidden>
> wrote:
> >
> > On Wed, 2013-04-24 at 14:24 +0000, Jeremiah Benham wrote:
> > > On 4/24/13, Richard Shann <address@hidden> wrote:
> > > > On Wed, 2013-04-24 at 07:27 -0500, Jeremiah Benham wrote:
> > > >> On Wed, Apr 24, 2013 at 08:25:23AM +0100, Richard Shann wrote:
> > > >> > On Wed, 2013-04-24 at 00:05 -0500, Jeremiah Benham wrote:
> > > >> > > On Tue, Apr 23, 2013 at 04:33:10PM +0100, Richard Shann
> wrote:
> > > >> > > > On Tue, 2013-04-23 at 09:01 -0500, Jeremiah Benham wrote:
> > > >> > > > > I don't know why this is only effecting the Mac build
> of denemo...
> > > >> > > > > Something seems to be getting out of sync. Denemo is
> finding and
> > > >> > > > > executing lilypond correcty and evince is loading pdf's
> correctly.
> > > >> > > > > What I see is that if I hit ctrl-p p,
> > > >> > > > Have you got continuous typesetting turned on? (If you
> delete the
> > > >> > > > print
> > > >> > > > view window it will be off, but set Continuous to manual
> anyway).
> > > >> > > >
> > > >> > >
> > > >> > > I set it to manual but it still did not work. It was not
> until I
> > > >> > > closed the window of the pop-up
> > > >> >
> > > >> > What pop-up are you referring to?
> > > >> >
> > > >> > If the score-check script finds a problem it pops up a dialog
> asking if
> > > >> > you want to try and print anyway. Is it that?
> > > >>
> > > >> No, Its the progressbar pop-up.
> > > >
> > > > Well, dismissing that aborts the waiting for the LilyPond
> process to
> > > > signal it has finished IIRC. Do you have top or some other tool
> for
> > > > looking at what the processes are doing?
> > >
> > > Ok. I ran it using ctrl-p p to get the printview. The top program
> is
> > > the bsd top (I believe) so it is a little different. Here is what
> it
> > > says:
> > >
> > > PID  COMMAND      %CPU      TIME     #TH  #WQ  #POR #MRE RPRVT
>  RSHRD
> > > RSIZE  VPRVT  VSIZE  PGRP PPID STATE    UID  FAULTS  COW   MSGSENT
> > > 197- lilypond     0.0       00:03.39 1    0    19   425  42M
>  50M
> > > 52M    101M   756M   181  191  sleeping 501  13585   798   740
> > >
> > > So that means that lilypond is idle but has not exited properly.
> Is
> > > this then a lilypond bug? Now I closed the progressbar pop-up and
> I
> > > see in the printview what I was trying to "print". Maybe I should
> try
> > > a different version of lilypond 2.17.x or something. It currently
> has
> > > 2.16.2. Perhaps it was the upgrade from 2.13 that caused this.
> >
> > Are you using LilyPond from the Denemo installation or one from a
> > LilyPond installer or one that is installed from your distribution?
> 
> I have tried gubs 2.16.2, 2.16.0, 2.13 and the official lilypond
> 2.16.2. Nothing seems to work. When I kill lilypond at the command
> line or I close the progressbar window then it opens up the pdf in the
> printview. I think the problem is in print.c somewhere because if I
> export to pdf everything works as expected. 

??? Do you get the pop saying your PDF is now ready? That is, do you see
LilyPond exiting in top when you invoke it for Export to PDF but not
exiting when you do print preview?
This popup is the equivalent of the progress bar exiting.

If you *are* getting the "Your pdf file has now been created" message
then:
in that case the call to launch LilyPond needs to be looked at: all
calls to generate a PDF file via LilyPond (except the thumbnail which is
hopefully not involved here) are done via the single call run_lilypond()
so, it would be worthwhile printing out the exact arguments and other
relevant information as it is called. And, of course, checking that the
g_child_watch_add has been correctly called for the pid in question.

Richard