Bug 1581481
| Summary: | Printing to SMB server gives URI error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Ryans <r.ryans> | ||||
| Component: | samba | Assignee: | Guenther Deschner <gdeschner> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | abokovoy, anoopcs, asn, gdeschner, jarrpa, jpopelka, lmohanty, madam, massi.ergosum, sbose, ssorce, 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: | |||||||
| : | 1686158 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-05-28 23:45:14 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1686158 | ||||||
| Attachments: |
|
||||||
Hi Robert, thank you for reporting this issue! This error message seems to come from smb backend, which is part of samba package. I'll reassign the issue to samba. I'm having the same issue when I use credentials for Samba authentication. As a workaround I need to stop cups.service, add manually the line "AuthInfoRequired username,password" in my /etc/cups/printers.conf file, and then start the service again. Update: my "No valid device URI" problem could be caused by the package samba-krb5-printing. I suspect this wrapper doesn't send a valid URI to smbspool. Solved by removing the package. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. |
Created attachment 1440323 [details] CUPS error_log output for a sample failed job Description of problem: I have been successfully using Fedora 26 systems, bound to our AD server, to print to our shared printers which are hosted on a Windows Server system. After installing Fedora 28 I am unable to print, with each job crashing with a report of "No valid device URI has been specified" The printer URI is the same as in Fedora 26, and the print queue is being configured using the same playbook. I can submit a print job using smbclient, and smbspool works fine if the standard URI is specified in an environment variable. Version-Release number of selected component (if applicable): cups-2.2.6-14.fc28.x86_64 How reproducible: Always. Steps to Reproduce: 1. Configure print queue using lpadmin, specifying the printer URI in the form smb://print-server.our.domain/Staff%20Mono 2. Attempt to print to this printer from AD account which has valid kerberos ticket Actual results: Printing fails with error about no valid device URI being specified. Expected results: Print job should be accepted by server, as it was in Fedora 26, and is when using smbclient or smbspool. Additional info: CUPS error_log output attached.