Hi!

I just upgrade cups to 1.1.21. But I don't think that is the issue here.

I am getting this error on my web interface (CUPS)


Printer State: idle, accepting jobs.
"unable to open print file "/var/spool/cups/d00117-001" - Permission denied"
Device URI: parallel:/dev/lp0

The printer shows that it receive some message from the comp cause the printer led start blinking and another one just lit up (normally it is not).

It is a HP Laserjet 2100TN.

What are the permissions and ownerships on /var/spool/cups/? Just a guess, but either the new cups is looking to a different place for it's spool directory than the old one did, or it's running as a different user.

-Bill

/var/spool/cups is rwx--x--- root root

Hmm.. other users do not have permission to read or write to eat. Strange.
should I change it? What should I change it to?

Well, just as a test, you could change the permissions on the directory to 0777 (rwxrwxrwx) and try printing, and see what happens. I wouldn't leave it set that way, but it might give a clue.

I think the next thing to check is what user cups is running as:

ps aux | grep cups

If that shows something other than "root", then you need to change the ownership of the directory to that user. If that does show "root", then I don't know what to look at next. I guess you'd have to start ferretting around in the cups configuration files. (Being an LPRng user, I can't help too much with those.)

As for the users spooling jobs into this directory, I think that is done via an entry in inetd.conf for cups-lpd. I would reckon this runs as the same user as cupsd. I suppose you could telnet to the printer port, and while that session is open, do the ps command above again, and make sure who it is running as.

-Bill

I changed it to +r with no success.

ps aux | grep cups
shows it running as root alright.

The other odd thing is that in /var/spool/cups there is no file which starts with d*
but all starts with c*

I guess I need to play around with /etc/cups/cupsd.conf. Will do that tomorrow. Getting late here.

Try changing it with "chmod 0777 /var/spool/cups". That will get you the write perms too.

-Bill

--BUMP--

Has this been solved? If so, what did the trick? I'm having the same problem all of a sudden...

Cheers, Leon.

Nope, haven't been resolve yet. Well work on it tonight since this isn't an isolated case now.

For me, the problem 'solved itself' after an upgrade of samba in Slack-current! WEEEHOOOOO!!! Printing again, what a relief ;-)
Still no clue what caused it though...

Cheers, Leon.

am able to print garbage now. sigh...

Have had a similar problem when first setting up the printing stuff. After figuring out the right Device URI in CUPS (http://localhost:631) that was solved.
I am printing over a LAN with the following syntax in cups:
The above is in Slack.
In Debian, I had to change it to
Hope this is of some help to you.

Cheers, Leon.