This issue is probably connected with #1276918, but behaves slightly different. I tried to reproduce this issue with Tore's steps from comment #6 in Fedora 26, but with no luck. But I have reports from people who are seeing printers, but cannot print with message: ERROR: No destination host name supplied by cups-browsed for printer <name>, is cups-browsed running? They can print again only after restarting cups-browsed or whole PC. That error message is printed out from implicitclass backend, when cups-browsed communication timed out. This issue is showed sometimes, which makes it difficult to reproduce. I think I can try to set bigger timeout or try to add network-online.target to cups-browsed unit file. Reproducible: Sometimes
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Maybe connected to changes in #975241, #975933, #959682.
Created attachment 1402973 [details] cups-browsed log when print did not start (service restart need not reported in gnome) cups-browsed log from the last few minutes, so it should include the even when I wanted to print a document, but the printing did not start (and service restart need not reported in gnome)
Packages used when seeing the issue above: # rpm -qa|grep cups bluez-cups-5.48-2.fc27.x86_64 gutenprint-cups-5.2.13-3.fc27.x86_64 cups-filters-libs-1.16.1-4.fc27.x86_64 cups-libs-2.2.4-8.fc27.x86_64 cups-client-2.2.4-8.fc27.x86_64 cups-filesystem-2.2.4-8.fc27.noarch python3-cups-1.9.72-14.fc27.x86_64 cups-filters-1.16.1-4.fc27.x86_64 cups-libs-2.2.4-8.fc27.i686 cups-pk-helper-0.2.6-4.fc27.x86_64 cups-2.2.4-8.fc27.x86_64
Created attachment 1403005 [details] cups log when print did not start (service restart need not reported in gnome) Also attaching cups log from the same time.
I was able to reproduce the issue for suspend/wake up scheme - but it reproduces only sometimes (I was able to reproduce it in 50% of attempts). Nothing interesting in cups-browsed (just notifications about creating print queues) and in cupsd (it is under cupsd systemd unit, but messages are from cups-browsed). All in attachments.
Created attachment 1411630 [details] cupsd log when job fails after waking up
Created attachment 1411631 [details] Troubleshooting output
My thoughts are that the issue is connected to implicitclass backend - all queues which experience the problem have this backend. Implicitclass backend is used when more than one machine provides the same print queue (I need to check this fact in our enviroment). So maybe the issue is connected to changing remote print queue's providers? But why cups-browsed doesn't react to this during browsing (like creating the new queue provided from different source)?
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
implicitclass is used by cups-browsed when it creates a printer. This causes cups to ask cups-browsed for where the printer actually is when it needs to print. And it seems there are certain conditions that cause cups-browsed to get stuck or stop responding to cups for some reason. I have a user that takes a laptop home to work in the evening and when she comes back in the morning, the printers don't work. I have turned on logging and I'll check tomorrow.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.