Bug 100425 – USB lpx port description

Bug 100425 - USB lpx port description

Summary:	USB lpx port description

Status:	CLOSED DUPLICATE of bug 81164

Aliases:	None

Product:	Red Hat Linux Beta
Classification:	Retired
Component:	redhat-config-printer (Show other bugs)
Sub Component:
Version:	beta1
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Tim Waugh
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-07-22 05:44 EDT by Kevin Arima
Modified:	2007-04-18 12:55 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:57:39 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 Kevin Arima 2003-07-22 05:44:38 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When there are more than one USB-based printer attached to a system, there is 
no way to determine which /dev/usb/lpx port a device is attached to, without 
trial and error.

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

How reproducible:
Always

Steps to Reproduce:
1. Connect more than one USB-based printer to a system.
2. Start the Printer Setup to setup a printer
3. Try to determine which /dev/usb/lpx port each printer is connected to.
    

Expected Results:  There should be a description showing the model number of 
the USB printer (or the print server) next to the port to make it easier to 
determine which printer is which.

Additional info:

Comment 1 Tim Waugh 2003-07-22 05:54:53 EDT


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

Comment 2 Red Hat Bugzilla 2006-02-21 13:57:39 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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