New: cups problems in buildroot

https://bugs.busybox.net/show_bug.cgi?id=12661

Bug ID: 12661
Summary: cups problems in buildroot
Product: buildroot
Version: 2019.11.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: skif at skif-web.ru
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 8401
--> https://bugs.busybox.net/attachment.cgi?id=8401&action=edit
configs and logs

If printing test-page (from cups web-interface), got error "Exception: open no:
No such file or directory" in web-interface

If printing text-file (fstab for example, lp /etc/fstab), got error "Exception:
open no: No such file or directory" in web-interface.

If printing binary file, (head -n 1 /bin/cp >/1;lp -d test /1) all works fine

Used printer - hp laserJet pro m402dn
Used driver - generic post-script (work fine fron linux-mint and gentoo) Used defaconfig - qemu_x86_84_defconfig

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12661

--- Comment #1 from Peter Seiderer <[email protected]> --- Maybe related to commit 'package/cups: store web-interface files under /usr/share/cups/doc-root' ([1])?

[1]
https://git.buildroot.net/buildroot/commit/?h=2019.02.x&id=822067294a9949fa79e5ff6c6d8d6a434ef4a7a0

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12661

--- Comment #2 from Alexey <[email protected]> --- I tried both variants - with this patch and without.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12661

--- Comment #3 from Alexey <[email protected]> ---
I found the answer myself

It's big complex ptobleb with qpdf, cups-filters and ghostscrips patchs sumbitted:

http://lists.busybox.net/pipermail/buildroot/2020-April/279672.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279676.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279677.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279673.html

There are multiple issues in buildroot that faults cups printing.

First trouble is incorrect qpdf buiding.
Qpdf is mandatory dependence of cups.
In current master, qpdf builds with incorrect --no-random option. On any work< qpdf send 'no such file' error. For example:
qpdf /usr/share/cups/data/secret.pdf -

This commmand must get PDF file in stdout.But only 'No such file or
directory' error present.

0/1 patch fix this by changing configure options to with-random=/dev/random.

Next global problem - cups-filters need ghostscript.
From https://github.com/OpenPrinting/cups-filters/blob/master/README :
By default, pdftops uses Ghostscript if this does not get changed
at compile time, for example by the Linux distribution vendor.

0/2 patch fix id by settinbg ghostscript as default render if ghostscript enabled in voard config.

Last trouble - ghostscript building without cups support.

0/3 patch fix is by removing disable-patch option. Now, if cups is enabled, it will be added to dependencies and correct configure options added to ghostscript building. Also fixed ghostscript buildroot building issue with unpleasant hack in configure.ac, which broke pkg-config. It's broke cups search by ghostscript configure script.
GHOSTSCRIPT_CUPS_CONFIG_FIX also needed for this task.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12661

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Thomas Petazzoni <[email protected]> --- All these patches have been applied:

https://git.buildroot.org/buildroot/commit/?id=69dfbbd33b2afab0814c5674b0bc7f5464941fbc
https://git.buildroot.org/buildroot/commit/?id=59acde11f9f93e99df309b2ed7a14795bedbcfa9
https://git.buildroot.org/buildroot/commit/?id=f9e359d7653f4af32a491e2baf4b6e524554174b

Thanks a lot for your contribution!

You are receiving this mail because:
You are on the CC list for the bug.