https://bugzilla.novell.com/show_bug.cgi?id=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c2 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jsmeix@suse.com | --- Comment #2 from Johannes Meixner <jsmeix@suse.com> 2013-11-29 09:56:26 CET --- Having a local "raw" print queue that only forwards application's print data "as is" to a remote CUPS queue is one correct way how printing to a remote CUPS queue can be done under Linux. Therefore things get set up in a technically correct way when system-config-printer is installed. As far as I understand the issue this bug would be fixed when system-config-printer gets installed by default. FYI: There are other correct ways too, see "Configuring CUPS <= 1.5 in the Network" at http://en.opensuse.org/SDB:CUPS_in_a_Nutshell and have a look at the "Printing via Network" dialog in the YaST printer setup module. Which one of the correct ways is best depends on the particular network environment and on the particular user's preferences. As far as I know the two main differentiating factors are: * Is it a stationary workstation in a static network environment or is it a mobile system (e.g. a laptop). * Is it a traditional CUPS <= 1.5 server that supports "Browsing" or is it a CUPS >= 1.6 server that does no longer support Browsing but that supports DNS-SD (via Avahi) instead (see bnc#735404). An advantage of a local "raw" queue that forwards to a remote CUPS queue is that this setup should work in any case regardless what CUPS version is used on the server and regardless of the networking setup (it also works when an active firewall on the local system blocks CUPS Browsing and/or DNS-SD network traffic). One disadvantage of having local queues to use a remote CUPS server is that this requires active setup actions on the client which is in contrast to the design of CUPS for printing in the network that is "no CUPS-specific configuration on the client hosts". The queues of a CUPS server should be automatically available on client hosts without need for a CUPS-specific configuration on the client that by default must require root permissions, see http://en.opensuse.org/openSUSE:Security_use_cases#Printer Another disadvantage of having local queues to print on a remote CUPS queue is that the local queue setup is static. I.e. whenever something changes on the remote CUPS server (e.g. when the remote queue on the CUPS server gets deleted), the local setup does not automatically adapt. On a mobile system the locally available print queues do not automatically adapt to the actually available print queues in the current network environment. But it depends on the particular user's preferences to have a static local setup for printing via network. -- 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.