Hide Forgot
Description of problem: After a) a system suspend and resume, or b) printing something successfully, subsequent print jobs just get stuck in the printer queue. Version-Release number of selected component (if applicable): cups-pk-helper-0.2.5-6.fc23.x86_64 cups-filters-libs-1.6.0-1.fc23.x86_64 cups-client-2.1.2-1.fc23.x86_64 cups-libs-2.1.2-1.fc23.x86_64 python3-cups-1.9.72-2.fc23.x86_64 bluez-cups-5.36-1.fc23.x86_64 cups-filesystem-2.1.2-1.fc23.noarch gutenprint-cups-5.2.11-1.fc23.x86_64 cups-2.1.2-1.fc23.x86_64 cups-filters-1.6.0-1.fc23.x86_64 How reproducible: Every time after a suspend/resume. Steps to Reproduce: 1. Print something on network printer, e.g. HP CP2025DN in my case. 2. Suspend PC. 3. Resume PC 4. Send something to printer. Actual results: Nothing prints until a full reboot is performed. /var/log/messages contains: tail -f /var/log/messages Feb 3 15:49:18 arcturus cupsd: Start rendering... Feb 3 15:49:18 arcturus cupsd: Processing page 1... Feb 3 15:49:22 arcturus cupsd: Connecting to printer. Feb 3 15:49:22 arcturus cupsd: The printer is not responding. Feb 3 15:49:48 arcturus systemd: Started CUPS Scheduler. Feb 3 15:49:52 arcturus cupsd: The printer is not responding. Feb 3 15:50:22 arcturus cupsd: The printer is not responding. Feb 3 15:50:52 arcturus cupsd: The printer is not responding. Feb 3 15:51:22 arcturus cupsd: The printer is not responding. etc. Expected results: Should just print with no 'not responding' error message. Additional info: This used to work. An update to cups or some related package has broken printing in the last month or so.
/var/log/dnf.rpm.log:Feb 10 09:39:53 INFO Upgraded: cups-libs-1:2.1.3-1.fc23.x86_64 /var/log/dnf.rpm.log:Feb 10 09:39:53 INFO Upgraded: cups-client-1:2.1.3-1.fc23.x86_64 /var/log/dnf.rpm.log:Feb 10 09:39:53 INFO Upgraded: cups-filesystem-1:2.1.3-1.fc23.noarch /var/log/dnf.rpm.log:Feb 10 09:39:53 INFO Upgraded: cups-1:2.1.3-1.fc23.x86_64 FC23 testing update seems to have fixed this. Many thanks.
cups-2.1.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-52591d6b8a
cups-2.1.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
OK, I'm not sure this is totally fixed. In the case where the machine has been suspended to RAM and then reawoken, I still get: $ lpstat -t scheduler is running system default destination: HP_HP_Color_LaserJet_CP2025dn ... printer HP_HP_Color_LaserJet_CP2025dn now printing HP_HP_Color_LaserJet_CP2025dn-135. enabled since Fri 12 Feb 2016 14:18:49 GMT The printer is not responding. HP_HP_Color_LaserJet_CP2025dn-135 daddy 18432 Fri 12 Feb 2016 14:18:49 GMT
Doing a: systemctl restart cups does not rectify the problem. Nor does re-booting the printer. Only re-booting the computer causes printing to start.
Further info: Sometimes, cups will print the 1st item in a queue, but then refuse to print subsequent items, saying the usual, 'The printer is not responding'. NB. My printer is network printer, not USB etc.
Created attachment 1134841 [details] CUPS connection error controlctl -t cupsd -t log file Show a complete connection failure resulting in Printer not responding' status.
If I grep out the connection messages from a 'controlctl -t cupsd' command, I get the lines below. On a successful connection, CUPS connects by IP address. On an unsuccessful connection, CUPS tries to connect by Ethernet address. See below. Compare 192.168.1.191:9100 with fe80::223:7dff:fe8c:7f0c:9100. Is this the bug? Mar 10 11:20:55 arcturus.home cupsd[931]: Connecting to 192.168.1.191:9100 Mar 10 11:20:55 arcturus.home cupsd[931]: Connecting to printer. Mar 10 11:20:55 arcturus.home cupsd[931]: Set job-printer-state-message to "Connecting to printer.", current level=INFO Mar 10 11:20:55 arcturus.home cupsd[931]: STATE: -connecting-to-device Mar 10 11:20:55 arcturus.home cupsd[931]: Connected to printer. Mar 10 11:20:55 arcturus.home cupsd[931]: Set job-printer-state-message to "Connected to printer.", current level=INFO Mar 10 11:20:55 arcturus.home cupsd[931]: Connected to 192.168.1.191:9100... Mar 10 11:21:47 arcturus.home cupsd[931]: STATE: +connecting-to-device Mar 10 11:21:48 arcturus.home cupsd[931]: STATE: -connecting-to-device,offline-report Mar 10 11:21:48 arcturus.home cupsd[931]: STATE: +connecting-to-device Mar 10 11:21:52 arcturus.home cupsd[931]: Connecting to fe80::223:7dff:fe8c:7f0c:9100 Mar 10 11:21:52 arcturus.home cupsd[931]: Connecting to printer. Mar 10 11:21:52 arcturus.home cupsd[931]: Set job-printer-state-message to "Connecting to printer.", current level=INFO Mar 10 11:21:52 arcturus.home cupsd[931]: Connection error: Invalid argument
fe80::223:7dff:fe8c:7f0c:9100 is *not* a "ethernet address" (most like you mean MAC-address) it's a IPV6-LINK-LOCAL-ADDRESS https://en.wikipedia.org/wiki/Link-local_address#IPv6
Good point. Didn't look carefully enough.
Still broken in: cups-filters-1.8.3-1.fc23.x86_64 cups-libs-2.1.3-1.fc23.x86_64 cups-pk-helper-0.2.5-6.fc23.x86_64 cups-2.1.3-1.fc23.x86_64 cups-filesystem-2.1.3-1.fc23.noarch python3-cups-1.9.72-2.fc23.x86_64 cups-filters-libs-1.8.3-1.fc23.x86_64 bluez-cups-5.36-1.fc23.x86_64 gutenprint-cups-5.2.11-1.fc23.x86_64 cups-client-2.1.3-1.fc23.x86_64
There is a work-around (nto a fix). 1. Delete all existing cups queues for HP network printers. 2. Re-create all the queues from scratch using the hp-setup tool.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.