On Sat, 8 Jul 2006 12:43:45 -0400 Anthony Agelastos <[EMAIL PROTECTED]> wrote:
Hi, I just installed cups from ports and had a similar problem with printing. Normally I haven't got any problems. The printer is a HL-1430 connected to USB and the error I got was: 'Unable to open USB device "usb:/dev/unlpt0" Permission Denied.' Now I don't know if this is relevant in any way. After trying all kinds of solutions I finally decided to simply do "chmod 777 /dev/unlpt0", and that solved the problem. Best and kind regards, Rico > On Jun 29, 2006, at 6:51 PM, Jan-Espen Pettersen wrote: > > > > > > >> I just tried /dev/unltp0 and I have the same issues. Basically, I > >> killed all of the jobs, made your change, submitted a test page, > >> watched as nothing happened (it didn't display any messages in the > >> web > >> interface), did a /usr/local/etc/rc.d/cupsd restart, killed the test > >> page, then resubmitted one, and then it mentioned the USB busy will > >> retry in 30 seconds line. I reattached my error_log for today's > >> activities. > >> > >> I will be on the road for the better part of a week, so I will try to > >> help out as much as I can given the circumstances. Thank you everyone > >> for your assistance with this. > >> > >> > > > > I found that the usb backend stalled here before actually doing any > > work. Before I've done any actual debugging of the backend, I suspect > > that it is being blocked on a status read attempt, though this is only > > my current guess. > > > > Here is a workaround: > > > > In printers.conf () you will probably find a line like this: > > > > DeviceURI usb:/dev/ulpt0 > > > > change usb: to file:, so that it looks something like this: > > > > DeviceURI file:/dev/ulpt0 > > > > Then restart cups. Cups will not read any status information from the > > printer, but at least it can print. Be warned about unknown side > > effects. :) > > > > Jan-Espen Pettersen > > > > > > > I did this fix and it enabled the local server that has the printer > connected to it to print (a test page anyways) however, when I try to > print to the printer through the network via my MacBook Pro (which > worked before), I get the message in the CUPS Web Interface: > > "/usr/local/libexec/cups/filter/foomatic-rip failed" > > Basically, I have the same problem reported in the one-message-thread > "Can't print to CUPS from Macintosh". > > Does anyone have any ideas? The FreeBSD community has my appreciation > for all of its help on this matter. > > Based on the number of problems associated with this issue (there's > this thread, the aforementioned Mac thread, and the "cups 1.2 - no > output" thread), would it be worthwhile to create a new Port named > cups-devel (keeping the 1.2.x codebase) and downgrade the existing > cups to the latest 1.1.x version until the bugs have been ironed out > on the 1.2.x branch (or at least adding an entry to /usr/ports/ > UPDATING to warn those updating)? Would 1.2.1 fix these issues (that > is the current stable version whereas FreeBSD's CUPS is at 1.2.0), or > perhaps the 1.3svn branch? I am unsure where the current problems lay > (on the CUPS side, on how it is installed in the FreeBSD environment, > or on the FreeBSD environment itself). Earlier in this thread, the > issues were primarily related with permissions (since, it was > mentioned, CUPS is trying to run with a more reasonable set of > permissions instead of via 'root'), but now they appear to be > configuration specific. I am willing to try whatever is proposed to > help the developers get past these issues. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"