https://bugzilla.novell.com/show_bug.cgi?id=888782 https://bugzilla.novell.com/show_bug.cgi?id=888782#c0 Summary: yast2-printer does not restart cupsd when printer driver RPMs changes need it Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: All OS/Version: openSUSE 13.1 Status: ASSIGNED Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: jsmeix@suse.com ReportedBy: jsmeix@suse.com QAContact: jsrain@suse.com Found By: Development Blocker: --- In particular when additional printer driver RPMs get installed - the new RPMs may provide necessary filters that are referenced in the PPD files to process print jobs for the new drivers - the new RPMs may require other RPMs that provide necessary filters with additional MIME *.convs files to process print jobs A restart of cupsd is needed when print job processing has changed. Currently yast2-printer does not restart cupsd when printer driver RPMs changes need it. In this case one can set up a print queue using a PPD from the new installed printer driver RPM but when print job processing has changed printing would fail with an error like the IPP error code "client-error-document-format-not-supported" or a message of the "lp" program like "Unsupported document-format". Re-starting yast2-printer does not help. Only re-starting cupsd helps which means for unexperienced users that a reboot helps. It is not possible to re-start cupsd in any case when printer driver RPMs were changed by yast2-printer because by design yast2-printer restarts cupsd only when really needed, see "Basic Implementation Principles:" "Strict Compliance With CUPS" at http://en.opensuse.org/Archive:YaST_Printer_redesign It could become tricky to implement a generic test when print job processing has changed so that yast2-printer could re-start cupsd only when really needed. -- 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.