[arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

[Rodrigo Rivas]

On Fri, Feb 22, 2013 at 11:49 AM, Mike Cloaked <mike.cloaked at gmail.com>wrote:

> On Thu, Feb 21, 2013 at 10:32 PM, Rodrigo Rivas <
> rodrigorivascosta at gmail.com
> > wrote:
>
> > On Thu, Feb 21, 2013 at 9:17 PM, Mike Cloaked <mike.cloaked at gmail.com
> > >wrote:
> >
> > > I am stuck on the configuration of the scanner functionality for a
> > Samsung
> > > SCX-4500W multifunction printer/scanner.
> > >
> > > I can get the printing function of this printer to work by the
> following
> > > steps:
> > >
> > > 1) Add a line to /etc/udev/rules.d/70-usbprinter.rules containing:
> > > ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0660",
> > GROUP:="lp"
> > >
> > >
> > I have a SCX-4200 MFP, quite similar to yours, and this is my udev rule:
> >
> > ATTR{idVendor}=="04e8", ATTR{idProduct}=="341b", MODE:="0660",
> GROUP:="lp",
> > ENV{libsane_matched}:="yes"
> >
> > The product is different, obviously, but note the added environment
> > variable. I cannot remember why I put it there, but hey! there it is, and
> > it works.
> >
> > $ scanimage -L
> > device `xerox_mfp:libusb:002:002' is a SAMSUNG ORION multi-function
> > peripheral
> >
> >
> Thanks Rodrigo,
>
> I tried adding in the additional environment variable and rebooted the
> machine - when I do:
>  $ scanimage -L
> device `xerox_mfp:libusb:001:006' is a Samsung Samsung SCX-4500W Series
> multi-function peripheral
>
> But if I do it again then:
>
> scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
>
> So it is still not working - when I went to the GIMP and tried to create a
> scan it hung GIMP after not finding any scanner devices.
>
> Plus journalctl -xn has:
> Plus journalctl:
> Feb 22 10:35:04 home1 systemd[1]: configure-printer at usb-001-006.service:
> main process exited, co
> Feb 22 10:35:04 home1 colord[365]: Device added:
> sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_S
> Feb 22 10:35:04 home1 udev-configure-printer[2919]: add usb-001-006
> Feb 22 10:35:04 home1 udev-configure-printer[2919]: device devpath is
> /devices/pci0000:00/0000:0
> Feb 22 10:35:04 home1 udev-configure-printer[2919]: Device already handled
> Feb 22 10:35:04 home1 udev-configure-printer[2920]: add usb-001-004
> Feb 22 10:35:04 home1 systemd[1]: Unit
> configure-printer at usb-001-006.serviceentered failed stat
> Feb 22 10:35:04 home1 udev-configure-printer[2920]: no device named
> /dev/bus/usb/001/004 found
> Feb 22 10:35:04 home1 systemd[1]: configure-printer at usb-001-004.service:
> main process exited, co
> Feb 22 10:35:04 home1 systemd[1]: Unit
> configure-printer at usb-001-004.serviceentered failed stat
>
> So clearly I am missing something in the configs somewhere - but I don't
> know where to look next?
>


That's weird... I don't have any of these. No udev-configure-printer,
configure-printer at .service... nothing like that. Where did all of these
come from?

Other than that, I have the more or less standard configuration for the
printer in cups, but that should not make much of a difference.

A quick test... you are  member of the `lp` group, aren't you?

Another one... something strange in `dmesg`?