https://bugzilla.novell.com/show_bug.cgi?id=889591 https://bugzilla.novell.com/show_bug.cgi?id=889591#c0 Summary: RPMs that provide new printing filters do not restart cupsd Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: All OS/Version: openSUSE 13.2 Status: ASSIGNED Severity: Minor Priority: P5 - None Component: Printing AssignedTo: jsmeix@suse.com ReportedBy: jsmeix@suse.com QAContact: jsmeix@suse.com Found By: Development Blocker: --- When packages get installed that provide new printing filters or change the CUPS MIME conversion rules e.g. by providing new /usr/share/cups/mime/<whatever>.convs files, then cupsd must be restarted. Also when such RPMs are uninstalled cupsd must be restarted because a restart of cupsd is needed whenever print job processing has changed, cf. https://bugzilla.novell.com/show_bug.cgi?id=888782#c0 For example when in a minimal system only cups-filters-ghostscript and cups-filters-foomatic-rip are installed, then printing "text/plain" is not supported. For example "echo hello | lp -d <queue_name>" fails with "lp: Unsupported document-format text/plain". To support "text/plain" the package cups-filters is needed because it provides in particular the printing filters /usr/lib/cups/filter/textto* together with a matching /usr/share/cups/mime/cupsfilters.convs To let cupsd recognize the changed print job processing, it must be restarted. The question is whether or not is is a good idea to automatically restart the cupsd by RPM postinstall scriptlet and also restart the cupsd by RPM postuninstall scriptlet for RPMs that provide printing filters or change the conversion rules. But a restart of the cupsd disrupts all currently printing jobs and re-prints them from the beginning after its restart so that automated restartd by RPM scriptlets is bad at least on print server machines. -- 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.