Bug#953419: cups: unable to print after a recent update

[Didier 'OdyX' Raboud <odyx@debian.org>]

Control: reassign -1 src:hplip 3.20.2+dfsg0-1
Control: retitle -1 hplip regression: 3.20.2 unable to print on HP_OfficeJet_Pro_8710

Dear Frank,

thank you for filing this bug.

This looks like a bug in hplip, not in CUPS, see #953104. I'm hereby
reassigning this one.

Cheers,
OdyX

Le lundi, 9 mars 2020, 13.48:58 h CET Frank Brokken a écrit :
> Dear Maintainer,
> 
> Subject: cups: unable to print after a recent update
> Package: cups
> Version: 2.3.1-11
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> After a recent upgrade files could no longer be printed. Printing a test
> page through the printer's direct web-interface still works, as does using
> its document scan facilities (through xsane). Printing a test-page through
> the cups interface no longer works, and neither does the lp command
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> The only thing that changed was a recent update. The debian packages are
> regularly updated, usually once a week.
> 
>    * What was the outcome of this action?
> 
> After a recent update standard print commands no longer worked. When trying
> to print a test-page printing is pending, and 'service cups status'
> reports:
> 
> service cups status
> ● cups.service - CUPS Scheduler
>      Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor
> preset: enabled) Active: active (running) since Mon 2020-03-09 13:10:31
> CET; 16min ago TriggeredBy: ● cups.path
>              ● cups.socket
>        Docs: man:cupsd(8)
>    Main PID: 13933 (cupsd)
>       Tasks: 3 (limit: 4602)
>      Memory: 33.0M
>      CGroup: /system.slice/cups.service
>              ├─13933 /usr/sbin/cupsd -l
>              ├─14170 HP_OfficeJet_Pro_8710 606 frank semval.h 1 finishings=3
> number-up=1 sides=two-sided-long-edge
> job-uuid=urn:uuid:b9fe96d0-d6e7-31b2-7c2b-22d0a80a401a
> job-originating-host-name=localhost date-time-at-creation=
> date-time-at-proces> └─14171
> hp:/net/HP_OfficeJet_Pro_8710?hostname=printer.oostum.north 606 frank
> semval.h 1 finishings=3 number-up=1 sides=two-sided-long-edge
> job-uuid=urn:uuid:b9fe96d0-d6e7-31b2-7c2b-22d0a80a401a
> job-originating-host-name=localhost date>
> 
> Mar 09 13:10:31 localhost.localdomain systemd[1]: Started CUPS Scheduler.
> Mar 09 13:25:40 localhost.localdomain hp[13939]: io/hpmud/jd.c 94: unable to
> read device-id Mar 09 13:25:40 localhost.localdomain hp[13939]:
> prnt/backend/hp.c 630: ERROR: 5012 device communication error! Mar 09
> 13:26:15 localhost.localdomain cupsd[13933]: pam_unix(cups:auth): Couldn't
> open /etc/securetty: No such file or directory Mar 09 13:26:15
> localhost.localdomain cupsd[13933]: pam_unix(cups:auth): Couldn't open
> /etc/securetty: No such file or directory
> 
> I've found several references to /etc/securetty, most of them indicating
> that /etc/securetty isn't used anymore, but after asking cups to print a
> test page it takes a long while (about 2 minutes) before 'service cups
> stop' completes.
> 
> After 'service cups stop'; 'touch /etc/securetty'; and 'service cups start'
> the error message no longer appears in the 'service cups status' command,
> but still nothing is printed.
> 
>    * What outcome did you expect instead?
> 
> After the update I expected the print commands to continue working



-- 
    OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.