This is a hard one to describe. Everything worked fine until a recent update, with the most likely culprits being udev (from 104-r13 to 114) and sane-backends (from 1.0.18-r2 to 1.0.18-r4). After the update, printing no longer works (I have tried downgrading both of those packages and rebuilding cups, but that doesn't fix it). Whenever I attempt to print anything (even a test page), I get (endlessly): "Printer not connected; will retry in 30 seconds..." Note 1: This ONLY happens on multifunction devices. Regular printers still print fine. Note 2: My printers.conf file has a line: DeviceURI usb://EPSON/Stylus%20CX3700 If I change this line (manually - CUPS won't allow this change via the web interface) to: DeviceURI file://dev/usb/lp0 then everything will work fine again.
Maybe you can check where exactly the permission problem lies. First: You told you have a multifunction device. Does that also has scanner functions? If yes perhaps libsane rules catch you and change group of /dev/bus/usb/???/??? to group scanner - and sadly mode to 660 instead of 664 as it should be. To verify this: Does changing sane rules from MODE="660" to MODE="664" (or deleting MODE setting) helps?
(In reply to comment #1) > Maybe you can check where exactly the permission problem lies. > > First: You told you have a multifunction device. > Does that also has scanner functions? Indeed it does (Epson Stylus 3700). > If yes perhaps libsane rules catch you and change group of /dev/bus/usb/???/??? > to group scanner - and sadly mode to 660 instead of 664 as it should be. Both of those appear true. # ls -al /dev/usb/lp0 crw-rw---- 1 root scanner 180, 0 2007-09-20 21:53:20 /dev/usb/lp0 # ls -al /dev/bus/usb/002/ total 0 drwxr-xr-x 2 root root 80 2007-09-20 21:53:20 ./ drwxr-xr-x 5 root root 100 2007-09-02 12:50:49 ../ crw-rw-r-- 1 root usb 189, 128 2007-09-02 12:50:49 001 crw-rw---- 1 root scanner 189, 144 2007-09-20 21:53:20 017 > To verify this: Does changing sane rules from MODE="660" to MODE="664" (or > deleting MODE setting) helps? Before I tried this, I suspected that it would not (since I belong to the scanner group). Unfortunately, my suspicions proved correct. I did get 664 permissions (instead of the 660 shown above) after restarting everything, but I still could not print with the message "Printer not connected; will retry in 30 seconds..." as before.
Looks quite similar to this other one...
Is this Bug fixed with version sane-backends-1.0.18-r5?
(In reply to comment #4) > Is this Bug fixed with version sane-backends-1.0.18-r5? No. It behaves the same as before. I restarted cupsd and hald (do I need to restart anything else?).
(In reply to comment #5) > (In reply to comment #4) > > Is this Bug fixed with version sane-backends-1.0.18-r5? > > No. It behaves the same as before. I restarted cupsd and hald (do I need to > restart anything else?). > As you use older udev maybe you need to delete /etc/udev/rules.d/99-libsane.rules and run udevtrigger.
Somewhere between udevtrigger and udev-115 (and mayabe even gimp-print-5.1.3 with completely reinstalling the printer) it started working again, so I will close this (calling it "fixed" :) ). Thank you.
