Bug 113302

Summary: printer [Add] workflow incomplete
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Johannes Meixner <jsmeix>
Component: PrintingAssignee: Michal Zugec <mzugec>
Status: RESOLVED FIXED QA Contact: Johannes Meixner <jsmeix>
Severity: Major    
Priority: P5 - None CC: afernandez, forgotten_QtBI7gWTIh, frederik.vos, gerry, jsmeix, kontakt, silviu_marin-caea, uwe.fischer
Version: Beta 3   
Target Milestone: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log

Description Johannes Meixner 2005-08-26 13:07:31 UTC
Using newest /work/CDs/all/full-i386/suse/i586/yast2-printer.rpm
on nelson.suse.de

In "Printer Configuration" main menue using [Add] leads to a
popup question for which I don't understand the meaning:

Warning: Do you want to configure new queue? [Yes] [No]

What is the meaning of this?

Regardless whether I click [Queue Yes] or [No] the workflow is
"Printer Type" ... "Queue Name"
but then on the "Queue Name" screen the [Next] button does nothing.
I.e. here I am stuck (regardless which "Printer Type" I have selected).
Comment 1 Johannes Meixner 2005-08-26 13:19:09 UTC
Sorry for causing confusion.
When I answer [Yes] to configure a new queue
I get an additional queue for the selected printer.

The workflow stops at the "Queue Name" screen when I answer
[No] to configure a new queue.

This makes no sense for me because I do want to set up a
new queue but not for one of the autodetected printes
but for another printer (e.g. for a network printer which
cannot be autodetected).
Comment 2 Johannes Meixner 2005-08-26 13:21:06 UTC
Created attachment 47773 [details]
y2log

y2log when I answered [No] and then
clicked always [Next] until the dead
end at the "Queue Name" screen.
There I cklicked [Next] twice.
Comment 3 Michal Zugec 2005-09-02 10:24:38 UTC
fixed for rc1
Comment 4 Michal Zugec 2005-09-06 11:46:54 UTC
*** Bug 115393 has been marked as a duplicate of this bug. ***
Comment 5 Michal Zugec 2005-09-06 12:51:15 UTC
*** Bug 115043 has been marked as a duplicate of this bug. ***
Comment 6 Michal Zugec 2005-09-06 13:38:23 UTC
*** Bug 114955 has been marked as a duplicate of this bug. ***
Comment 7 Michal Zugec 2005-09-07 09:14:07 UTC
*** Bug 115507 has been marked as a duplicate of this bug. ***
Comment 8 Michal Zugec 2005-09-07 10:56:25 UTC
*** Bug 115569 has been marked as a duplicate of this bug. ***
Comment 9 Johannes Meixner 2005-09-08 06:42:37 UTC
*** Bug 115763 has been marked as a duplicate of this bug. ***
Comment 10 Johannes Meixner 2005-09-14 14:27:56 UTC
*** Bug 116972 has been marked as a duplicate of this bug. ***
Comment 11 Michal Zugec 2005-09-16 10:37:55 UTC
*** Bug 117291 has been marked as a duplicate of this bug. ***