Bug 537443
| Summary: | can't re-enable HP inkjet printer without root intervention | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael J. Chudobiak <mjc> |
| Component: | hplip | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | jpopelka, twaugh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-16 12:35:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael J. Chudobiak
2009-11-13 16:21:33 UTC
This is the reason the printer was disabled: D [12/Nov/2009:16:23:40 -0500] [Job 316] prnt/backend/hp.c 618: ERROR: 5012 device communication error! HPLIP might have logged more information in /var/log/messages. Can you please take a look to see if you can find any HPLIP-related messages in /var/log/messages* from that moment? Nov 12 16:17:05 thorn hp[5872]: io/hpmud/jd.c 531: timeout write_channel hp:/net/Deskjet_6940_series?ip=192.168.0.161 Nov 12 16:17:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:17:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:18:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:18:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:19:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:19:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:20:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:20:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:21:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:21:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:22:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:22:35 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:23:05 thorn hp[5872]: prnt/backend/hp.c 604: ERROR: 1014 media-jam-error; will retry in 30 seconds... Nov 12 16:23:38 thorn hp[5872]: io/hpmud/jd.c 88: unable to read device-id Nov 12 16:23:38 thorn hp[5872]: prnt/backend/hp.c 618: ERROR: 5012 device communication error! The computer was turned off shortly after that, and turned on next morning. No further hp[....] messages occur after the above ones. - Mike Perhaps the printer was turned off at 16:23? That would explain "unable to read device-id" which seems to be the cause of the communication error which led to the print queue becoming disabled. I spoke to the user:
1) A print job was being printed, and they noticed the paper tray was almost empty.
2) They somehow inserted more paper, but this made the printer unhappy ("printer jam").
3) They turned it off and went home.
Which is all fine and good - but it would be nice if the printer auto-re-enabled the next morning, after printer and cpu power up.
I've run into this in other now-forgotten situations. I (the admin) have to re-enable a printer as root, and the printer is then fine.
- Mike
So, in this situation, there is no way for CUPS or HPLIP to know whether this is a temporary or permanent error. The job gets marked as having failed, so the printer-error-policy is followed. It sounds like you want to change the printer-error-policy to retry-job. It would make more sense to set the default error policy to retry-job. That way, the user does not require root to re-start the printer once the paper jam (or whatever) has been fixed. Ubuntu has done so: https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/41313 - Mike |