[sane-devel] saned: Permission problem on Fedora 8, Deskjet_F300_series all-in-one

2008-01-03 Thread Nick Urbanik
Dear Folks,

I am having problems setting up saned on Fedora 8:
$ grep sane /var/log/rpmpkgs
libsane-hpaio-2.7.7-6.fc8.i386.rpm
sane-backends-1.0.18-17.fc8.i386.rpm
sane-backends-devel-1.0.18-17.fc8.i386.rpm
sane-backends-libs-1.0.18-17.fc8.i386.rpm
sane-frontends-1.0.14-3.fc7.i386.rpm
xsane-0.994-4.fc8.i386.rpm
xsane-gimp-0.994-4.fc8.i386.rpm

I've created user and group saned.
$ grep saned /etc/passwd
saned:x:1020:1021:User to run saned scanner daemon only:/:/sbin/nologin

When I do:
$ sudo -u saned sane-find-scanner |grep ^found
found USB scanner (vendor=0x03f0, product=0x5511) at libusb:003:004
However, as myself, we also get the model information:
$ sane-find-scanner |grep ^found
found USB scanner (vendor=0x03f0 [HP], product=0x5511 [Deskjet F300 series]) at
+libusb:003:004
$ scanimage -L
device `hpaio:/usb/Deskjet_F300_series?serial=CN72FGM1CB04KH' is a 
Hewlett-Packard Deskjet_F300_series all-in-one
And as the saned user, we get no biscuit:
$ sudo -u saned scanimage -L

No scanners were identified.

Here are the permissions:
$ ls -l /proc/bus/usb/003/004
-rw-r--r-- 1 root root 147 2008-01-03 06:21 /proc/bus/usb/003/004
$ cat /selinux/enforce 0

local scanning works fine for me.
All updates applied.

I'd be grateful for any suggestions.
-- 
Nick Urbanik  http://nicku.org  nicku at nicku.org
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080103/bb1ad369/attachment.pgp
 


[sane-devel] Canon LiDE 90

2008-01-03 Thread Guillaume Gastebois
Thank you Ralf,

But LiDE 60 PID only appears 2 times in genesys_devices.c and 1 time in
genesys.conf.in I still change them and no result (scanimage -L return LiDE 90
but can't move or turn on led with scanimage toto.pnm!!)

For help I did a usbsnoop and with a usbsnoop2libusb.pl a .c file. Maybe it can
help you (or others). You can find then to :
http://ggastebois.free.fr/lide90_snoop

Regards

Guillaume



[sane-devel] Another avision bug in current CVS : blue scans with HP 5300C

2008-01-03 Thread Julien BLACHE
Hi,

Another avision bug, this time with an HP 5300C producing only
all-blue scans (see below).

Feel free to contact the submitter directly, address  details at
http://bugs.debian.org/458932.

 After upgrading from 1.0.19~cvs20071028-1 to 1.0.19~cvs20071213-1 all scans
 are blue. http://izac.free.fr/image-1.0.18-5.ppm is a correct image using
 libsane-1.0.18-5 and http://izac.free.fr/image-1.0.19~cvs20071213-1.ppm
 is the same with libsane-1.0.19~cvs20071213-1 (warning: images are raw
 output of scanimage and sizes are about 6.5 MB). Outputs of ``scanimage
 -v'' are the same with both versions.

 % scanimage -L
 device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 5300C flatbed
 scanner

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - jblache at debian.org 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



[sane-devel] Formulardaten

2008-01-03 Thread cgi-mai...@kundenserver.de


===
== Neuer Eintrag
===

  
---
-- Formular: 'adddev'
---

1. Your email address:
   'carter.r.a.l at gmail.com'
2. Manufacturer (e.g. Mustek):
   'Epson'
3. Model name (e.g. ScanExpress 1200UB):
   'Perfection V500 PHOTO'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   '0x04b8'
6. Product id (e.g. 0x0002):
   '0x0130'
7. Chipset (e.g. lm9831):
   ''
8. Comments (e.g. similar to Mustek 1234):
   'New model.'
9. Data (e.g. sane-find-scanner -v -v):
   '
device descriptor of 0x04b8/0x0130 at 005:008 (EPSON EPSON Scanner)
bLength   18
bDescriptorType   1
bcdUSB2.00
bDeviceClass  255
bDeviceSubClass   255
bDeviceProtocol   255
bMaxPacketSize0   64
idVendor  0x04B8
idProduct 0x0130
bcdDevice 1.00
iManufacturer 1 (EPSON)
iProduct  2 (EPSON Scanner)
iSerialNumber 0 ()
bNumConfigurations1
 configuration 0
 bLength  9
 bDescriptorType  2
 wTotalLength 32
 bNumInterfaces   1
 bConfigurationValue  1
 iConfiguration   0 ()
 bmAttributes 192 (Self-powered)
 MaxPower 2 mA
  interface 0
   altsetting 0
   bLength9
   bDescriptorType4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints  2
   bInterfaceClass255
   bInterfaceSubClass 255
   bInterfaceProtocol 255
   iInterface 0 ()
endpoint 0
bLength   7
bDescriptorType   5
bEndpointAddress  0x81 (in 0x01)
bmAttributes  2 (bulk)
wMaxPacketSize512
bInterval 255 ms
bRefresh  0
bSynchAddress 0
endpoint 1
bLength   7
bDescriptorType   5
bEndpointAddress  0x02 (out 0x02)
bmAttributes  2 (bulk)
wMaxPacketSize512
bInterval 255 ms
bRefresh  0
bSynchAddress 0

trying to find out which USB chip is used
checking for GT-6801 ...
this is not a GT-6801 (bcdUSB = 0x200)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
this is not a MA-1015 (bcdUSB = 0x200)
checking for MA-1509 ...
this is not a MA-1509 (bcdUSB = 0x200)
checking for LM983[1,2,3] ...
this is not a LM983x (bcdUSB = 0x200)
checking for GL646 ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL646_HP ...
this is not a GL646_HP (bcdUSB = 0x200)
checking for GL660+GL646 ...
this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL841 ...
this is not a GL841 (bNumEndpoints = 2)
checking for ICM532B ...
this is not a ICM532B (check 2, bcdUSB = 0x200)
checking for PV8630/LM9830 ...
this is not a PV8630/LM9830 (bDeviceClass = 255)
checking for M011 ...
this is not a M011 (bcdUSB = 0x200)
checking for RTS8822L-01H ...
this is not a RTS8822L-01H (bDeviceClass = 255)
checking for rts8858c ...
this is not a rts8858c (bDeviceClass = 255)
checking for SQ113 ...
this is not a SQ113 (bDeviceClass = 255)
Couldn't determine the type of the USB chip (result from sane-backends 1.0.18)

found USB scanner (vendor=0x04b8 [EPSON], product=0x0130 [EPSON Scanner]) at 
libusb:005:008

device descriptor of 0x05e3/0x0608 at 005:002 (USB2.0 Hub)
bLength   18
bDescriptorType   1
bcdUSB2.00
bDeviceClass  9
bDeviceSubClass   0
bDeviceProtocol   1
bMaxPacketSize0   64
idVendor  0x05E3
idProduct 0x0608
bcdDevice 7.02
iManufacturer 0 ()
iProduct  1 (USB2.0 Hub)
iSerialNumber 0 ()
bNumConfigurations1
 configuration 0
 bLength  9
 bDescriptorType  2
 wTotalLength 25
 bNumInterfaces   1
 bConfigurationValue  1
 iConfiguration   0 ()
 bmAttributes 224 (Self-poweredRemote Wakeup)
 MaxPower 100 mA
  interface 0
   altsetting 0
   bLength9
   bDescriptorType4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints  1
   bInterfaceClass9
   bInterfaceSubClass 0
   bInterfaceProtocol 0
   iInterface 0 ()
endpoint 0
bLength   7
bDescriptorType   5
bEndpointAddress  0x81 (in 0x01)
bmAttributes  3 (interrupt)
wMaxPacketSize1
bInterval 12 ms
bRefresh  0
bSynchAddress 0

device descriptor of 0x/0x at 005:001 (Linux 2.6.18-5-amd64 ehci_hcd 
EHCI Host Controller)
bLength   18
bDescriptorType   1
bcdUSB 

[sane-devel] Canon CanoScan LiDE 600F

2008-01-03 Thread Jürgen Ernst
Hi!

Unfortunately yesterday I bought a Canon CanoScan LiDE 600F.
Is anyone working on a backend to that scanner yet?

If yes I want to join.

If not I want to start programming a backend.

-- 
Ciao
J?rgen

Microsoft is not the answer. Microsoft is the question.
NO is the answer.



[sane-devel] Canon CanoScan LiDE 600F

2008-01-03 Thread Gerald Murray
Quoting J?rgen Ernst jrernst at gmx.de:
  Canon CanoScan LiDE 600F.
 Is anyone working on a backend to that scanner yet?

 If not I want to start programming a backend.

 Ciao
 J?rgen

There is no one working on adding this scanner as of yet, so welcome!

There is a lot of information on the sane site about starting.
The chips for the LiDE 600F are known, but are not known to be
compatible with sane-supported chips.  A good start would be to
complete a small scan with a usb sniffer to log the traffic on the usb bus for
that device, and make the scan log available for interested persons to view.
That may allow identification of the protocol.

Gerald