Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 160827 - redhat-config-printer crashed after detecting numeric printer queue name
redhat-config-printer crashed after detecting numeric printer queue name
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: redhat-config-printer (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2005-06-17 13:56 EDT by George Liu
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-20 06:07:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description George Liu 2005-06-17 13:56:41 EDT
Description of problem: 
Used CUPS web GUI to create a printer queue named 2232.  
Start redhat-config-printer, and redhat-config-printer will crash.  
Version-Release number of selected component (if applicable): 
How reproducible: 
Steps to Reproduce: 
1.Use cups webgui to create a printer named 2232  
2.start redhat-config-printer  
3.redhat-config-printer will crash.  
Actual results: 
Expected results: 
Additional info:
Comment 1 Tim Waugh 2005-06-20 06:00:11 EDT
FWIW, the code that imports CUPS-created queues into the redhat-config-printer
configuration database has been removed since Red Hat Enterprise Linux 4, so
future releases should not be affected.
Comment 2 Tim Waugh 2005-06-20 06:07:52 EDT
You cannot in general create a queue in CUPS and be able to edit it correctly
using redhat-config-printer.  It is better, if you intend to use
redhat-config-printer, to create the queue there in the first instance. 
Alternatively, you can use the CUPS web interface exclusively.

Since this work-around is available, I am closing this bug as WONTFIX.

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