Bug 97921 - printer install problems
printer install problems
Status: CLOSED CANTFIX
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-printer (Show other bugs)
9
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-06-23 23:10 EDT by Bert Smart
Modified: 2007-04-18 12:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-16 12:44:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bert Smart 2003-06-23 23:10:48 EDT
Description of problem:
Printer installation does not work

Version-Release number of selected component (if applicable):

V 9
How reproducible:

Easy
Steps to Reproduce:
1.click printer setup
2.choose any printer in list
3.apply, then try to print test page
    
Actual results:
Returns error message: There was a problem sending CUPS test page to 'printer' 
queue;
lpr:unable to print file:server-error-service-unavailable

The printer installed never appears as a icon in Gnome printer window.

Computer is new, 2gh Celeron, 256mb ddr, ECS P4VMM2 motherboard VIA chipset.
Linux V9 installed ok and loads ok, no error messages.

Expected results:
V9 was installed on a old Gateway and the printer installed with no problem at 
all.

Additional info:

The printer was tested with a boot 3 1/2 flop, w win98-2 to be sure that there 
was not a problem in the hardware, it printer perfectly.

Have been fighting this problem for over 2 weeks.
Comment 1 Tim Waugh 2003-11-05 11:40:58 EST
Component is wrong -- fixing.
Comment 2 Tim Waugh 2003-11-05 11:44:39 EST
Please attach the output of 'printconf-tui --Xexport', taking care to
replace any passwords it contains.
Comment 3 Tim Waugh 2005-09-16 12:44:12 EDT
No feedback; closing.

Note You need to log in before you can comment on or make changes to this bug.