The list I have is far longer than that, but maybe that is due to having installed KDE (Plasma 5) or Gnome DE’s. I’ve never needed to install any further packages (especially CUPS components). Some users did need to install glibc-32bit for the 32-bit Brother drivers (as per the thread I linked to already).
I’ve put on hold attempting to get the TW about previously written to print. Now I’m on TW on a different PC trying via YaST2 to install basic print support.
What exactly does “server” mean in the context of YaST2’s description provided for patterns-server-printing? It seems to me each IP printer would be its own server, so any OS installation needs its cups to be no more than a client, if that. IOW, it looks like patterns-server-printing would include unnecessary bloat.
Any host that can accept a print job and communicate to either a USB-connected printer or network-attached printer is acting as a CUPS server, even if the job is originating on the localhost. So most users would already have a working CUPS server environment for printing via a local machine.
CUPS clients are described here…
https://www.cups.org/doc/sharing.html
More info
man client.conf
The ‘patterns-server-printing’ pattern (a metapackage) would bring in cups (and it’s dependencies) as well as the ‘basesystem’ pattern.
# zypper info --requires patterns-server-printing
Retrieving repository 'packman' metadata ...........................................................................................[done]
Building repository 'packman' cache ................................................................................................[done]
Loading repository data...
Reading installed packages...
Information for package patterns-server-printing:
-------------------------------------------------
Repository : openSUSE-Leap-15.2-Oss
Name : patterns-server-printing
Version : 20180302-lp152.6.3
Arch : x86_64
Vendor : openSUSE
Installed Size : 54 B
Installed : No
Status : not installed
Source package : patterns-server-20180302-lp152.6.3.src
Summary : Print Server
Description :
This pattern provides all packages necessary for printing. It provides all
needed packages for printing to a locally connected printer, printing using a
remote print server and for setting up a print server.
Requires : [2]
cups
pattern() = basesystem
I’m not sure why this wouldn’t also include ‘cups-filters’ as well, and IMO ‘cups-filters’ should include the requirement for ‘poppler-tools’ I guess.
I mentioned bug #868148 back in post #11.
Looking at the OBS cups-filters/cups-filters.spec I note the following…
# /usr/bin/pdftops (provided by poppler-tools)
# is needed (but not required for non-PostScript printers)
# to print PDFs on PostScript printers because in this case
# the CUPS filter chain is:
# /usr/lib/cups/filter/pdftopdf
# /usr/lib/cups/filter/pdftops
# where /usr/lib/cups/filter/pdftops calls /usr/bin/pdftops
# /usr/lib/cups/backend/...
# see https://bugzilla.novell.com/show_bug.cgi?id=868148
Recommends: poppler-tools
TW host asa88 also fails to provide any clues to failure that I can recognize, other than HTTP_STATE_WAITING Closing for error 32 (Broken pipe), which as yet hasn’t lead me to anything helpful. Also as yet, no print job has ever shown up in http://localhost:631/printers/<printername>. This error_log is from trying to print test pages from both YaST2 & http://localhost:631/printers/<printername>.
Installed packages from this search look pretty much like that from OP test host ab85m, with a few added by installing the pattern print_server.
# zypper se -i cups popp glibc libstdc pdf 32bit print
...
S | Name | Summary | Type
---+------------------------------+------------------------------------------------------------------------+--------
i+ | OpenPrintingPPDs-ghostscript | PPD files from OpenPrinting.org which use Ghostscript built-in drivers | package
i+ | OpenPrintingPPDs-postscript | PPD files from OpenPrinting.org for PostScript printers | package
i | cups | The Common UNIX Printing System | package
i+ | cups-backends | Additional Backends for CUPS | package
i | cups-client | CUPS Client Programs | package
i | cups-config | CUPS library configuration files | package
i | cups-filters | OpenPrinting CUPS filters, backends, and cups-browsed | package
i+ | cups-pdf | Virtual PDF printer for CUPS | package
i+ | glibc | Standard Shared Libraries (from the GNU C Library) | package
i+ | glibc-32bit | Standard Shared Libraries (from the GNU C Library) | package
i | glibc-locale-base | en_US Locale Data for Localized Programs | package
i+ | hl5470dwcupswrapper | Brother HL-5470DW CUPS wrapper driver | package
i | libQt5PrintSupport5 | Qt 5 Print Support Library | package
i | libcups2 | HTTP/IPP communication and printer queue and job library | package
i | libcupsimage2 | CUPS library for working with large images | package
i | libgcc_s1-32bit | C compiler runtime library | package
i | libpoppler-cpp0 | C++ API of the Poppler PDF rendering library | package
i | libpoppler-glib8 | Glib wrapper for the poppler PDF rendering library | package
i | libpoppler103 | PDF Rendering Library | package
i | libqpdf28 | Shared libraries for qpdf | package
i | libstdc++6 | The standard C++ shared library | package
i+ | libstdc++6-32bit | The standard C++ shared library | package
i | linux-glibc-devel | Linux headers for userspace development | package
i | parallel-printer-support | Parallel Printer Support | package
i+ | patterns-server-printing | Print Server | package
i | poppler-data | Encoding Files for use with libpoppler | package
i | poppler-tools | PDF Rendering Library Tools | package
i | print_server | Print Server | pattern
i+ | trinity-kpdf | PDF viewer for Trinity | package
i+ | trinity-tdeprint | Print system for TDE | package
i+ | yast2-printer | YaST2 - Printer Configuration | package
# ls -l /etc/cups/ppd/
...
-rw-r----- 1 root lp 12158 Dec 6 23:54 HL5470DW.ppd
-rw-r----- 1 root lp 12159 Dec 6 23:53 HL5470DW.ppd.O
Please avoid trying to share the output using fm.no-ip.com. None of those you’ve posted so far allow me to view the content. Stick with pastebin or susepaste please.
That’s my own Apache2 running on this machine. All those URLs work for me. I load them, then paste those working URLs into the message. If they’re being denied to others, I need to find out why. Are you blocking http://-only sites somehow?
Susepaste has been a PITA for me, between outright rejections, claimed failures, erroneous claimed successes, latency, short default lifetimes, and more.
# susepaste -e 10080 -n mrmazda error_log-asa88tw-5470-testsEQyastEQcups.txt
Pasted as:
https://susepaste.org/3760608
https://paste.opensuse.org/3760608
# susepaste -e 10080 -n mrmazda error_log-asa88tw-5470-yasttest.txt
Pasted as:
https://susepaste.org/96059575
https://paste.opensuse.org/96059575
These URLS are giving me 404s. Pastebin I don’t even try any more, as it has given me its own set of foibles. Besides, my website is convenient, and should be working, with expiry readily under my control. Maybe you can help me try troubleshooting via IRC, a-865 or a-865k on three different suse channels on freenode.
Can you filter the output by grepping as I indicated back in post #3? That should reduce the output enough that it can be posted here. Make sure CUPS is in debug mode (for more verbose reporting) first.
I just checked and can reach the following ok…
http://info.cern.ch
http://example.com
If I attempt to use the posted URLs nothing loads. Should wget work to download the file?
That only cut the size to 130kb.
I got a susepaste through of the grep’d edition: SUSE Paste.
Trying again got the full log through: SUSE Paste.
This is the one from ~25 hours ago: SUSE Paste
Yes, I just saw that. Late here, so will check back here tomorrow.
The error_log reports…
Grayscale/monochrome printing requested for this job but Poppler is not able to convert to grayscale/monochrome PostScript.
Use \"pdftops-renderer\" option (see README file) to use Ghostscript or MuPDF for the PDF -> PostScript conversion.
You could try changing the postscript renderer to Ghostscript with something like
lpadmin -p printer -o pdftops-renderer-default=gs
•where printer is the printer queue name.
Refer cups-filters README for more info…
https://fossies.org/linux/cups-filters/README
In particular the ‘POSTSCRIPT PRINTING RENDERER AND RESOLUTION SELECTION’ section.
The ‘cups-filters’ README file is located at /usr/share/doc/packages/cups-filters/README.
Ghostscript has better color management and is generally optimized
more for printing. Poppler produces a PostScript which is
compatible with more buggy built-in PostScript interpreters of
printers and it leads to a somewhat quicker workflow when
graphical structures of the input PDF has to be turned into
bitmaps. Adobe Reader is the PDF renderer from Adobe, the ones who
created PDF and PostScript. pdftocairo is a good choice for the
PDF output of Cairo (for example when printing from evince). It
is less resource-consuming when rasterizing graphical elements
which cannot be represented in PostScript (like
transparency). Note that pdftocairo only supports PDF input using
DeviceRGB, DeviceGray, RGB or sGray and is not capable of
generating PostScript level 1. So its support is only experimental
and distributions should not choose it as default.
The selection is done by the "pdftops-renderer" option, setting it to "gs", "pdftops", "pdftocairo", "acroread", "mupdf", or "hybrid":
Per-job: lpr -o pdftops-renderer=pdftops ... Per-queue default: lpadmin -p printer -o pdftops-renderer-default=gs Remove default: lpadmin -p printer -R pdftops-renderer-default
By default, pdftops uses Ghostscript if this does not get changed at compile time, for example by the Linux distribution vendor.
Hybrid means Ghostscript for most printers, but Poppler's pdftops for Brother, Minolta, and Konica Minolta. Printer make and model information comes from the PPD or via the "make-and-model" option.