Closed
Bug 125800
Opened 24 years ago
Closed 24 years ago
"there was a problem printing. no printer could be found
Categories
(Core :: Printing: Output, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: tracy, Assigned: rods)
References
()
Details
(Keywords: smoketest)
Attachments
(1 file)
|
1.09 KB,
patch
|
Details | Diff | Splinter Review |
I can't print with the latest linux build: 2002-02-15-13-trunk (comm.)
on clicking print I get a message saying "There was a problem printing. No
printer could be found"
4.7x works fine on same machine.
this is a smoketest blocker
Comment 1•24 years ago
|
||
Do you build yourself ?
If yes, please update the "configure" script, we added a build flag to disable
the build of the postscript module on demand.
Check whether the |MOZ_ENABLE_POSTSCRIPT| symbol is set in config/autoconf.mk :
-- snip --
cat config/autoconf.mk | fgrep "MOZ_ENABLE_POSTSCRIPT"
-- snip --
It should return "MOZ_ENABLE_POSTSCRIPT=1".
If not the postscript module won't be build...
Roland, can you back out your fix until you figure out how to get that working ?
Comment 4•24 years ago
|
||
Did you get that OK'd with Rod.. this should have been cleared with Rod and
myself so we could head off this kind of problem. Why do we have that
flag..when linux is very dependent on that module?
Comment 5•24 years ago
|
||
Rods ok'd the changes from bug 80625 . I missed the missing AC_SUBST when I
reviewed the configure changes. This patch should fix that problem. (run
autoconf after applying)
Comment 6•24 years ago
|
||
Comment on attachment 69757 [details] [diff] [review]
propogate MOZ_ENABLE_POSTSCRIPT to Makefiles
r=Roland.Mainz@informatik.med.uni-giessen.de
Comment 7•24 years ago
|
||
The patch has been checked in.
Comment 8•24 years ago
|
||
Marking fixed so Tracy/Sujay can verify.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 9•24 years ago
|
||
can anyone verify that this patch fixes the problem?
Comment 10•24 years ago
|
||
dcone wrote:
> Why do we have that flag..when linux is very dependent on that module?
Remember - we have the Xprint print module, too. The idea behind the
--disable-postscript build flag is that we do not need the PostScript module
when we can use Xprint module (this is an optional flag for platforms which ship
with the server side of Xprint ("Xprt") by default (that are Solaris>=2.7 and
HP-UX), we're building both modules by default) ...
Comment 11•24 years ago
|
||
*** Bug 126222 has been marked as a duplicate of this bug. ***
| Reporter | ||
Comment 12•24 years ago
|
||
verified with commercial linux build 2002-02-18-06-trunk
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•