Bill Davidsen wrote:
I believe scanning works, but I think it either "just works" or "never works," because no one seems to even have a suggestion of anything to try.
There used to be a lot of references and tricks needed to get scanners to work and settings needed in configuration files. Since every scanner I had to deal with worked, I did not need to learn how to configure a scanner. People have successfully configured the scanners. I am just glad that I did not need to undergo the hassle of configuring one. The problem with permissions when a program that controlled scanners was removed was enough fun.
People either say "it just worked for me" or "I never got it
working either," and a lack of process for debugging indicates a lack of understanding of process.
You might need to go into the process files regarding devices and set the permission for your scanner or adjust something in udev configuration. That was fun and now long forgotton on the specific tricks needed. 660 were needed permissions or something.
But after 3-4 scanners on many machines I'm willing to believe it's just luck when it does work, and if it doesn't you replace the scanner, computer, distribution, and USB cable and try again. ;-)
There has to be a rational reason and cause for your bad luck with the scanners you selected. The scanner utilities might help you diagnose the problem. Cycling power on my printer scanner does the trick for me.
Bug for my case. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213187 Jim
As noted, I need it working, there are no paths to get it working other than buying more scanners in hope that a miracle will occur, so I moved on.
-- In 1880 the French captured Detroit but gave it back ... they couldn't get parts.
