[Bug 852842] New: system-config-printer-applet makes unexpected setup to print to a remote CUPS queue
https://bugzilla.novell.com/show_bug.cgi?id=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c0 Summary: system-config-printer-applet makes unexpected setup to print to a remote CUPS queue Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: jsmeix@suse.com QAContact: qa-bugs@suse.de CC: cfarrell@suse.com Found By: Development Blocker: No I am only the messenger here. The problem was shown to me by Ciaran Farrell. When system-config-printer-applet is installed but system-config-printer is not installed (which is probably the default) then system-config-printer-applet makes an unexpected setup to print to a remote CUPS queue: It set up a local queue using the PPD file from the remote queue from the remote CUPS server which means that the local host would do the print job filtering (i.e. the conversion from application's print data like PostScript or PDF into printer model specific data). This means that in particular the printer driver must run on the local host which means that matching software that provides the printer driver must be installed on the local host. That is contradictory to how printing to a remote CUPS queue should usually be done under Linux: The client submits application's print data like PostScript or PDF directly into the remote CUPS queue and on the remote CUPS server the print job filtering happens, compare the section about "Differences in Printing between Windows and Linux" in http://en.opensuse.org/SDB:Printing_from_Windows_to_Linux In contrast when system-config-printer is installed, the behaviour is very different: The dialogs look different and what gets set up in the end is a local "raw" print queue (i.e. a local queue without a PPD file) that forwards application's print data "as is" to the remote CUPS queue. How to reproduce: In Gnome desktop klick "Activities" and at "Type to search" slowly enter "printer" - while typing it "Printers - Add printers, ..." appears - click on that so that a "Printers" dialog opens. Therein click "Unlock" and enter the root password. Then click [Add New Printer] - a "Add a New Printer" dialog opens. Therein at "Enter address of a printer or a text to filter results" type in the IP address of the remote CUPS server and hit the enter key. Then the remote CUPS queues on that server are shown. Select one of those remote CUPS queues and click [Add]. In the end a local print queue gets set up using the PPD file from the remote queue from the remote CUPS server. It even searches for packages to be installed that provide needed printer driver software but if no matching packages are found or can be installed it is a dead end and printing via that queue cannot work. -- 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=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |dimstar@opensuse.org InfoProvider| |jsmeix@suse.com --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> 2013-11-28 22:43:21 UTC --- (In reply to comment #0)
When system-config-printer-applet is installed but system-config-printer is not installed (which is probably the default)
That is actually an error in the .spec file... the requires are wrong (fixed in my branch).
then system-config-printer-applet makes an unexpected setup to print to a remote CUPS queue:
That's then understandable. The applet is basically missing entry points and starts 'guessing'..
In contrast when system-config-printer is installed, the behaviour is very different:
The dialogs look different and what gets set up in the end is a local "raw" print queue (i.e. a local queue without a PPD file) that forwards application's print data "as is" to the remote CUPS queue.
And this is how it should be, right? -- 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=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo. |dimstar@opensuse.org |novell.com | -- 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=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.
https://bugzilla.novell.com/show_bug.cgi?id=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c3 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|system-config-printer-apple |[MAINT] |t makes unexpected setup to |system-config-printer-apple |print to a remote CUPS |t makes unexpected setup to |queue |print to a remote CUPS | |queue --- Comment #3 from Dominique Leuenberger <dimstar@opensuse.org> 2013-12-01 18:05:16 UTC --- Maintenance update submitted, requiring system-config-printer from the -applet package. This results at least in a valid setup. -- 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=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c4 Benjamin Brunner <bbrunner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Benjamin Brunner <bbrunner@suse.com> 2013-12-09 14:52:23 CET --- Update released for openSUSE 13.1. Resolved fixed. -- 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=852842 https://bugzilla.novell.com/show_bug.cgi?id=852842#c5 --- Comment #5 from Swamp Workflow Management <swamp@suse.de> 2013-12-09 14:05:20 UTC --- openSUSE-RU-2013:1842-1: An update that has two recommended fixes can now be installed. Category: recommended (low) Bug References: 852450,852842 CVE References: Sources used: openSUSE 13.1 (src): system-config-printer-1.4.2-2.4.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.
participants (1)
-
bugzilla_noreply@novell.com