11-21-04 10:49 PM
Greetings!
I thought I may have a ghostscript error/bug, but it now occurs to me
it may be something else...
(I'm running RedHat Linux 7.1, although I've upgraded, on my own,
numerous things. For example, I'm using the 2.4.17 kernel.)
I have a Users Guide for the HP 9110 printer in a .pdf file, and I've
attempted to print this. From my own account (barry), I can type "gs
HPUserGuide.ps" and see it on the screen, and I am able to press <RETURN>
enough times to display successfully all the way through the file.
However, when I try to print it, gs runs in the "lp" account. When I
su into lp and run "gs HPUserGuide.ps" (the same file), I get an error:
sh-2.04$ gs HPUserGuide.ps
GNU Ghostscript 7.07 (2003-05-17)
Copyright (C) 2003 artofcode LLC, Benicia, CA. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Error: /invalidfileaccess in --.libfile--
Operand stack:
(/home/barry/NOTES/HPUserGuide.ps)
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval
-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval--
false 1 %stopped_push --nostringval-- 1 3 %oparray_pop --no
stringval-- --nostring
val-- --nostringval--
Dictionary stack:
--dict:1057/1123(ro)(G)-- --dict:0/20(G)-- --dict:68/200(L)--
Current allocation mode is local
Last OS error: 13
GNU Ghostscript 7.07: Unrecoverable error, exit code 1
It occurs to me there may be library/environment variable or similar
file that is in my own account, but not in lp's. However, when I set
GS_LIB and LD_LIBRARY_PATH to just about every /lib directory I can find,
including what is in my own (barry) account as well as others (in
/etc/profile, so that when I "su - lp" into lp, those environment
variables are set), I still get exactly the same error.
Do you have any suggestions on what I should try next?
Thank you!
Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
bbond@cfl.rr.com <- personal | (My personal home web page, last
Phone: 407-382-2815 | updated July 21, 2004)
|
[ Post a follow-up to this message ]
|