[sane-devel] Epson Perfection V200
Hello everybody, I would like to know if the V200 scanner run with sane and eventually the package libsane-extras (available in Debian, provide epkowa) or I'm obliged to use iscan ? I would like to use Kooka with this scanner, as it is a frontend, I supposed that there is no problem ? -- Tourneur Henry-Nicolas
[sane-devel] Nightly CVS snapshot link outdated on Alioth
I've noticed on the Alioth Sane CVS pages, that the link to download the nightly CVS snapshot sends an outdated file: sane-scm-latest.tar.gz, with latest modifications dated 14 May 2007... The page with the CVS link is: https://alioth.debian.org/scm/?group_id=30186 Is there a way to fix that (or remove the link) ? I suspect some people to download the CVS version using this link instead of the CVS anonymous access, and not to notice the file is not the correct one. Nicolas
[sane-devel] EpsonStylus cx3650 SANE scan problem
Hello, I tried to use the SANE driver for my Epson Stylus cx3650 on an iMacIntel, but did not get it to work and TWAIN SANE Interface says ?no image source found?. Any help would be great! I try to explain, what I did till now in the following? - sane-find-scanner gives me the following: ? found USB scanner (vendor=0x2040 [Hauppauge], product=0x7060 [Nova-T Stick]) at libusb:005:005-2040-7060-00-00 found USB scanner (vendor=0x04b8 [EPSON], product=0x080e [USB MFP]) at libusb:005:004-04b8-080e-00-00 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. scanimage -L gives the following: 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). - I changed the last lines in epson.conf like this without any change?: # USB scanner: # There are two different methods of configuring a USB scanner: libusb and the kernel module # For any system with libusb support (which is pretty much any recent Linux distribution) the # following line is sufficient. This however assumes that the connected scanner (or to be more # accurate, it's device ID) is known to the backend. usb # For libusb support for unknown scanners use the following command # usb product ID device ID # e.g.: usb 0x04b8 0x080e usb 0x2040 0x7060 usb /dev/usbscanner0 usb /dev/usb/scanner0 I can also add the info I get from SANE_DEBUG_EPSON=255 scanimage -L: [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.1.0-cvs [epson] sane_init, # epson.conf [epson] sane_init, # [epson] sane_init, # here are some examples for how to configure the EPSON backend [epson] sane_init, # [epson] sane_init, # SCSI scanner: [epson] sane_init, scsi EPSON [epson] sane_init, # for the GT-6500: [epson] sane_init, scsi EPSON SC [epson] sane_init, # [epson] sane_init, # Parallel port scanner: [epson] sane_init, #pio 0x278 [epson] sane_init, #pio 0x378 [epson] sane_init, #pio 0x3BC [epson] sane_init, # [epson] sane_init, # USB scanner: [epson] sane_init, # There are two different methods of configuring a USB scanner: libusb and the kernel module [epson] sane_init, # For any system with libusb support (which is pretty much any recent Linux distribution) the [epson] sane_init, # following line is sufficient. This however assumes that the connected scanner (or to be more [epson] sane_init, # accurate, it's device ID) is known to the backend. [epson] sane_init, usb [epson] attach_one_usb() [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(, 3) [epson] attach: opening [epson] attach_one_usb(libusb:005:004-04b8-080e-00-00) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(libusb:005:004-04b8-080e-00-00, 3) [epson] attach: opening libusb:005:004-04b8-080e-00-00 [epson] sane_init, # For libusb support for unknown scanners use the following command [epson] sane_init, # usb product ID device ID [epson] sane_init, # e.g.: [epson] sane_init, # usb 0x4b8 0x110 [epson] sane_init, # And for the scanner module, use the following configuration: [epson] sane_init, #usb /dev/usbscanner0 [epson] sane_init, #usb /dev/usb/scanner0 [epson] sane_init, usb 0x04b8 0x080e [epson] attach_one_usb(libusb:005:004-04b8-080e-00-00) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(libusb:005:004-04b8-080e-00-00, 3) [epson] attach: opening libusb:005:004-04b8-080e-00-00 [epson] sane_init, usb 0x2040 0x7060 [epson] sane_init, usb /dev/usbscanner0 [epson] attach_one_usb(/dev/usbscanner0) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(/dev/usbscanner0, 3) [epson] attach: opening /dev/usbscanner0 [epson] sane_init, usb /dev/usb/scanner0 [epson] attach_one_usb(/dev/usb/scanner0) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(/dev/usb/scanner0, 3) [epson] attach: opening /dev/usb/scanner0 [epson] sane_init, [epson] sane_get_devices()
[sane-devel] Nightly CVS snapshot link outdated on Alioth
Nicolas nicolas.martin at freesurf.fr wrote: Hi, I've noticed on the Alioth Sane CVS pages, that the link to download the nightly CVS snapshot sends an outdated file: sane-scm-latest.tar.gz, with latest modifications dated 14 May 2007... As it happens, CVS snapshots were broken for all Alioth projects since this date, and nobody noticed. This has now been fixed by the Alioth admins. Thanks very much for the heads up, JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] EpsonStylus cx3650 SANE scan problem
why did you add your Hauppauge card's id's to the epson driver conf file? allan On 3/24/08, alexander-hoeppner at freenet.de alexander-hoeppner at freenet.de wrote: Hello, I tried to use the SANE driver for my Epson Stylus cx3650 on an iMacIntel, but did not get it to work and TWAIN SANE Interface says no image source found. Any help would be great! I try to explain, what I did till now in the following? - sane-find-scanner gives me the following: ? found USB scanner (vendor=0x2040 [Hauppauge], product=0x7060 [Nova-T Stick]) at libusb:005:005-2040-7060-00-00 found USB scanner (vendor=0x04b8 [EPSON], product=0x080e [USB MFP]) at libusb:005:004-04b8-080e-00-00 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. scanimage -L gives the following: 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). - I changed the last lines in epson.conf like this without any change?: # USB scanner: # There are two different methods of configuring a USB scanner: libusb and the kernel module # For any system with libusb support (which is pretty much any recent Linux distribution) the # following line is sufficient. This however assumes that the connected scanner (or to be more # accurate, it's device ID) is known to the backend. usb # For libusb support for unknown scanners use the following command # usb product ID device ID # e.g.: usb 0x04b8 0x080e usb 0x2040 0x7060 usb /dev/usbscanner0 usb /dev/usb/scanner0 I can also add the info I get from SANE_DEBUG_EPSON=255 scanimage -L: [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.1.0-cvs [epson] sane_init, # epson.conf [epson] sane_init, # [epson] sane_init, # here are some examples for how to configure the EPSON backend [epson] sane_init, # [epson] sane_init, # SCSI scanner: [epson] sane_init, scsi EPSON [epson] sane_init, # for the GT-6500: [epson] sane_init, scsi EPSON SC [epson] sane_init, # [epson] sane_init, # Parallel port scanner: [epson] sane_init, #pio 0x278 [epson] sane_init, #pio 0x378 [epson] sane_init, #pio 0x3BC [epson] sane_init, # [epson] sane_init, # USB scanner: [epson] sane_init, # There are two different methods of configuring a USB scanner: libusb and the kernel module [epson] sane_init, # For any system with libusb support (which is pretty much any recent Linux distribution) the [epson] sane_init, # following line is sufficient. This however assumes that the connected scanner (or to be more [epson] sane_init, # accurate, it's device ID) is known to the backend. [epson] sane_init, usb [epson] attach_one_usb() [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(, 3) [epson] attach: opening [epson] attach_one_usb(libusb:005:004-04b8-080e-00-00) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(libusb:005:004-04b8-080e-00-00, 3) [epson] attach: opening libusb:005:004-04b8-080e-00-00 [epson] sane_init, # For libusb support for unknown scanners use the following command [epson] sane_init, # usb product ID device ID [epson] sane_init, # e.g.: [epson] sane_init, # usb 0x4b8 0x110 [epson] sane_init, # And for the scanner module, use the following configuration: [epson] sane_init, #usb /dev/usbscanner0 [epson] sane_init, #usb /dev/usb/scanner0 [epson] sane_init, usb 0x04b8 0x080e [epson] attach_one_usb(libusb:005:004-04b8-080e-00-00) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(libusb:005:004-04b8-080e-00-00, 3) [epson] attach: opening libusb:005:004-04b8-080e-00-00 [epson] sane_init, usb 0x2040 0x7060 [epson] sane_init, usb /dev/usbscanner0 [epson] attach_one_usb(/dev/usbscanner0) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(/dev/usbscanner0, 3) [epson] attach: opening /dev/usbscanner0 [epson] sane_init, usb /dev/usb/scanner0 [epson] attach_one_usb(/dev/usb/scanner0) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(/dev/usb/scanner0, 3) [epson] attach: opening /dev/usb/scanner0 [epson] sane_init, [epson] sane_get_devices() -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] HAL and scanners.
Hi, First of all, i have to apologize for being away from computer since few days. This was easter days. Happy easter days :D About proprietary backends. They have to support SANE, but SANE has not to support those backends. Actually, as Allan said, nothing will be break. And it's up to the proprietary backend to provide its own HAL callout. The discussion is not about patching e.g. XSane to use HAL, but rather to allow parallel unified device naming in SANE backends. This will allow a HAL callout to compute mostly working SANE device name in order HAL addon to open a device on plug and monitor its sensors, and much more. Regards, ?tienne.
[sane-devel] HAL and scanners.
On Mon, Mar 24, 2008 at 10:13 AM, ?tienne Bersac bersace03 at gmail.com wrote: Hi, First of all, i have to apologize for being away from computer since few days. This was easter days. Happy easter days :D About proprietary backends. They have to support SANE, but SANE has not to support those backends. Actually, as Allan said, nothing will be break. And it's up to the proprietary backend to provide its own HAL callout. The discussion is not about patching e.g. XSane to use HAL, but rather to allow parallel unified device naming in SANE backends. This will allow a HAL callout to compute mostly working SANE device name in order HAL addon to open a device on plug and monitor its sensors, and much more. you mentioned HAL working on freebsd? what do sane's default device names look like on that platform? allan -- The truth is an offense, but not a sin
[sane-devel] root gets correct 'scanimage -L' results, but user does not, even if I hack permissions
I asked this a while back and heard zilch, so I'll try again.
Please do not be put off by my email address! I'm a real
person, asking a real question!
Here's the question:
Ok, so I have a ScanMaker 3600 USB scanner, and I'm running debian:
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-13) (da...debian.org)
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri
Jun 1 00:47:00
UTC 2007
When I run:
rcdesk:/etc/udev# sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try modprobe sg.
found USB scanner (vendor=0x05da, product=0x40b3, chip=M011) at
libusb:001:006
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
rcdesk:/etc/udev#
So, as root I try debug output of scanimage:
rcdesk:/etc/udev# SANE_DEBUG_SM3600=255 scanimage -L
[sanei_debug] Setting debug level of sm3600 to 255.
[sm3600] SM3600 init
[sm3600] SM3600 version: 106
[sm3600] found dev 05DA/40B3, libusb:001:006
device `v4l:/dev/video0' is a Noname BT878 video (ATI TV-Wonder VE)
virtual device
device `sm3600:libusb:001:006' is a Microtek ScanMaker 3600 flatbed scanner
rcdesk:/etc/udev#
That was for root. For normal user, the output of sane-find* is the same.
As normal user, scanimage gives:
rusty at rcdesk:~$ SANE_DEBUG_SM3600=255 scanimage -L
[sanei_debug] Setting debug level of sm3600 to 255.
[sm3600] SM3600 init
[sm3600] SM3600 version: 106
device `v4l:/dev/video0' is a Noname BT878 video (ATI TV-Wonder VE)
virtual device
rusty at rcdesk:~$
If I chmod the scanner device in /proc/bus/usb to 666 I still get the
same results from scanimage as user.
Also, no matter what I try in /etc/udev, I get permissions 644 for the
device associated with the SM3600. Here's udev:
rusty at rcdesk:~$ ls -l /etc/udev/rules.d/025_libsane.rules
lrwxrwxrwx 1 root root 16 2008-03-13 06:26
/etc/udev/rules.d/025_libsane.rules - ../libsane.rules
rusty at rcdesk:~$ egrep 40b3 /etc/udev/rules.d/025_libsane.rules
# Microtek ScanMaker 3600
SYSFS{idVendor}==05da, SYSFS{idProduct}==40b3, MODE=664,
GROUP=scanner
and yet:
rusty at rcdesk:~$ ls -l /proc/bus/usb/001
total 0
-rw-rw-rw- 1 root root 43 2008-03-14 09:02 001
-rw-rw-rw- 1 root root 43 2008-03-14 09:02 002
-rw-rw-rw- 1 root root 43 2008-03-14 17:42 007
rusty at rcdesk:~$
And, finally:
rcdesk:/etc/udev# cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor= ProdID= Rev= 2.06
S: Manufacturer=Linux 2.6.18-5-686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=:00:1f.4
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor= ProdID= Rev= 2.06
S: Manufacturer=Linux 2.6.18-5-686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=:00:1f.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.01 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=05e3 ProdID=0604 Rev= 0.12
S: Product=USB Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=05da ProdID=40b3 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
rcdesk:/etc/udev#
Hopefully I've given enough info above, without wasting anyone's time
with TOO much info!
Thanks for any ideas/pointers (or even questions) on either of the above
problems
Rusty
[sane-devel] root gets correct 'scanimage -L' results, but user does not, even if I hack permissions
On Mon, 24 Mar 2008 08:29:09 -0700 Rusty Carruth rustyc at descomp.com wrote: I asked this a while back and heard zilch, so I'll try again. Please do not be put off by my email address! I'm a real person, asking a real question! [...] If I chmod the scanner device in /proc/bus/usb to 666 I still get the same results from scanimage as user. Also, no matter what I try in /etc/udev, I get permissions 644 for the device associated with the SM3600. Here's udev: I believe that udev is setting permissions on /dev/bus/usb/* and not in /proc/bus/usb/* I also think libusb is using the /dev/bus/usb/* paths in order to access devices. Please check access rights there. [...] Bye, Giuseppe
[sane-devel] HPLJM1005MFP
Dear list: My probles is so simple. I've an Hewlett Packard Laser Jet M 1005 MFP, that work fine in printing, but is impossible to de in scanner mode. I ve searched for a solution, but everything was wrong. The places en the lasts month were http://gersonruotolo.wordpress.com/2008/01/15/instalando-a-multifuncional-hp-m1005-mfp-no-slackware-12/ http://article.gmane.org/gmane.comp.graphics.scanning.sane.devel/11067 http://www.sane-project.org/lists/sane-backends-external.html#S-HPLJM1005 Recentry, I saw that sane-backends-1.0.19 have support for this machine, but... ...but this don't work. I've not problems to compile ands install, but don't work. My system: -Computer- Processor : Genuine Intel(R) CPU 2160 @ 1.80GHz Memory : 1010MB (487MB used) Operating System : Debian GNU/Linux lenny/sid User Name : root (root) Date/Time : lun 24 mar 2008 14:37:28 ART -Display- Resolution : 1440x900 pixels OpenGL Renderer : Unknown X11 Vendor : The X.Org Foundation -Multimedia- Audio Adapter : HDA-Intel - HDA Intel -Input Devices- Macintosh mouse button emulation AT Translated Set 2 keyboard PC Speaker ImPS/2 Generic Wheel Mouse -Printers (CUPS)- HPLJM1005MFP : i(Default)/i -IDE Disks- SAMSUNG HD161HJ TSSTcorpCD/DVDW SH-S182F -SCSI Disks- Linux bbar7 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64 GNU/Linux The problem: bbar7:/usr/src# sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. found USB scanner (vendor=0x03f0, product=0x3b17) at libusb:007:005 found USB scanner (vendor=0x0458, product=0x7004) at libusb:003:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. You can see that the machine exist *found USB scanner (vendor=0x03f0, product=0x3b17) at libusb:007:005* , but it dont identify like an scanner. The other is the webcam. Please, I need your help. For this ONLY reason, I keep a WinXP partition active. Javier
[sane-devel] HPLJM1005MFP
with sane 1.0.19 installed, try this command: SANE_DEBUG_HPLJM1005=5 scanimage -L 2hpljm1005.log and lets see what is in that log file. allan On 3/24/08, JAP javier.debian.bb.ar at gmail.com wrote: Dear list: My probles is so simple. I've an Hewlett Packard Laser Jet M 1005 MFP, that work fine in printing, but is impossible to de in scanner mode. I ve searched for a solution, but everything was wrong. The places en the lasts month were http://gersonruotolo.wordpress.com/2008/01/15/instalando-a-multifuncional-hp-m1005-mfp-no-slackware-12/ http://article.gmane.org/gmane.comp.graphics.scanning.sane.devel/11067 http://www.sane-project.org/lists/sane-backends-external.html#S-HPLJM1005 Recentry, I saw that sane-backends-1.0.19 have support for this machine, but... ...but this don't work. I've not problems to compile ands install, but don't work. My system: -Computer- Processor : Genuine Intel(R) CPU 2160 @ 1.80GHz Memory : 1010MB (487MB used) Operating System : Debian GNU/Linux lenny/sid User Name : root (root) Date/Time : lun 24 mar 2008 14:37:28 ART -Display- Resolution : 1440x900 pixels OpenGL Renderer : Unknown X11 Vendor : The X.Org Foundation -Multimedia- Audio Adapter : HDA-Intel - HDA Intel -Input Devices- Macintosh mouse button emulation AT Translated Set 2 keyboard PC Speaker ImPS/2 Generic Wheel Mouse -Printers (CUPS)- HPLJM1005MFP : i(Default)/i -IDE Disks- SAMSUNG HD161HJ TSSTcorpCD/DVDW SH-S182F -SCSI Disks- Linux bbar7 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64 GNU/Linux The problem: bbar7:/usr/src# sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. found USB scanner (vendor=0x03f0, product=0x3b17) at libusb:007:005 found USB scanner (vendor=0x0458, product=0x7004) at libusb:003:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. You can see that the machine exist *found USB scanner (vendor=0x03f0, product=0x3b17) at libusb:007:005* , but it dont identify like an scanner. The other is the webcam. Please, I need your help. For this ONLY reason, I keep a WinXP partition active. Javier -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] FIXED! Thanks! Re: root gets correct 'scanimage -L' results, but user does not, even if I hack permissions
Giuseppe Sacco wrote: On Mon, 24 Mar 2008 08:29:09 -0700 Rusty Carruth rustyc at descomp.com wrote: [...] If I chmod the scanner device in /proc/bus/usb to 666 I still get the same results from scanimage as user. Also, no matter what I try in /etc/udev, I get permissions 644 for the device associated with the SM3600. Here's udev: I believe that udev is setting permissions on /dev/bus/usb/* and not in /proc/bus/usb/* I also think libusb is using the /dev/bus/usb/* paths in order to access devices. Please check access rights there. [...] Ah, yes, exactly! (duh!) Thank you! That fixed it! As a normal user: rusty at rcdesk:~$ /orig/usr/bin/scanimage -L device `v4l:/dev/video0' is a Noname BT878 video (ATI TV-Wonder VE) virtual device device `sm3600:libusb:001:005' is a Microtek ScanMaker 3600 flatbed scanner rusty at rcdesk:~$ xsane I'd suggest fixing the doc to mention /dev/bus, but instead I'll put doing it myself into the list of things I need to do One Of These Days Real Soon Now. rc
