Scanner suddenly stopped working [semi-SOLVED]

[eliddell]

I have an Epson CX4200 multifunction printer/scanner that was working perfectly under Gentoo as of Jan. 12, but when I tried to use it today, all attempts to scan failed silently.

sane-find-scanner and scanimage both still detect the device:

[BillWho]

eliddell,

Start the apps from the cl to see if it kicks any messages back.

[eliddell]

I did that, multiple times, both from my user account and as root. No messages.

[BillWho]

eliddell,

[eliddell]

I think it's odd, too—if I could just get it to generate an error message, I'd be off to the nearest search engine. :/

I run revdep-rebuild every time I update world. I may not have run it to completion last time, as I was having problems involving a couple of live ebuilds being out of sync with each other, but as far as I can tell, no relevant packages were updated at that time (unless you count either linux-headers or a rebuild of the version of cups I've had installed since November.).

udevadm monitor --udev gives the following:

[BillWho]

eliddell,

Unfortunately all the output is not a heck of a lot of help with this. One more thing to look at is what's getting picked-up with udev. This just simulates what took place when the device was detected.
You'll have to change the device address to your output.

root@gentoo-gateway linuxshared # udevadm test /devices/pci0000:00/0000:00:12.1/usb4/4-2 2>&1|grep libsane
parse_file: reading '/lib/udev/rules.d/41-libsane.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-libsane.rules' as rules file
udev_rules_apply_to_event: GROUP 102 /lib/udev/rules.d/41-libsane.rules:43
udev_rules_apply_to_event: MODE 0664 /lib/udev/rules.d/41-libsane.rules:43
udev_rules_apply_to_event: RUN '/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'' /lib/udev/rules.d/41-libsane.rules:1530
libsane_matched=yes

The line with 41-libsane.rules:43 corresponds to line 43 of /lib/udev/rules.d/41-libsane.rules - in this case it's the correct scanner at line 43. Line 1530 has to do with disabling USB autosuspend for the device. Maybe you can see what's happening with yours.

42 # Hewlett-Packard ScanJet 4100C
43 ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="0101", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

I would run this when the device doesn't work to see if the problem was with udev mixing up the scanner.

I wanted to buy a new printer/scanner because mine are aging, but I don't want one that I'm going to have problems with in linux.

Hope this helps

[eliddell]

Uninstalled iscan and the other applications suddenly started to work again (driver conflict, maybe)? This is suboptimal, but I guess I'll just have to live with kooka and xsane from now—they're better than nothing, which was what I had. :/