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

[Rodrigo Rivas]

On Fri, Feb 22, 2013 at 9:04 PM, Mike Cloaked <mike.cloaked at gmail.com>wrote:

> On Fri, Feb 22, 2013 at 7:19 PM, Rodrigo Rivas
> <rodrigorivascosta at gmail.com>wrote:
>
> >
> >
> > > 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`?
> >
>
> Yes I am a member of both lp and scanner groups.  The lines in messages.log
> are for example:
>
> Feb 22 19:39:26 localhost kernel: [32142.463787] usblp 3-4:1.1: usblp0: USB
> Bidirectional printe
> r dev 8 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B
> Feb 22 19:39:26 localhost colord: Device added:
> sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_Se
> ries
> Feb 22 19:39:26 localhost systemd[1]: Starting Printer.
> Feb 22 19:39:26 localhost systemd[1]: Reached target Printer.
> Feb 22 19:39:26 localhost systemd[1]: Starting Configure Plugged-In
> Printer...
> Feb 22 19:39:27 localhost systemd[1]: Started Configure Plugged-In Printer.
> Feb 22 19:39:27 localhost systemd[1]: configure-printer at usb-003-008.service
> :
> main process exited
> , code=exited, status=1/FAILURE
> Feb 22 19:39:27 localhost systemd[1]: Unit
> configure-printer at usb-003-008.service entered failed
> state
>
> I am wondering now whether this is a problem with a systemd service file
> possibly?  The printer part works. Just the scanner that doesnt.
> By the way there is a bug in cups awaiting the version 1.6.2 which I
> "fixed" by removing the offending line in cupsd.conf as per:
>
> https://bugs.archlinux.org/task/32768
>
> I also tried with and without the file in /etc/udev/70-libsane.rules
> containing:
> ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0660",
> GROUP="scanner",  ENV{libsane_matched}="yes"
>
> Behaves the same with that included or not.
>
> --
> mike c
>

Well, it looks like your systemd services come from packages
"system-config-printer" and "cups-pk-helper", and I have none installed.
You can try disabling or uninstalling them and see if it makes any
difference.

Other than that, I'm out of ideas, sorry.

-- 
Rodrigo