Bug 2180752
| Summary: | cups reports: "The printer may not exist or is unavailable at this time" and the printer is permanently disabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Albert Flügel <af> |
| Component: | cups | Assignee: | Zdenek Dohnal <zdohnal> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | twaugh, zdohnal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-22 12:22:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Albert Flügel
2023-03-22 08:05:37 UTC
Hi, your print job failed: Mar 21 19:46:15 darkstar cupsd[867]: [Job 278] The printer is unreachable at this time. Mar 21 19:49:16 darkstar cupsd[867]: [Job 278] Unable to write print data: Broken pipe Mar 21 19:49:16 darkstar cupsd[867]: bunti alb 278 [21/Mar/2023:19:49:16 +0100] total 2 - localhost Document from - - Mar 21 19:49:16 darkstar cupsd[867]: [Job 278] Backend returned status 1 (failed) which disables the print queue by default - this is configurable by ErrorPolicy directive in cupsd.conf. The default is set like this to don't lose the job and prevent failures of other jobs in the queue - once user fixes the problem, he can reenable the queue, resubmits the job and the job and others in the queues get printed. (In reply to Albert Flügel from comment #0) > BTW. why was it necessary to abolish options BrowseRemoteProtocols etc., > that were even crucial in earlier versions ? They are no longer used by CUPS for various reasons - f.e. BrowseRemoteProtocol is removed from CUPS because there is only one way how to look for printers via a protocol - mDNS - and this is used everytime when there is avahi-daemon running. Btw the option was removed from cupsd.conf during cups-filters creation, more than 10 years ago. >And what does it mean "Printer > drivers are deprecated and will stop working in a future version of CUPS" ? > I've read the articla, but it is not getting clear to me, what is meant by > "driver" - for my perception a fuzzy term since the early days microsoft > called everything a "driver" that had to do with anything outside the os. Printer drivers are PPD files+filters+non-IPP backends. To keep it simple, the driver support is just moved from CUPS to printer applications, so in case you have to use a driver, you install the printer in printer application - CUPS is able to pick up the service which shared from the printer application. > And i want to know, how much effort went during the last 5 years into what > is going to be abolished thus breaking lots of existing setups. This effort lasts over 10 years and printer drivers and their CUPS PPD API are deprecated for most of that time. OpenPrintning and PWG groups did a great job with this - the whole printer application design was brought by them, so users don't have to throw away their old printers - and the groups made it while dealing supporting the current use cases. There are docs regarding how to find out whether your printer is capable of using driverless stuff - https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to_find_out_whether_my_printer_is_capable_of_driverless_printing and several user stories how to install printers nowadays https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to_install_a_print_queue . |