Scanner does not work as user

[Jim Cornette]

Roland Wolters wrote:
> Once upon a time Sandy Pond wrote:
> 
>>On Mon, 2004-04-19 at 09:04 -0400, Sandy Pond wrote:
>>
>>>On Mon, 2004-04-19 at 07:45 +0200, Roland Wolters wrote:
>>>
>>>>Once upon a time Sandy Pond wrote:
>>>>
>>>>>chmod 777 $(sane-find-scanner | \
>>>>>            grep '^found USB scanner' | \
>>>>>            sed -e 's?^.*libusb:?/proc/bus/usb/?' -e 's?:?/?')
>>>>
>>>>Ok, now scnaimage finds it, thank you very much.
>>>>But xsane now gives me a I/O device error:
>>>>/Failed to open device libusb:003:002
>>>>\Error during I/O device.
>>>>
>>>>  :-(
>>>
>>>I don't have a mustek but I think you need to correct the config file
>>>in /etc/sane.d/mustek*
>>>
>>>I would guess adding a line like:
>>>
>>>usb libusb:003:002
>>>
>>>To the proper file ... but maybe it's not supported.
>>>
>>>Does xsane work as root?  If so then might be selinux.  Try xsane after
>>>running:
>>>
>>>setenforce 0
>>>
>>>:)
>>
>>Just checked ... xsane is badly broken with selinux enforcing ... turn
>>it off to use xsane.
> 
> 
> Well, I changed the mustek_usb.conf file (the device Message from xsane talks 
> about mustek_usb:libusb:003:002) from autodetect to the line above, but than 
> scanimage is unable ot recongnize it.
> If I start xsane with my tv card, I am able to "scan" pictures, so xsane alone 
> works.
> But setenforce 0 does not help, I typed it as root, tried to open xsane as 
> user, and got the same error as written in my old messages.
> 
> Roland
> 
> 

I doubt that this fact for my scanner will help you. I can scan if I use 
a Fedora Core 1 - 2.4 kernel. I have an HP ScanJet 2100C and don't need 
to edit anything to get it to work. I tried this with the Fedora Core 2 
version of xsane and did not have any problem. With the 2.6 kernel 
version, no dice, not recognized.
I figured that they changed some module from the 2.4 kernel to the 2.6 
kernel and have not made the needed changes to xsane and initscripts to 
get some of these scanners off of the "unemployment" roles.
With SELinux in the mix now, it might cause a lot of problems running a 
non-SELinux aware kernel, just to scan something.
Oh well! Maybe the scanners will be working for test3.

Jim