Bug 50588 - printconf-gui random screen
Summary: printconf-gui random screen
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: printconf   
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-01 13:30 UTC by Tim Waugh
Modified: 2007-04-18 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-01 16:45:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Tim Waugh 2001-08-01 13:30:53 UTC
Description of Problem:
While adding a local printer, I get a screen 'Configure a Unix Print
Queue', asking me for the server and queue names.  It's a local printer!

Also, it says 'label158' at the top.

The same thing happens with 'Configure a Windows Print Queue'.  And it says
'label170' at the top.

And with 'Configure a Novell Print Queue', and it says 'stuff' at the top.

And finally, with 'Select a Print Driver', there is nothing to select from.
 And it says 'label164' at the top.

Comment 1 Gene Czarcinski 2001-08-01 16:45:46 UTC
I also tried this for local printer definition and simply kept "next"ing through
the screens but not filling in anything until I got the the "printers" panel
where I needed to select a printer type from a list BUT ... surprise, no list!

Comment 2 Crutcher Dunnavant 2001-08-01 20:20:58 UTC
something tracebacked at the begining of the handler, and then you lost pythons
control, leaving you free to move arround in the widget without it doing
anything smart. I wish tracebacks in gtk were fatal, grr.

Anyway, fixed.

Comment 3 Glen Foster 2001-08-01 20:30:25 UTC
This defect is considered MUST-FIX for Fairfax


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