[SOLVED] Unable to authenticate samba printer

Jphillips · 2019-09-16 10:18:51

I'm trying to get a network samba printer working. So far I have installed cups, samba, smbclient, system-config-printer, and python-pysmbc. When search for the printer via clicking the "Browse" button in the smb uri field, I can successfully enter my credentials and find the printer. However, when I then select "Set authentication details now" and try to verify my username/pw, the same credentials now returns "Print share not accessible". What's weird too is that even if I click apply after entering my authentication details, it doesn't save this setting, so when I reopen the Device URI page to edit the device, it has defaulted back to "Prompt user if authentication is required".

When I try to print a test page the error returned is "Idle - Filter failed" and var/log/cups/error_log says "Job held for authentication". It also intermittently returns "[cups-deviced] PID 3710 (cups-brf) stopped with status 13!" and "[GI] Bad SNMP packet from 129.132.221.2: variable-bindings uses indefinite length", though these latter two errors occur regardless of if I'm trying to print.

Lastly, when I open the print queue, I can see the Test Page listed, with the status "Held for authentication." But when I right-click and select "Authenticate" nothing happens, so I am unable to authenticate.

Any thoughts on what's going on or how to troubleshoot this?

EDIT:

As noted in my post below, I found a temporary workaround. In the file /etc/cups/printers.conf the authorization for the printer was set to:

AuthInfoRequired none

I changed this to:

AuthInfoRequired username,password

And it now prompts me to enter my credentials when I print something, and it prints without issue. Apparently this will revert to "none" on restart https://bbs.archlinux.org/viewtopic.php?id=245658, although I haven't checked whether this is the case.

EDIT#2:

This change appears to be sticking across restarts. I still do have to go to the queue and manually authenticate a new print task, but able to authenticate it without issue, and the changes to /etc/cups/printers.conf are sticking.

Last edited by Jphillips (2019-09-18 08:19:07)

Jphillips · 2019-09-16 11:19:06

Just to give a bit more detail, when I open the printer setting dialog via:

sudo system-config-printer

I then right click to open the print queue, right click to authenticate the Test Page print, and these errors show up in the terminal:

(system-config-printer:1879): libnotify-WARNING **: 13:13:22.600: Failed to connect to proxy

(system-config-printer:1879): GLib-GIO-CRITICAL **: 13:13:27.422: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(system-config-printer:1879): GLib-GIO-CRITICAL **: 13:13:27.424: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Traceback (most recent call last):
  File "/usr/share/system-config-printer/jobviewer.py", line 1620, in on_job_authenticate_activate
    uri, auth_info_required, True)
  File "/usr/share/system-config-printer/jobviewer.py", line 1110, in get_authentication
    self.display_auth_info_dialog (job, keyring_attrs)
  File "/usr/share/system-config-printer/jobviewer.py", line 1114, in display_auth_info_dialog
    auth_info_required = data['auth-info-required']
KeyError: 'auth-info-required'
Traceback (most recent call last):
  File "/usr/share/system-config-printer/jobviewer.py", line 94, in on_get_service
    service = Secret.Service.get_finish(result)
gi.repository.GLib.Error: g-spawn-exit-error-quark: Error spawning command line “dbus-launch --autolaunch=60c539077fa746a6822eadb11c6c79ad --binary-syntax --close-stderr”: Child process exited with code 1 (1)
Traceback (most recent call last):
  File "/usr/share/system-config-printer/jobviewer.py", line 94, in on_get_service
    service = Secret.Service.get_finish(result)
gi.repository.GLib.Error: g-spawn-exit-error-quark: Error spawning command line “dbus-launch --autolaunch=60c539077fa746a6822eadb11c6c79ad --binary-syntax --close-stderr”: Child process exited with code 1 (1)

seth · 2019-09-16 13:45:24

You're trying to add a printer to the arch machine using the smb protocol to access a device that's probably shared by a windows host?

a) cut out that systray-widget-thingy and use "localhost:631" to configure the printer (if using a GUI at all)
b) most likely https://askubuntu.com/questions/915828/ … -smb-share

Jphillips · 2019-09-17 07:27:48

I was able to fix the problem, though I don't quote know why it arose. In the file /etc/cups/printers.conf the authorization for the printer was set to:

AuthInfoRequired none

I changed this to:

AuthInfoRequired username,password

And it now prompts me to enter my credentials when I print something, and it prints without issue.

seth · 2019-09-17 07:32:07

There was https://bbs.archlinux.org/viewtopic.php?id=245658 but it's unresolved. Prepare for the setting to reset on reboot.
Otherwise please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2019-09-16 10:18:51

[SOLVED] Unable to authenticate samba printer

#2 2019-09-16 11:19:06

Re: [SOLVED] Unable to authenticate samba printer

#3 2019-09-16 13:45:24

Re: [SOLVED] Unable to authenticate samba printer

#4 2019-09-17 07:27:48

Re: [SOLVED] Unable to authenticate samba printer

#5 2019-09-17 07:32:07

Re: [SOLVED] Unable to authenticate samba printer

Board footer