On Tue, Mar 09, 2010 at 07:46:48PM +1000, p...@pjb.com.au wrote:
Greetings Jonas, thanks for your prompt answer.

Yeah, I appreciate that myself - especially when initially posting a bugreport. Unfortunately too often I don't get around to responding until ages later (if at all) :-(


What command did you invoke that lead to above error?

 /usr/bin/gv
and then "o" for open and do the file-dialogue thing. Or:
 /usr/bin/gv ~/www/muscript/samples/courante.pdf
gives the same error :-(

But on the other hand:
 /usr/bin/gs ~/www/muscript/samples/courante.pdf
displays the page perfectly :-)

So gs works, but gv fails (though when gv reports the error,
it reports it as a GPL Ghostscript error...)

Ah.  gv works for me too.


Do you perhaps have something odd below /usr/local which
confuses ghostscript?

Well /usr/local/lib seems like it's ahead of /usr/lib,

That sounds like a possible cause, then.


also, I moved /usr/local/lib and /usr/local/bin aside and re-ran
ldconfig, and gs still worked, but gv still failed (though when
gv reports the error, it reports it as a Ghostscript error...)

Ghostscript also pulls data files from */usr/share.

Try put aside /usr/local completely!

And I wonder how all those binaries ended below /usr/lib - could it be that you've compiled a bunch of different stuff by hand and installed it as root? If so, I suspect that some install routines might accidentally have installed stuff below /usr too, and you do not really run a Debian system any longer :-(

Not certain, though. A way forward could perhaps be to use strace to check which files are being touch prior to the crash. But that's beyond me, so can't really help there.


 - Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

Reply via email to