Bug 1420 – printer setup fails

Bug 1420 - printer setup fails

Summary:	printer setup fails

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	linuxconf (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-03-04 09:08 EST by rblach
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-03-22 18:47:30 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description rblach 1999-03-04 09:08:38 EST

When I try to configure a printer without samba and ncpfs,
the printer setup icon fails to come up.  This is very
frustrating since I do not either of these.

Comment 1 Bill Nottingham 1999-03-08 14:08:59 EST

do you get an error message or stack trace?

What happens when you run printtool from the command line?

Comment 2 rblach 1999-03-09 04:34:59 EST

H'mmm.  Here were the exact set of circumstances.
I had just finished upgrading from 5.1 to 5.2.  As an additional
printer, I have the hp 710 installed with the package from
//www.rpi.edu/~normat/technical/ppa/  (GREAT SOFTWARE).
When I went to the printtool to add printer and the samba error box
appeared.   There were no printers displayed in the  tool,
even though there was a printcap file.   Every time I hit ok to the
samba error responce, the netware printer warning appeared.   After
hitting ok the second time, the warning dissapeared and so did the
printtool

I had to delete queues by hand and readd them by the printtool.

I cant get it to fail now.  It must have been an upgrade problem.

Chip

Comment 3 rblach 1999-03-09 20:03:59 EST

No, unfortunately did NOT get an error trace and I cant make it fail
again.  This is as frustrating as the initial failure.

Comment 4 Bill Nottingham 1999-03-22 18:47:59 EST

if you can replicate this, re-open the bug.

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