Hi Oliver, I start it normally from KDE-Desktop, I created two Icons for it, copy like "xsane -c" or "normal" with "xsane -s", without any path. So it should be allways the same verion of xsane.
Greetz, Christoph Am Donnerstag, 5. April 2007 17:03:59 schrieb Oliver Rauch: > Hello Christoph, > > Works fine for me. > > Please check if you really use the same xsane version when you start it > from the command line as "xsane -c" compared to the other case (may be > not started via command line). > > Best regards > Oliver -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070407/58b44ccf/attachment.pgp From [email protected] Sat Apr 7 05:40:55 2007 From: [email protected] (D_S -) Date: Sat Apr 7 09:36:16 2007 Subject: [sane-devel] Genius HR6X Slim Message-ID: <[email protected]> I would like to test if this scaner works with the genesys backend but had some trouble. udev won't make a device file so I made a rule: <10-udev.rules> # Scanner Genius BUS=="usb", SYSFS{idVendor}=="0458", SYSFS{idProduct}=="2019", NAME="%k", SYMLINK="custom/scanner", OWNER="root", GROUP="users", MODE="755" I would like to get this scanner working if possible. It's been there dusting since I changed all my sistems to GNU/Linux about 2 years ago so It's about time to get it working. The genesys backend supports the chip so maybe it's just bad configuration. I'm willing to make tests with it so please tell me if there's something I can do. Thanks. Here's the info. Gentoo GNU/Linux sane-backends-1.0.18-r2 sane-frontends-1.0.14 sane-0.991 # 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. found USB scanner (vendor=0x0458, product=0x2019, chip=GL646) at libusb:002:003 # 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. cat /etc/sane.d/genesys.conf # genesys.conf: Configuration file for Genesys Logic GL646 and GL841 based scanners # # scanners that are not yet supported # uncomment them only for developpment purpose # ... # # Testing by me # # Genius ColorPage HR6X Slim usb 0x0458 0x2019 # # supported scanners # # Medion MD5345/MD6228/MD6471 usb 0x0461 0x0377 # Hewlett Packard ScanJet 2300c usb 0x03f0 0x0901 # Canon LiDE 35/40/50 usb 0x04a9 0x2213 # Canon LiDE 60 usb 0x04a9 0x221c # scanimage -d genesys:/dev/custom/scanner -T [sanei_debug] Setting debug level of genesys to 255. [genesys] SANE Genesys backend version 1.0 build 8 from sane-backends 1.0.18 [genesys] sane_init: authorize != null [genesys] sane_init: little endian machine [genesys] sane_init: reading config file `genesys.conf' [genesys] sane_init: config file line 1: ignoring comment line [genesys] sane_init: config file line 2: ignoring empty line [genesys] sane_init: config file line 3: ignoring comment line [genesys] sane_init: config file line 4: ignoring comment line [genesys] sane_init: config file line 5: ignoring comment line [genesys] sane_init: config file line 6: ignoring comment line [genesys] sane_init: config file line 7: ignoring empty line [genesys] sane_init: config file line 8: ignoring comment line [genesys] sane_init: config file line 9: ignoring comment line [genesys] sane_init: config file line 10: ignoring empty line [genesys] sane_init: config file line 11: ignoring comment line [genesys] sane_init: config file line 12: ignoring comment line [genesys] sane_init: config file line 13: ignoring empty line [genesys] sane_init: config file line 14: ignoring comment line [genesys] sane_init: config file line 15: ignoring comment line [genesys] sane_init: config file line 16: ignoring empty line [genesys] sane_init: config file line 17: ignoring comment line [genesys] sane_init: config file line 18: ignoring comment line [genesys] sane_init: config file line 19: ignoring empty line [genesys] sane_init: config file line 20: ignoring empty line [genesys] sane_init: config file line 21: ignoring comment line [genesys] sane_init: config file line 22: ignoring comment line [genesys] sane_init: config file line 23: ignoring comment line [genesys] sane_init: config file line 24: ignoring empty line [genesys] sane_init: config file line 25: ignoring comment line [genesys] sane_init: config file line 26: trying to attach `usb 0x0458 0x2019' [genesys] attach: start: devp != NULL, may_wait = 0 [genesys] attach: trying to open device `libusb:002:003' [genesys] attach: device `libusb:002:003' successfully opened [genesys] attach: vendor 1112 product 8217 is not supported by this backend [genesys] sane_init: config file line 27: ignoring comment line [genesys] sane_init: config file line 28: ignoring empty line [genesys] sane_init: config file line 29: ignoring comment line [genesys] sane_init: config file line 30: ignoring comment line [genesys] sane_init: config file line 31: ignoring comment line [genesys] sane_init: config file line 32: ignoring empty line [genesys] sane_init: config file line 33: ignoring comment line [genesys] sane_init: config file line 34: trying to attach `usb 0x0461 0x0377' [genesys] sane_init: config file line 35: ignoring empty line [genesys] sane_init: config file line 36: ignoring comment line [genesys] sane_init: config file line 37: trying to attach `usb 0x03f0 0x0901' [genesys] sane_init: config file line 38: ignoring empty line [genesys] sane_init: config file line 39: ignoring comment line [genesys] sane_init: config file line 40: trying to attach `usb 0x04a9 0x2213' [genesys] sane_init: config file line 41: ignoring empty line [genesys] sane_init: config file line 42: ignoring comment line [genesys] sane_init: config file line 43: trying to attach `usb 0x04a9 0x221c' [genesys] sane_init: config file line 44: ignoring empty line [genesys] sane_init: exit [genesys] sane_open: start (devicename = `/dev/custom/scanner') [genesys] sane_open: couldn't find `/dev/custom/scanner' in devlist, trying attach [genesys] attach: start: devp != NULL, may_wait = 1 [genesys] attach: trying to open device `/dev/custom/scanner' [genesys] attach: couldn't open device `/dev/custom/scanner': Invalid argument scanimage: open of device genesys:/dev/custom/scanner failed: Invalid argument [genesys] sane_exit: start [genesys] sane_exit: exit lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 003: ID 0458:2019 KYE Systems Corp. (Mouse Systems) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070406/17a9dbb6/attachment.html From [email protected] Sun Apr 8 06:56:12 2007 From: [email protected] (=?iso-8859-1?q?K=E5re_S=E4rs?=) Date: Sun Apr 8 07:31:05 2007 Subject: [sane-devel] Parameter Default Values Message-ID: <[email protected]> Hi! I'm implement a sane frontend and have a question about default values. I have an 'Epson Stylus Photo RX500' and use the epkowa backend. I know epkowa is not part of sane, but seems to supports my scanner better than the epson backend. At least more of the parameters are active. The problem I have is that the default values for the color correction parameters ('cct-1' -> 'cct-9') give me a yellow page (original is white) when I write back the original value to one of the parameters. If I don't touch any of the cct parameters I get a white page. Should I be able to assume that the default values are sane, or do I have to initialize the values myself? Best Regards, K?re S?rs
