Re: Mozilla/Firefox "PostScript/default" security problems
Michael B Allen(mba2000@ioplex.com) is reported to have said:
> On Tue, 6 Jul 2004 20:52:37 -0400
> Wayne Topa <brittman@capital.net> wrote:
> > I am also running firefox 0.8 but it was installed with apt-get. I am
> > stuck with Xprint with no postscript/default. :-(
>
> Try it. Just run the Xprint daemon (/etc/init.d/xprint start?), find out
> what display it's running on by looking at ps -fax (say it's ":2") and then
> add export XPRTSERVERLIST=":2" to your environment (and log out and in if
> necessary to reinit the env). Start mozilla and see if your printers
> exported by CUPS (or whatever your lpq reports) is listed in the printer
> dialog. Printing through xprint is considerably nicer.
Sorry, I didn't mention that I have Xprint working, I just don't like
it! I had, before the Moz change, 3 different print entries working
in printcap. Now only 2 work and not the way they used to. I'm stuck
with 300 DPI, whis is OK for general use, but have lost the ability to
use 600 DPI when I need to.
I also loaded the Mozilla browser and find that the printer works
differently in it then it does in Firefox. Entries that work in
firefox don't work in moz and vice versa.
All in all the printer does work, but, why anyone would want to
disable postscript printing when it was working fine for most users.
I haven't read the bugreport that caused this but it is a bit scary
when one person has a problem and it is fixed, for him, and causes so
many others to scramble to get printing working. Have not seen this
happen before in many many years with Debian.
Wayne
--
It works! Now if only I could remember what I did...
_______________________________________________________
Reply to: