http://bugzilla.opensuse.org/show_bug.cgi?id=1078553
http://bugzilla.opensuse.org/show_bug.cgi?id=1078553#c2
--- Comment #2 from Johannes Meixner ---
I think it works as designed, see
https://en.opensuse.org/YaST_Printer
that reads (excerpts):
---------------------------------------------------------------------------
The Printer Configurations Dialog
When the YaST printer module started, it shows the printer configurations.
This dialog shows an overview of all available print queues - both local
and remote queues - at a glance and it shows also all possible
configuration tasks.
There is a difference between "local/remote queue"
and "local/remote printer":
"Local queue" means a print queue which is configured on the local
computer (strictly speaking the computer where the YaST printer
module runs) which is usually the computer where the user sits
in front of.
"Remote queue" means a print queue which exists on whatever
computer in the network or on whatever network printer.
"Local printer" means a printer device which is directly connected
to the local computer (usually a USB printer).
"Remote printer" means a printer device which is not directly
connected to the local computer (usually a printer with
a built-in network interface).
Only local print queues can be configured with the YaST printer module.
But local print queues can be set up both for local printers and
for remote printers. It does not matter how the printer device
is connected but it does matter whether or not the print queue
configuration exists on the computer where the YaST printer module runs.
...
Connection
...
The YaST printer module does not implement any printer autodetection
on its own. It only shows those printer connections which were
already autodetected by CUPS ...
---------------------------------------------------------------------------
In the same way as describend for "Connection" above
the YaST printer module does not implement any remote print queue
autodetection on its own. It only shows those remote print queues
which were already autodetected by CUPS or by other lower-level tools
like DNSSD (implemented by Avahi on Linux) that is used by CUPS
or by the cups-browsed service (part of the separated cups-filters
software that is not a sub-package of CUPS) that do the actual
remote print queue autodetection.
Simply put the YaST printer module shows a subset of the locally
avialable print queues that are listed by "lpstat -h localhost -p"
as "remote queues" with whatever queue names and info as it comes
out of "lpstat -h localhost -p" i.e. same as what CUPS "knows"
and same what application programs that use libcups should show
cf. the section "Strict Compliance With CUPS" in
https://en.opensuse.org/Archive:YaST_Printer_redesign
Only FYI (perhaps not directly related to this issue):
Newest CUPS versions have a new "automated print queue setup"
feature (perhaps together with cups-browsed from the
separated cups-filters software) where you may get
automatically print queues setup with whatever
"driver" the automatism "thinks" is o.k.
cf. "Automated Printer Configuration" in
https://en.opensuse.org/YaST_Printer
see also in
https://features.opensuse.org/316789
the entry about "CUPS 2.2 Preview"
--
You are receiving this mail because:
You are on the CC list for the bug.