Rainer Heesen wrote:
[EMAIL PROTECTED] ~# echo test /dev/ulpt0
bash: /dev/ulpt0: Device busy
so I think it is not a cups problem, but what kind of program make the usb
device busy?
It can't be any other program if fstat is not reporting anything. I've
been reading on the usb printer
the permissions of /dev/ulp* are:
crw-rw 1 root cups0, 169 Jul 3 20:35 /dev/ulpt0
crw-rw 1 root cups0, 170 Jul 3 20:35 /dev/unlpt0
the directory /var/cache/cups is group writable
when I start a print job I get the message
printer Minolta now printing Minolta-59.
Rainer Heesen wrote:
the permissions of /dev/ulp* are:
crw-rw 1 root cups0, 169 Jul 3 20:35 /dev/ulpt0
crw-rw 1 root cups0, 170 Jul 3 20:35 /dev/unlpt0
the directory /var/cache/cups is group writable
when I start a print job I get the message
printer
Rainer Heesen wrote:
USB port busy; will retry in 30 seconds...
fstat | grep ulpt0
.. will reveal which process is eventually having ulpt0 open, and
causing 'device busy'.
The usb backend seems to get this error while trying to open /dev/ulpt0.
Please also make sure that either the
On Sunday 02 July 2006 16:50, Jan-Espen Pettersen wrote:
Rainer Heesen wrote:
USB port busy; will retry in 30 seconds...
fstat | grep ulpt0
.. will reveal which process is eventually having ulpt0 open, and
causing 'device busy'.
The usb backend seems to get this error while trying
