If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Can not print without root access.

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
15 years ago
15 years ago

People

(Reporter: Jan D., Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4b) Gecko/20030517 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4b) Gecko/20030517 Mozilla Firebird/0.6

To get printing to work one has to have root access to install the Xprint stuff.
 This is a major regression from all previous netscape and mozilla versions that
did not require this.  This makes it very hard to evaluate new versions.

Reproducible: Always

Steps to Reproduce:
1. Install phoenix
2. Try to print something.
3. Error message appears saying Xprint server not running.


Actual Results:  
Error message appears saying Xprint server not running.

Expected Results:  
Printed the page.

Comment 1

15 years ago
you do not require root permission to use xprint
where do you get that false information from?
you can fetch the solaris binary tarball release from
http://puck.informatik.med.uni-giessen.de/download/xprint-2003-05-08-release_008-sparc-sun-solaris2.7.tar.gz
unpack the content into any location and follow the instructions in the readme
(Reporter)

Comment 2

15 years ago
The information is from the GISWxprint* packages.  The xprint pages gives the
impression that this is what is needed for Solaris.  If I am wrong, that is good
news :-)

Comment 3

15 years ago
Jan, did the hint given in comment #1 helped you with your problem? If so I'd
suggest resolving this one "invalid"! Thanks a lot.
(Reporter)

Comment 4

15 years ago
Yes it did, just tried it, thanks.  Suggest improving this piint on the xprint
web page though.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.