Epson Scanner/Printer recognized but "not connected"

[Igor Bujna]

Hello,
problem is where this port is blocked in version 1.2.2 and newer how its write in CHANGES.txt:
    - The USB backend now reports a "no such device" error
      when using the old filename-based USB URIs instead of
      the "success" error.

I think it's no good idea because every documentation where is installing usb printer in cups is this "DeviceURI usb:/dev/usb/lp0".
Or if i have raw printing to usbprinter and i everyday change printer model on usb i will must put this new printer to cups but i won't this.
I make this patch to downgrade this problem from older version....

--- backend/usb-unix.c~ 2007-02-20 14:41:07.000000000 +0100
+++ backend/usb-unix.c  2007-04-01 18:50:15.000000000 +0200
@@ -310,6 +310,7 @@
     * Do not allow direct devices anymore...
     */

+   return (open(uri + 4, O_RDWR | O_EXCL));
     errno = ENODEV;
     return (-1);
   }




> > Some days ago I updated cups to 1.2.6 (1.2.7 is not yet marked stable on Gentoo), and now my Epson Stylus Photo RX420 scanner/printer combo doesn't print anymore. Scanning works fine.
> > I can install the printer without any problems, it is automatically recognized during installation, but when it comes to printing, no matter what, it doesn't work, not even a "cat file.txt | lpr".
> >
> > When accessing the cups daemon via webbrowser, cups starts processing the file to be printed, but complains about "Printer not connected; will retry in 30 seconds..."
> >
> > I switched to "debug" in the config, but that only flooded my terminal with debug messages within seconds. If you need some info of this kind just ask.
> >
> > One thing which looks somewhat weird is the URI of the printer:
> > usb://EPSON/Stylus%20Photo%20RX420
> > Before I reinstalled the printer, it was /dev/usb/lp0.
> >
> > I'm using the gutenprint 5.0.0 driver and a vanilla 2.6.18 linux kernel.
> >
> > I hope someone can give me some advice on this.
>
> OK, using version 1.1.23-r8 (Gentoo version) works out of the box, 1.2.7 gives me the same problems as 1.2.6.
> Anyone a clue?