<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Sorry about that last post. Apparently I accidentally hit "send" before I intended to. Corrected and updated post follows:<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I had it, and I lost it.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After BR, Louis wrote:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"If /usr/lib64/sane is empty you probbly don;t have sane-backends-drivers-scanners installed: yum install sane-backends-drivers-scanners should solve your problem...."<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I followed his advice, ran "yum install sane-backends-drivers-scanners" and scanimage -L detected my Canon Canoscan N124OU. I left things alone for a couple of weeks, and when I came back to it I'm now back to getting "no scanners were identified". (Incidentally, I'm signed on as root). The only thing I did in the interim was move my home directory from the SSD, where Linux lives, to the RAID, which is much bigger. It's hard to see how that would effect scanimage, but what <span style='color:#1F497D'>d</span>o I know? FWIW, I'm pretty sure I got all the hidden files, etc, moved to the new location and got all the ownership and permissions the same as they were in the old location, which I have not deleted.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>I've more recently discovered that rebooting the server and </span>logging in <span style='color:#1F497D'>either </span>as root <span style='color:#1F497D'>or with my usual login </span>and <span style='color:#1F497D'>then </span>typing "scanimage -L" gives me, after a very long time, "device 'plustek:libusb:001:002 is a Canon CanoScan N1240U/LiDE30 flatbed scanner"<span style='color:#1F497D'>. </span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>However, </span>typing "scanimage -L" a second or third time gives me:<o:p></o:p></p><p class=MsoNormal>"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)."<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>sane-find-scanner still gives me:<o:p></o:p></p><p class=MsoNormal>found USB scanner (vendor=0x04a5 [Canon], product=0x220e [Canoscan] ) at libusb:001:002<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>regardless of whether it's the first run after rebooting or subsequent runs<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This observation scanimage -L gives different results on the first run after rebooting and subsequent runs may well account for the difference between the results I got immediately after installing sane-backends-drivers-scanners and those I saw more recently, with the business about moving my home directory being a red herring.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I'm currently doing some additional work comparing output of scanimage-L on first and subsequent runs after rebooting and setting environment variables <o:p></o:p></span></p><p class=MsoNormal>SANE_DEBUG_DLL=128 and <o:p></o:p></p><p class=MsoNormal>SANE_DEBUG_PLUSTEK=128<o:p></o:p></p><p class=MsoNormal>and will post the results once obtained<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>