can't print until cups restart or job cancel

[vergnano]

Hello everyone,

I got the following problem: I print something, but it won't get printed until I either restart cups or cancel the job from cups interface. Sometimes it will print but it takes ages and I'm talking about very simple text documents, nothing really complicated.

Any ideas?

Thanks in advance

I thought it could be helpful to show you some logs:

/var/log/cups/error_log

E [02/Oct/2011:18:30:54 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:31:50 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported
E [02/Oct/2011:18:31:50 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:35:01 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported
E [02/Oct/2011:18:35:01 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:35:25 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported
E [02/Oct/2011:18:35:25 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:36:17 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported
E [02/Oct/2011:18:36:17 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:36:36 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported
E [02/Oct/2011:18:36:36 +0200] [Job 29] SpliX Cannot get input slot information.
E [02/Oct/2011:18:37:48 +0200] [Job 29] SpliX Cannot get input slot information.
W [02/Oct/2011:18:38:32 +0200] [Job 29] Remote host did not respond with data status byte
after 300 seconds!
W [02/Oct/2011:18:38:57 +0200] [Job 30] Remote host did not respond with data status byte
after 300 seconds!
W [02/Oct/2011:18:45:27 +0200] [Job 31] Remote host did not respond with data status byte
after 300 seconds!

/var/log/cups/access_log
localhost - - [02/Oct/2011:18:30:54 +0200] "POST /printers/Samsung-ML-1610 HTTP/1.1" 200 4
89 Create-Job successful-ok
localhost - - [02/Oct/2011:18:30:54 +0200] "POST /printers/Samsung-ML-1610 HTTP/1.1" 200 1
659873 Send-Document successful-ok
localhost - - [02/Oct/2011:18:34:49 +0200] "POST /printers/Samsung-ML-1610 HTTP/1.1" 200 4
3020 Print-Job successful-ok
localhost - - [02/Oct/2011:18:38:22 +0200] "POST /jobs HTTP/1.1" 401 137 Cancel-Job succes
sful-ok
localhost - - [02/Oct/2011:18:38:32 +0200] "POST /jobs HTTP/1.1" 200 136 Cancel-Job succes
sful-ok
localhost - - [02/Oct/2011:18:38:57 +0200] "POST /jobs HTTP/1.1" 200 136 Cancel-Job succes
sful-ok
localhost - - [02/Oct/2011:18:40:22 +0200] "POST /printers/Samsung-ML-1610 HTTP/1.1" 200 3
8652 Print-Job successful-ok

[djohnston]

"E [02/Oct/2011:18:31:50 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs
/0" - Operation not supported"

Not sure why the print procedure is trying to set access control lists on that file. It is read only and owned by root. The printer is a Samsung-ML-1610. What does your CUPS setup look like as far as who can access the printer? In other words, what users did you add to the list?

[vergnano]

Well, I just installed PCLinuxOS, installed my printer and that's all. There are two normal users and the root. Everyone can print, but I didn't specify anything about users in the CUPS setup.

I also did some more tests and it seems those files get printed, but it takes ages - about 5 minutes per 2 page pdf it's far too much for me.
If you need any more data to help, please tell me what should I provide.

[djohnston]

Check in Synaptic and see if packages acl and libacl1 are installed. (They probably are.)

Are you using a ppd driver supplied by Samsung or the cups-drivers-splix package from Synaptic?

Have you tried setting up the printer as ML-1710 instead? Sounds crazy, but my research showed that users with that printer only got it working by using the ML-1710 driver.

[vergnano]

I will check for packages. -> acl and libacl1 are installed

I use synaptic drivers.

I will try also to set it as 1710.

This is very weird.... I reinstalled the printer as 1710 and it works the same - the page remains stuck for ages (it will be eventually printed but after a very long time), unless I cancel the job. If I do that, everything gets printed immediately.