https://bugzilla.novell.com/show_bug.cgi?id=437735 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c1 --- Comment #1 from Johannes Meixner 2008-10-23 00:13:22 MDT --- According to y2log in attachment #247150 printer_proposal.ycp is called correctly and it also runs without errors. But what I see in its source file src/printer_proposal.ycp is that no real functionality is implemented there. As far as I see it just calls Printer::Read() and Printer::Write() but this is totally insufficient to actually set up a queue. I.e. as far as I see it is just not yet implemented. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User kssingvo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c4 --- Comment #4 from Klaus Singvogel 2008-11-06 07:57:51 MST --- In beta4, when disabling automatic configuration: the printer configuration page shows an empty page, where no input is possible and is skipped after some time. I had the feeling that this function is not implemented. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c9 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #9 from Michal Zugec 2008-11-14 07:58:07 MST --- Fixed in yast2-printer-2.17.37 Klaus, it would be great if you can test the package (just contact me via IRC) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c14 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #14 from Johannes Meixner 2008-11-19 07:34:33 MST --- Tested yast2-printer 2.17.41 in the running system according to comment #8. It should work o.k. in most cases. It results multiple queue set up using the same queue name if a printer is listed more than once in the ConnectionItems list. For example currently my HP LaserJet 1220 is connected both via parallel port and via USB and is accessible as follows: ------------------------------------------------------------------ direct parallel:/dev/lp0 direct hp:/par/HP_LaserJet_1220?device=/dev/parport0 direct usb://HP/LaserJet%201220 direct hp:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX ------------------------------------------------------------------ Currently "usb://HP/..." and "hp:/usb/..." duplicates are suppressed by default in the ConnectionItems list. I must also suppress by default "parallel:/dev/lp*" and "hp:/par/" duplicates. Additionally I will use the queue_name string in src/printer_proposal.ycp to suppress duplicates: Same queue_name string for different URIs indicates a duplicate - even if then for two same printer models which are connected only one queue is set up, see Klaus' strange lsusb output in comment #0 and compare https://bugzilla.novell.com/show_bug.cgi?id=433044#c15 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c15 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #15 from Johannes Meixner 2008-11-19 09:06:51 MST --- Fixed in yast2-printer 2.17.42. Submitted to FACTORY/STABLE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c17 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |mzugec@novell.com --- Comment #17 from Johannes Meixner 2008-11-20 02:16:22 MST --- Michal, I have some questions: 1. What happens in case of an update of the installation? For example an update form an openSUSE 11.0 sytem to 11.1 - where the 11.0 system is set up as "client-only" - where the printer(s) are already set up in 11.0 In both cases there should be no automated queue setup. 2. In src/Printer.ycp in the Read() function the cupsd is started if( Mode::installation() && Stage::cont() ) As far as I know this is only needed for the automated queue setup, see bug #418585. If yes, I like to move this code from src/Printer.ycp to src/printer_proposal.ycp to have all what belongs to automated queue setup at one place. Do you agree? 3. The current code to start the cupsd in the Read() function only blindly triggers its start but it does not wait until the cupsd becomes actually accessible i.e. until "lpstat -h localhost -r" returns successfully, see in src/Printerlib.ycp the GetAndSetCupsdStatus() function. I like to add wait functionality to src/printer_proposal.ycp and additionally tests as in src/overview.ycp - whether or not it is a "client-only" config and - whether or not the cupsd listens on the official IANA IPP port (631) Do you agree? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c19 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC|coolo@novell.com | Priority|P1 - Urgent |P5 - None --- Comment #19 from Stephan Kulow 2008-11-20 04:09:48 MST --- doesn't sound P1 anymore -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=437735 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=437735#c21 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #21 from Johannes Meixner 2008-11-20 07:55:06 MST --- - Fixed how to avoid to autoconfigure multiple queues for the same printer. It is now based upon the URI which is sufficient because "usb://HP/" versus "hp:/usb/" duplicates and "parallel:/" versus "hp:/par/" duplicates are already avioded via the ConnectionItems("BasicAddDialog") call. Moved cupsd start when continuing a fresh installation in the target system (i.e. for the hardware proposal) from the Read() function in Printer.ycp to printer_proposal.ycp and wait for a started cupsd to become actually accessible (see Novell/Suse Bugzilla bnc#437735 starting at comment #17). - 2.17.43 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.