Bug 60678 - printconf-gui / printconf-tui doesn't create printer queue nor printcap
Summary: printconf-gui / printconf-tui doesn't create printer queue nor printcap
Status: CLOSED DUPLICATE of bug 59481
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: printconf
Version: 7.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-03-04 18:25 UTC by Need Real Name
Modified: 2007-04-18 16:40 UTC (History)
0 users

Clone Of:
Last Closed: 2002-03-04 19:48:39 UTC

Attachments (Terms of Use)

Description Need Real Name 2002-03-04 18:25:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.0.2 (X11; Linux i686; U;) Gecko/20011226

Description of problem:
There's a problem with the latest version of printconf.
After having installed all the latest updates, the printconf tool doesn't create
printing queues nor /etc/printcap file.
The only thing that works is creating a RAW queue.
It really is a printconf problem since editing /etc/printcap by hand or
configuring a printer with printtool works.
Here's a listing of some rpms installed on my system:

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

How reproducible:

Steps to Reproduce:
1. Upgrade all packages with up2date or any other tool
2. Launch printconf (gui or tui)
3. Create a new entry with any driver

Actual Results:  No error message, the entry is not created in /var/spool/pld
and the /etc/printcap is not updated (and sometimes it even delete all the other

Expected Results:  New printer queue created

Additional info:

Comment 1 Tim Waugh 2002-03-04 18:28:45 UTC
Do you have mpage installed, and if not does installing it fix the problem?

Comment 2 Need Real Name 2002-03-04 19:48:32 UTC
With mpage installed, it does work !
I think it should be added to the printconf rpm depency.
Thank you, at last my problem's solve...

Comment 3 Tim Waugh 2002-03-04 20:40:27 UTC

*** This bug has been marked as a duplicate of 59481 ***

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