Description of problem:
Authentication dialog in print job list for network printer has no inputs whatsoever
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up a network printer via SMB in CUPS, e.g. something like smb://printserver/queue which requires authentication
2. Try to print a document
3. The job is held for authentication. Upon opening authentication pop-up dialog in print job list it shows empty without any input fields.
The printout is held for authentication.
A popup asking for Windows username and password should be shown and the printout should be sent to the printer by using these authentication information.
If I change `AuthInfoRequired negotiate` => `AuthInfoRequired username,password` in `/etc/cups/printers.conf`, I am able to authenticate next print job correctly, but after that cups changes the settings back and problem repeats.
Even if dialog works correctly, it seems silly to be forced authenticate every print job. There should be an option to save credentials. I also tried to fill credentials into DeviceURI (e.g. `smb://domain\username:password@printserver/queue`), did not work any better.
My /etc/cups/printers.conf is as follows:
# Printer configuration file for CUPS v2.2.11
# Written by cupsd on 2019-05-31 16:18
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
MakeModel KONICA MINOLTA C360SeriesPS(P)
JobSheets none none
This is an issue in samba package. It returns the "negotiate" in AuthInfoRequired. The version of samba in Fedora 29 worked so I tried to find the commit which caused this.
It is a set of related commits:
If I revert them in Fedora 30 then the dialog shows the fields.
I made a scratch build of samba with the commits reverted here: https://koji.fedoraproject.org/koji/taskinfo?taskID=35458274
I'm reassigning this to samba.
I can not upgrade to Fedora 31 due to this bug as even upgrading samba in F29 I am unable to print through my windows computer due to this bug.
Is it expected to be solved in Fedora 33?
Accepted as a Prioritized Bug: https://meetbot.fedoraproject.org/fedora-meeting/2020-02-12/fedora_prioritized_bugs_and_issues.2020-02-12-16.00.log.html#l-55
Can you re-test with the latest available update for f30 (samba 4.10.14) ?
We (Andreas and me) tend to believe that the issues with smbspool are resolved in that release.
(In reply to Guenther Deschner from comment #4)
> Can you re-test with the latest available update for f30 (samba 4.10.14) ?
> We (Andreas and me) tend to believe that the issues with smbspool are
> resolved in that release.
I am sorry, but at the moment I am unable to try replicate the problem under same conditions as this particular samba printer is placed at my workplace. And due to covid19 quarantine I work entirely from home, where I do not have printer at all.
Setting to ON_QA since a fix is released, but not confirmed. If some is able to test and verify, I will close it.
As I can not go to my office due to lockdown I can not check the fix. Will report when available.
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.
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 30 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.
After upgrading to Fedora 32, I'm still having problems. Browsing to:
and selecting my printer, then maintenance, print test page, I see:
Fri 01 May 2020 09:56:50 AM CDT
"Connection failed: NT_STATUS_CONNECTION_DISCONNECTED"
I was never offered an opportunity to enter in a username or password (although my particular samba server was set up for password-less printing). Meanwhile, Windows machines in my subnet have no problem printing to the same samba server. I'd welcome any advice on what troubleshooting steps I can take to help you fix this.
Guenther and Andreas, does the report in comment 9 seem like the same issue?
Ben, no, I don't think so it is the same issue Eric is seeing in comment #9
Re-setting version and status fields based on comment 11.
Agreed in today's Prioritized Bugs meeting that unless the original behavior can be confirmed to *not* be fixed in update FEDORA-2020-a1eacf6355, by the 20 May prioritzed bugs meeting, we will close this bug as resolved.
Eric, I encourage you to file a new bug about the behavior you reported in comment 9.
Per comment #12, I am closing this bug.
For me it seems to be working just fine after upgrade.
Thanks Jan, for providing the feedback!