cupsdauthorize: no authentication data provided; debian, gnome, epson stylus d120

WorkingClassHero · 03-16-2008, 06:33 AM

Hello,

I'm running debian lenny with gnome. My attempt to get my new printer, epson stylus d120, working failed. Below is the /var/log/cups/error_log output. The problem is probably related to the lines at the end with "no authentication data provided."
I don't know how to authorize my printer. There is some warning about avahi at the beginning, but I suppose these can be ignored.

Thanks for your help

avahi stuff seems to be installed:

Code:

dpkg -l|grep libavahi-compat
ii  libavahi-compat-howl0                0.6.22-2                     Avahi Howl compatibility library
ii  libavahi-compat-libdnssd1            0.6.22-2                     Avahi Apple Bonjour compatibility library

The beginning from /var/log/cups/error_log

Code:

I [16/Mar/2008:12:10:39 +0100] Saving job cache file "/var/cache/cups/job.cache"...
I [16/Mar/2008:13:11:48 +0100] Listening to :::631 (IPv6)
I [16/Mar/2008:13:11:48 +0100] Listening to 0.0.0.0:631 (IPv4)
I [16/Mar/2008:13:11:48 +0100] Listening to /var/run/cups/cups.sock (Domain)
I [16/Mar/2008:13:11:48 +0100] Loaded configuration file "/etc/cups/cupsd.conf"
I [16/Mar/2008:13:11:48 +0100] Using default TempDir of /var/spool/cups/tmp...
I [16/Mar/2008:13:11:48 +0100] Configured for up to 100 clients.
I [16/Mar/2008:13:11:48 +0100] Allowing up to 100 client connections per host.
I [16/Mar/2008:13:11:48 +0100] Using policy "default" as the default!
I [16/Mar/2008:13:11:48 +0100] Full reload is required.
I [16/Mar/2008:13:11:48 +0100] Loaded MIME database from '/usr/share/cups/mime:/etc/cups': 36 types, 40 filters...
D [16/Mar/2008:13:11:48 +0100] Loading printer Stylus-Color-Series...
*** WARNING *** The program 'cupsd' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=cupsd>
W [16/Mar/2008:13:11:48 +0100] DNS-SD registration of "Stylus-Color-Series" failed with -65537
I [16/Mar/2008:13:11:48 +0100] Loading job cache file "/var/cache/cups/job.cache"...

The end of /var/log/cups/error_log. The cupsdAuthorize messages are repeated periodically.

Code:

D [16/Mar/2008:12:28:56 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:28:56 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:28:56 +0100] CUPS-Get-Printers
D [16/Mar/2008:12:28:56 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:28:56 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:28:56 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:28:56 +0100] Get-Printer-Attributes ipp://localhost/printers/Stylus-Color-Series
D [16/Mar/2008:12:28:56 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:01 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:01 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:01 +0100] CUPS-Get-Printers
D [16/Mar/2008:12:29:01 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:01 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:01 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:01 +0100] Get-Printer-Attributes ipp://localhost/printers/Stylus-Color-Series
D [16/Mar/2008:12:29:01 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:06 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:06 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:06 +0100] CUPS-Get-Printers
D [16/Mar/2008:12:29:06 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:06 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:06 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:06 +0100] Get-Printer-Attributes ipp://localhost/printers/Stylus-Color-Series
D [16/Mar/2008:12:29:06 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:11 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:11 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:11 +0100] CUPS-Get-Printers
D [16/Mar/2008:12:29:11 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:11 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:11 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:11 +0100] Get-Printer-Attributes ipp://localhost/printers/Stylus-Color-Series
D [16/Mar/2008:12:29:11 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:16 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:16 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:16 +0100] CUPS-Get-Printers
D [16/Mar/2008:12:29:16 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)
D [16/Mar/2008:12:29:16 +0100] cupsdReadClient: 9 POST / HTTP/1.1
D [16/Mar/2008:12:29:16 +0100] cupsdAuthorize: No authentication data provided.
D [16/Mar/2008:12:29:16 +0100] Get-Printer-Attributes ipp://localhost/printers/Stylus-Color-Series
D [16/Mar/2008:12:29:16 +0100] cupsdProcessIPPRequest: 9 status_code=0 (successful-ok)

WorkingClassHero · 03-16-2008, 05:30 PM

Ok, this seemed to be some driver issue.
The driver debian recognizes automatically does not work. (maybe it does not work at all or there has to be done some additional configuring which I could not figure out)
The driver has no d120 specific name, but is called something like epson stylus color or epson stylus color new or sth. like that, I forgot. To get it working:
apt-get install cupsysdriver-gutenprint
Since there is no d120 listed, I chose the latest epson -d model available, this was d88 for me.

Cheers

jschiwal · 03-16-2008, 09:59 PM

With an earlier version of openSuSE, 10.1 if memory serves, I had a problem using the cups web configuration interface. I added my name and password using "lppasswd" to resolve the problem. After pointing a web browser to "https://localhost:631" I entered in my own credentials. With later versions of SuSE, I just need to enter root/password at the pop up authentication dialog. The "lppasswd" program works just like "smbpasswd".

Also, check the ownership & permissions of /dev/lp0. It should be owned by root with a group ownership of lp. If it isn't check if the dbus & had daemons are running. If they aren't, one possible reason is if you boot with the "noacpi" kernel boot option.

I took a look in my cups.conf file and was surprised to find XML entries when I was expecting name value ... styled entries. There is a <Policy .. Policy/> in it but I don't know if this relates to polkit or not. I use hplip on my system.

For comparison if it will help:

Code:

# Set the default printer/job policies...
<Policy default>
  # Job-related operations must be done by the owner or an adminstrator...
  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscri
ption Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  # All administration operations require an adminstrator to authenticate...
  <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New
-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedul
e-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default
>
    AuthType Basic
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  <Limit All>
    Order deny,allow
  </Limit>
</Policy>

Some of these policies relate to starting, stop and pausing jobs, which is the sort of thing that you are getting the cupsdAuthorize errors on, so I thought you could look at that. Does your system use policy kit to enable users to do things with devices?