[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#931560: cups-backend-bjnp: refuses to print with "out of paper" error



Package: cups-backend-bjnp
Version: 2.0.1-1
Severity: important
Tags: upstream

Dear Maintainer,

Printer: Canon PIXMA MG6150
Backend: bjnp

Upgraded to Debian buster, cups now refuses to print with error
"Network host '...' is out of paper, will retry in 30 seconds..."

Tried restarting the printer, restarting cups, manually removing
'Reason' lines from /etc/cups/printers.conf (while cups is off),
nothing solved the issue.

I took a look at upstream changelog and noticed this for 2.0:
> Ink level reporting is added as well as improved error handling.

I suspected that there could be a regression, so I downgraded the
package (and only this package) to the version in stretch (1.2-2)
and the problem went away instantly. I didn't even need to restart
cups: the new bjnp backend started printing in the next automatic
retry. Tried upgrading again and problem returned; downgraded and
problem disappeared.

Note that I have a few ink cartdriges that are nearly running out,
but not low enough that the printer refuses to print. It could be
possible that the new ink level reporting code is misinterpreting
this condition as an "out of paper" condition. Unfortunately I
don't have new cartdriges at hand to test this hypothesis.

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.15-1-pve (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-backend-bjnp depends on:
ii  libc6     2.28-10
ii  libcups2  2.2.10-6

Versions of packages cups-backend-bjnp recommends:
ii  printer-driver-gutenprint  5.3.1-7

cups-backend-bjnp suggests no packages.

-- no debconf information


Reply to: