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