hi ! 
since many months i have a big bug between my scanner and xsane. 
in reality, since outgoing from ubuntu-mate 16.04; and again with 16.10. 
= nothing runs !! :( 

before that, my scanner was running fine since many many years. 
needed some adaptations like here : 
http://srimal-techdiary.blogspot.fr/2008/04/installing-epson-perfection-660-usb.html
 
but all was ok. 

just: it was.... now, i dont understand why nor whats happen :( 
all whats was, is not more :( 
i searched many and many hours on internet and the best {simplest, clearest for 
me} i found, are here : (sorry for the french ;) ) 
https://doc.ubuntu-fr.org/sane-backends 
https://doc.ubuntu-fr.org/scanner_usb_non_reconnu 

even if my scanner seems to be recognize = 
$ sane-find-scanner -q  gives back : 
found USB scanner (vendor=0x04b8 [EPSON], product=0x0114 [EPSON Scanner]) at 
libusb:005:002 
$ scanimage -L   makes the scanner in light but nothing more. 

i send you too the pages  *.conf from ' /etc/sane.d ' , if it could help you. 
if more are needed > ask me. 

what have you to explain to me to help for this problem, please ? 

i dont have money to buy a new scanner -_- only for that....... 
then, i wish very hard, its a solution for this. 

thanks for your answer as soon as possible :) 

sincerely yours
elis 
-- 
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
Et si on changeait la règle du jeu une bonne fois pour toutes?!!  

Attachment: dll.conf
Description: Binary data

Attachment: epson.conf
Description: Binary data

Attachment: epson2.conf
Description: Binary data

Attachment: epsonds.conf
Description: Binary data

Attachment: saned.conf
Description: Binary data

Attachment: snapscan.conf
Description: Binary data

Attachment: tail_058.bin
Description: Binary data

Attachment: tail_061.bin
Description: Binary data

-- 
sane-devel mailing list: [email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [email protected]

Reply via email to