Bug 223039

Summary:	YaST2 printer does not offer freshly added printers for "new queue for existing printer"
Product:	[openSUSE] openSUSE 10.2	Reporter:	Christian Boltz <suse-beta>
Component:	Printing	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Johannes Meixner <jsmeix>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log one mor y2log "Printer Configuration" screen "New queue for existing printer" screen

Description Christian Boltz 2006-11-21 19:51:48 UTC

YaST2 printer does not offer freshly added printers for "new queue for existing printer".

How to reproduce:
- make sure you have _no_ printers configured (in my casee because of
  bug 223037)
- start YaST2 - printer
- add a printer (in my case: a HP DJ 710C on a remote CUPS server)
- choose "new queue for existing printer" ("Neue Warteschlange für bestehenden
  Drucker")

Expected result: you can clone the queue of the freshly configured DJ 710 printer

Actual result: you can (only) clone the queue "unknown"

Workaround: Save and exit after adding the DJ 710 printer, then restart the printer module. Now you can create a new queue for the existing printer.


The y2logs are available in attachment 106452 [details] of bug 223037.

Comment 1 Michal Zugec 2006-11-22 10:02:32 UTC

Couldn't reproduce - it works for me with raw ipp
If you use remote CUPS - was it client only (first option)?

Comment 2 Christian Boltz 2006-11-22 11:47:22 UTC

I used add - network printer - print on CUPS network server ("Drucken über CUPS-Netzwerkserver) - remote IPP queue ("Entfernte IPP-Warteschlange")

Another thing: I accidently used the "new queue for existing printer" (which offered only "unknown" of course) before finding this bug. Not sure if it is related ;-)

Comment 3 Johannes Meixner 2006-11-22 13:28:34 UTC

Michal,
as far as I see it does not depend on the connection type.
I could reproduce it with a new quque for a parallel port printer.
"Cloning" this new queue via "new queue for existing printer"
in the same YaST run leads to wrong results.
In my case I got a wrong PPD file for the cloned queue.
The PPD file for the queue from which I made the clone is
"Alps MD-1000, Foomatic + md2k (Japanese version, needs cupsomatic)"
but the clone got
"Generic postscript printer"

Comment 4 Johannes Meixner 2006-11-22 13:31:05 UTC

Created attachment 106569 [details]
y2log

y2log for my test above

Comment 5 Johannes Meixner 2006-11-22 13:33:34 UTC

I got the same wrong PPD file for another clone even after I finished
and re-started yast2 printer.

Comment 6 Johannes Meixner 2006-11-22 13:34:53 UTC

Created attachment 106572 [details]
one mor y2log

y2log for my second cloning test (after yast2 printer restart).

Comment 7 Johannes Meixner 2006-11-23 11:00:34 UTC

There is one more problem:

After clicking [Add] and selecting "New queue for existing printer" the
"New queue for existing printer" screen shows only as many entries
as there are different model names (i.e. what is shown in the "Model"
column on the "Printer Configuration" screen).

This leads to problems if there are more than one queue for the same model.

The "New queue for existing printer" screen must show all available queues
(i.e. te same as on the "Printer Configuration" screen) and then
YaST must clone all info from the selected queue to be the
defaults for the new queue (except the queue name).

Comment 8 Johannes Meixner 2006-11-23 11:03:58 UTC

Created attachment 106685 [details]
"Printer Configuration" screen

"Printer Configuration" screen for comment #7

Comment 9 Johannes Meixner 2006-11-23 11:04:29 UTC

Created attachment 106686 [details]
"New queue for existing printer" screen

"New queue for existing printer" screen for comment #7

Comment 10 Johannes Meixner 2006-11-23 11:15:09 UTC

Why does the "New queue for existing printer" screen exist at all?

Shouldn't it also work when the user selects a queue on the
"Printer Configuration" screen and then after clicking [Add]
and selecting "New queue for existing printer" YaST could
use the previously selected queue to be cloned.

Comment 11 Michal Zugec 2007-02-19 12:48:20 UTC

duplicate and fixed
now the printers are identifying by DeviceUri and not by ModelName

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