Bug 50611

Summary: strange phantom printer definitions
Product: [Retired] Red Hat Linux Reporter: Gene Czarcinski <gczarcinski>
Component: printconfAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-08-01 21:28:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
printconf-0.3.0-5 with two "phantom" entries1
none
settings.xml
none
settings.xml none

Description Gene Czarcinski 2001-08-01 16:14:54 UTC 
Description of Problem:
Define a remote unix lpd printer.
After deleting this printer, I tried to (re)define a printer with the name
"lp" -- would not "finish" and text message in the terminal window said
that "lp" alread exists.

Restarted printconf-gui and noticed a "strange" entry labeled "lp" but with
Queue Type "INVALID" and Details "Invalid Printer Record".

More attempts to define a printer produced some additional "Invalid Printer
Record" entries.

These records cannot be selected/deleted.

/etc/printcap shows nothing and /var/spool/lpd has nothing.

How Reproducible:


Steps to Reproduce:
1. Define "lp"
2. Delete "lp"
3. "define "lp"

Actual Results:
garbage

Expected Results:
valid entry

Additional Information:
Comment 1 Gene Czarcinski 2001-08-01 17:07:07 UTC 
OK, this is not happening with printconf-0.3.6 from rawhide for NEW definitions
but I do I get rrid of the existing phantoms whithout blowing away this system.
Comment 2 Gene Czarcinski 2001-08-01 17:22:09 UTC 
OK, the nature of this bug has changes.  I discovered printconf-tui and it does
see and can delete the phantom (INVALID Queue type records).  The problem is
that the gui interface cannot.
Comment 3 Crutcher Dunnavant 2001-08-01 20:28:15 UTC 
can you do the following for me?

printconf-tui --Xexport > printer-settings.xml

and then attach printer-settings.xml to this bug? Thanks.
Comment 4 Glen Foster 2001-08-01 20:29:43 UTC 
This defect is considered MUST-FIX for Fairfax
Comment 5 Gene Czarcinski 2001-08-01 21:26:09 UTC 
Created attachment 25893 [details]
printconf-0.3.0-5 with two "phantom" entries1
Comment 6 Gene Czarcinski 2001-08-01 21:27:56 UTC 
After creating the attachment, I was able to back with printconf-tui and delete
a bad entry but printconf-gui does not let me do this.
Comment 7 Crutcher Dunnavant 2001-08-02 02:09:01 UTC 
hoho.

Well, I apparently didnt want people to try to edit invalid printer entries, so
I /explicitly/ made them unselectable. Which of course means you can not delete
them.

fixed. Thanks for spotting this one.
Comment 8 Crutcher Dunnavant 2001-08-02 02:12:13 UTC 
btw, to fix your existing system, use the following attachement, and do:

printconf-tui --Ximport < settings.xml
Comment 9 Crutcher Dunnavant 2001-08-02 02:19:40 UTC 
Created attachment 25932 [details]
settings.xml
Comment 10 Crutcher Dunnavant 2001-08-02 02:20:47 UTC 
Created attachment 25933 [details]
settings.xml