This bug was initially created as a copy of Bug #2071417 I am copying this bug because: Description of problem: 30-second delay occurs after print job is submitted to Windows Server 2016 via HTTPS (IPPS). The delay occurs after the print job is submitted and prevents the next job from being started. Adding "waitjob=false" to the Device URI has no effect. This issue does not occur when using HTTP on port 80. As the issue only happens when using TLS, this may actually be an issue with gnutls, not CUPS. How reproducible: 100% Steps to Reproduce: 1. Stand up a Windows server with - IPP support for printing - A valid TLS certificate - A print queue connected to LPT1: with any driver (queues that send jobs to files won't work) 2. Pause the print queue so Windows doesn't actually try to send anything to LPT1:. 3. Create a print queue on a CUPS server to send jobs to the queue on the Windows server: lpadmin -p test -m raw -v https:/<winsrv>:443/printers/<queue>/.printer?version=1.0 -E (Windows only supports IPP/1.0, and badly at that.) 4. Send two jobs to the queue on the CUPS server: lp -d test /etc/fstab; lp -d test /etc/fstab Actual results: The first job is sent to the Windows server immediately, but takes 30 seconds to complete, so the second job is delayed by 30 seconds. Expected results: The first job should complete within 1-2 seconds and then the second job should be processed.
FEDORA-2022-7a4ad08008 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a4ad08008
FEDORA-2022-6c661ccfe0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6c661ccfe0
FEDORA-2022-7e5d0094ef has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7e5d0094ef
FEDORA-2022-7a4ad08008 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7a4ad08008` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a4ad08008 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6c661ccfe0 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6c661ccfe0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6c661ccfe0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-7e5d0094ef has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7e5d0094ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7e5d0094ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6c661ccfe0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-7e5d0094ef has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-7a4ad08008 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.