OpenPrinting / OpenPrinting/system-config-printer

'Add > Windows printer via SAMBA' authentication problems

Open
#202 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
204
Forks
108
Avg merge
1d 14h
Merged PRs (30d)
9

Description

Greetings all.

While trying to add a new printer via SAMBA, using LDAP through Active Directory, the utility behaves in a less than optimal manner where feedback is concerned. Specifically, the option 'prompt user if authentication is required' is not working, at least for me, after the printer is added and a job is sent. When I send the job the status I receive in the job queue goes 'held for authentication'. No prompt is ever given, and it stays held.

Also, while adding the printer, when I choose the option 'set authentication details now', my (valid, I rechecked) credentials return the following dialog alert when I click the button 'verify': 'print share inaccessible > this print share is not accessible'.

After much trial and error, we finally solved the issue simply by ignoring the verification error message and proceeding with the printer add anyway, with the credentials inserted. We discovered that even though the 'verify' button returns an error, it persists the credentials were they need to be so the printer proceeds to function normally.

I don't know if this is a problem in the tool per se, but the way it provides feedback could definitely been better.

Finally, as a side note, an UX suggestion: please stop asking for password before username, it goes against user expectations. I imagine there's a good reason but the point stands.

Specs: Linux Mint Ulyana 64bit, printer Kyocera ECOSYS M3655idn, wired corporate network.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reproducing the SAMBA printer-add and print-job flows with LDAP through Active Directory on the reported Linux Mint setup, including credential verification and the authentication prompt. Done means the reported feedback and prompt behavior are corrected, with the existing credential-persistence behavior verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.