https://bugzilla.novell.com/show_bug.cgi?id=388575 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388575#c1 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal --- Comment #1 from Johannes Meixner 2008-05-09 01:11:25 MST --- No longer a major bug because it is only the wording which totally confused me. Furthermore the CUPS UTF-8 issue (see bug #387130) hit me because I run yast2-printer in a "en_GB.iso885915" locale which is probably the reason that yast2-printer didn't get any possible DeviceURI from the cupsd so that the list was empty. When running yast2-printer in a UTF-8 or 7-bit ASCII locale the "New Queue for Existing Printer" popup shows a list of possible DeviceURIs. Because of the YaST2 'text freeze' I suggest to simply omit the "New Queue for Existing Printer" text at all because it is plain wrong here. What is missing is a way to set an arbitrary DeviceURI. Could perhaps the [Connection Wizard] button lead to the usual workflow to choose the connection manually (locally connected, network, ...), see bug #388574. -- 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=388575 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388575#c3 --- Comment #3 from Johannes Meixner 2008-05-09 02:52:22 MST --- When I have a queue for a USB printer and change its connection to "parallel..." there is no automated selection of a new driver. When I have a queue for a parallel port printer and change its connection to one for a USB printer there is an automated selection of a new driver but the selected driver does not always match to the model to which the USB printer DeviceURI belongs. I have in particular plain wrong automated drivers if I use a DeviceURI for a HP network printer like hp:/net/Officejet_7200_series?ip=10.10.100.100 I.e. the results are inconsistent and sometimes plain wrong depending on whatever obscure magic! The more I test it the worse it becomes. -- 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=388575 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388575#c5 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Enhancement Status|RESOLVED |REOPENED Component|YaST2 |YaST2 OS/Version|openSUSE 11.0 |SuSE Other Product|openSUSE 11.0 |openSUSE 11.1 Resolution|FIXED | Version|Beta 2 |Alpha 0 --- Comment #5 from Johannes Meixner 2008-05-16 08:16:37 MST --- Some good news after the many bug reports: I installed openSUSE 11.0 beta3 from scratch on i386 hardware but I updated yast2-printer from what is in beta-3 to yast2-printer-2.16.26 which I built from what was in /work/src/done/STABLE/yast2-printer/ I can confirm that now "Change Connection" works well. It changes only the DeviceURI and it does it regardless which strange new URI I choose or which strange URI I enter manually (e.g. it works for "parallel:/tmp/foobar") which is excatly correct (provide reasonable predefined values but nevertheless let the user the freedom to configure it as he insists). There is only one tiny issue left: CUPS rejects to set up a DeviceURI if the URI scheme (the first word in the URI, see "man backend") is unknown to the cupsd. Therefore it fails when I enter manually "paralel:/dev/lp0" (note the missing 'l' - the correct URI scheme is "parallel"). It is perfectly correct that it fails but 1. There is only an error message when [Finish] so that the user cannot correct it at this stage. Compare http://en.opensuse.org/YaST/Development/Printer_Enhancement "Transaction Semantics For Each One Setup" 2. The error popup reads "Queue <queuename> cannot be saved because the selected spooler does not support it" which is misleading. 3. The error popup does not show the original error message from the system which mentions exactly what is actually wrong: --------------------------------------------------------------- nelson:~ # lpadmin -p printer -v paralel:/dev/lp0 lpadmin: Bad device-uri "paralel:/dev/lp0"! --------------------------------------------------------------- Compare this bug from the stone age: https://bugzilla.novell.com/show_bug.cgi?id=suse10048 Therefore I reopened it as enhancement for openSUSE 11.1 -- 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=388575 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388575#c7 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|jsmeix@novell.com | --- Comment #7 from Johannes Meixner 2008-05-20 00:22:54 MST --- What about x86_64 (i.e. /usr/lib64/cups/backend/)? What about architectures which may have /usr/lib32/? (read the FHS!) What about files in /usr/lib[64]/cups/backend/ which are not exectutable (e.g. intentionally disabled backends)? What about exectuable backends which fail on the particular user's system? Read http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends"! Why do you always prefer to inspect the file system when it is the local running cupsd and only this cupsd which has the currently actually correct information? I explained it already so many many times to you! Use "lpinfo -h localhost ..." and nothing else! Get rid of all this crap in yast2-printer which leads only to more and more problems! Start to implement it in compliance with CUPS! Stop re-implementing stuff as YaST-specific ditry-hacks! Only lpinfo -h localhost -v | cut -s -d ' ' -f2 | cut -d ':' -f1 | sort -u (or equivalent CUPS library calls) results what you need! If this command results nothing, there is a severe reason, e.g. no local running cupsd and then it is exactly correct that the command fails in contrast to your dirty hack which works even without a local running cupsd! -- 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.