<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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><p class=MsoPlainText>Hi Olaf,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Yes, I tried running scanimage -L when logged on as root with the same result i.e. "No scanners were identified...."<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Since my original post I made an observation which may or may not be relevant. >From the Centos 7.0 man page for plustek, <a href="https://www.unix.com/man-page/centos/5/sane-plustek/">https://www.unix.com/man-page/centos/5/sane-plustek/</a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"FILES<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>/etc/sane.d/plustek.conf<o:p></o:p></p><p class=MsoPlainText>The backend configuration file<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>/usr/lib64/sane/libsane-plustek.a<o:p></o:p></p><p class=MsoPlainText>The static library implementing this backend.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>/usr/lib64/sane/libsane-plustek.so<o:p></o:p></p><p class=MsoPlainText>The shared library implementing this backend (present on systems that support dynamic loading)."<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On my system I'm seeing /etc/sane.d/plustek.conf but /usr/lib64/sane is empty. I've seen something somewhere that says if sane-find-scanner finds the scanner but scanimage -L does not it means that you don't have the right backend for the scanner installed. Could a missing library file be the culprit?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I should mention that, if it is not already obvious, I'm a relative Linux newbie. As always, any suggestions appreciated.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<o:p></o:p></p><p class=MsoPlainText>From: Olaf Meeuwissen [<a href="mailto:paddy-hack@member.fsf.org">mailto:paddy-hack@member.fsf.org</a>]<o:p></o:p></p><p class=MsoPlainText>Sent: Saturday, October 27, 2018 11:40 PM<o:p></o:p></p><p class=MsoPlainText>To: Terry Spearman<o:p></o:p></p><p class=MsoPlainText>Cc: <a href="mailto:sane-devel@alioth-lists.debian.net">sane-devel@alioth-lists.debian.net</a><o:p></o:p></p><p class=MsoPlainText>Subject: Re: [sane-devel] sane-find-scanner finds Canon Canoscan N24OU, scanimage -L does not<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Hi Terry,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Terry Spearman writes:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> I'm running under Centos 7 (kernel 3.10.0-862.14.4.e17x86_64) and the <o:p></o:p></p><p class=MsoPlainText>> version of SANE I downloaded from the Centos repository via yum install.<o:p></o:p></p><p class=MsoPlainText>> When I run sane-find-scanner -v -v it tells me "found USB scanner<o:p></o:p></p><p class=MsoPlainText>> (vendor=0x0a9 [Canon], product= 0x220e [CanoScan] at libusb:001:002", <o:p></o:p></p><p class=MsoPlainText>> but, after checking several possibilities, says: <Couldn't determine <o:p></o:p></p><p class=MsoPlainText>> the type of USB chip (result from sane-backends 1.0.24)>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Device reported as completely supported with 1.0.24, so should work.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> Running scanimage -L tells me "No scanners were identified.....".<o:p></o:p></p><p class=MsoPlainText>> [...]<o:p></o:p></p><p class=MsoPlainText>> I'm pretty much out of ideas. Any and all suggestions gratefully <o:p></o:p></p><p class=MsoPlainText>> received<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Have you tried with root permissions? The user trying to scan needs read and write access to the device.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Hope this helps,<o:p></o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27<o:p></o:p></p><p class=MsoPlainText> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9<o:p></o:p></p><p class=MsoPlainText> Support Free Software <a href="https://my.fsf.org/donate">https://my.fsf.org/donate</a><o:p></o:p></p><p class=MsoPlainText> Join the Free Software Foundation <a href="https://my.fsf.org/join">https://my.fsf.org/join</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>