[sane-devel] Avision Backend
my god you are hard to help. i have to repeat EVERY message? ...(give root password)... allan On 5/7/07, Robin Stewart s48...@bluebottle.com wrote: Allan When I run su and put in my login password it is rejected as an authentication failure. When I use the same password in sudo, it works! Do you have a work around? Robin The above comments are in response to m. allan noah's email of 07/05/07 18:18 as quoted below: try this: su - (give root password) you now have a root shell. then run the command i gave. logout of root shell when done. allan -- Get a free email account with anti spam protection. http://www.bluebottle.com -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Avision Backend
On Tuesday 08 May 2007, Julian Stacey wrote: When I run su and put in my login password it is rejected as an authentication failure. When I use the same password in sudo, it works! Do you have a work around? Maybe sudo doesnt check if your UID is in group 0 in /etc/group. whereas su does check bounce you. just do sudo su then you can use your own password and become root unless this has been explicitly forbidden in the sudoers configuration Horst
[sane-devel] RE: CONFIG_USB_SUSPEND and black scans
Hi Gerhard-- Could you tell me what are your versions of libusb libsane? I have a report that libsane 1.0.19-cvs20070421-1 will not work, but libsane 1.0.18-6 will I have a non-working with libusb 2:0.1.12-7 Dean Message: 4 Date: Mon, 7 May 2007 11:49:12 +0200 From: Gerhard Jaeger gerh...@gjaeger.de Subject: Re: [sane-devel] On CONFIG_USB_SUSPEND and black scans To: sane-devel@lists.alioth.debian.org Message-ID: 200705071149.12399.gerh...@gjaeger.de Content-Type: text/plain; charset=ansi_x3.4-1968 Hi, one thing to add. I've tested the Plustek-Backend on a recent Debian system x86_64 AND CONFIG_USB_SUSPEND activated. Result: no problems so far. Gerhard
[sane-devel] Avision Backend
Allan It is not that I can not read carefully, but that I had found that the su command could not be run due to my only password being rejected. I therefore hoped that sudo would do and that is why I spelt out that I had used sudo not su. I had been given advice to use sudo in another situation because su was not accessable with my known password. I have just found a way of changing my root password so that I can use SU. I appreciate you support and I am trying to follow your instructions but at the time I could not do so because I did not know how to access the root with the passwords that I remembered. Here are the results. root@robin-desktop:/home/robin# SANE_DEBUG_AVISION=7 scanimage -L [sanei_debug] Setting debug level of avision to 7. [avision] sane_init:(Version: 1.0 Build: 201) [avision] sane_init: parsing config line # This are the possible options. Normally any scanner [avision] sane_init: config file line 1: ignoring comment line [avision] sane_init: parsing config line # should work just fine without them - and they are only [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line # needed for test and debugging. So if you experience problems [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line # and you solve them with enabling options here, please notify [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line # the SANE/Avision maintainer: Rene Rebe r...@exactcode.de [avision] sane_init: config file line 5: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 6: ignoring empty line [avision] sane_init: parsing config line #option disable-gamma-table [avision] sane_init: config file line 7: ignoring comment line [avision] sane_init: parsing config line #option disable-calibration [avision] sane_init: config file line 8: ignoring comment line [avision] sane_init: parsing config line #option force-a4 [avision] sane_init: config file line 9: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 10: ignoring empty line [avision] sane_init: parsing config line #scsi AVISION [avision] sane_init: config file line 11: ignoring comment line [avision] sane_init: parsing config line #scsi FCPA [avision] sane_init: config file line 12: ignoring comment line [avision] sane_init: parsing config line #scsi MINOLTA [avision] sane_init: config file line 13: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-S600C [avision] sane_init: config file line 14: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-SS600 [avision] sane_init: config file line 15: ignoring comment line [avision] sane_init: parsing config line #scsi HP [avision] sane_init: config file line 16: ignoring comment line [avision] sane_init: parsing config line #scsi hp [avision] sane_init: config file line 17: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 18: ignoring empty line [avision] sane_init: parsing config line #scsi /dev/scanner [avision] sane_init: config file line 19: ignoring comment line [avision] sane_init: parsing config line # usb libusb:002:003 [avision] sane_init: config file line 20: ignoring comment line [avision] sane_init: parsing config line # usb 0x03f0 0x0701 [avision] sane_init: config file line 21: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 22: ignoring empty line [avision] sane_init: parsing config line #added to read the visioneer strobe xp 450 [avision] sane_init: config file line 23: ignoring comment line [avision] sane_init: parsing config line #addresses found from sane-find-scanner [avision] sane_init: config file line 24: ignoring comment line [avision] sane_init: parsing config line #usb libush:001:006 [avision] sane_init: config file line 25: ignoring comment line [avision] sane_init: parsing config line usb 0x04a7 0x0424 [avision] sane_init: config file line 26: trying to attach USB:`usb 0x04a7 0x0424' [avision] attach: [avision] attach: opening libusb:002:003 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 1, status: 0 [avision] attach: Inquiry gives mfg=VISIONER, model=Strobe XP 450, product revision=1.02. [avision] attach: model is not in the list of supported models! [avision] attach: You might want to report this output. [avision] attach: To: r...@exactcode.de (the Avision backend author) [avision] sane_init: Trying to find USB device 638 a27 ...
[sane-devel] RE: CONFIG_USB_SUSPEND and black scans
On Dienstag, 8. Mai 2007, Dean Loros wrote: Hi Gerhard-- Could you tell me what are your versions of libusb libsane? I have a report that libsane 1.0.19-cvs20070421-1 will not work, but libsane 1.0.18-6 will I have a non-working with libusb 2:0.1.12-7 Hi, I've installed libusb-0.1-4 Version 2:01.12-4 and libsane 1.0.18-5 and as mentioned directly compiled from CVS. HTH Gerhard
[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet 5550/5590/7650
On 5/6/07, Julien BLACHE j...@jblache.org wrote: That's a question for Ilia ;) I think he did test everything as he has the hardware, though. The backend doesn't support scanning at 150 dpi yet, as its functionality is similar to Windows driver, which uses only limited list of scanner resolutions, doing its downgrading for all other values. The problem is that the backend doesn't reject incorrect resolution value but has to. I'll fix that. -- Ilia Sotnikov
[sane-devel] minor problem with current (20070507) CVS code on OS/2
On 5/8/07, Franz Bakan fba...@gmx.net wrote: configure (generated by Autoconf 2.61) fails and claims not to find grep (which is bogus) Running autoconf (2.59) locally solves the problem. can someone please regenerate configure in cvs with autoconf 2.59 Please send the fragment of config.log from configure when it didn't find the grep. -- Ilia Sotnikov
[sane-devel] Scanners available for experiments
Hi, I have some scanners lying around, and reading http://www.meier-geinitz.de/sane/misc/mustek-scanners.html#UNSUPPORTED and the referenced mailinglist entry http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/011685.html I realized that instead of simply throwing out these scanners they might be usable for obduction by some of you guys. I live in Roskilde, Denmark, and realize that scanners are probably too expensive to get safely transported too far. But I could help arrange a remote lab with SSH root access to a Debian machine with the scanners attached, and me available through IRC (or better: Ekiga) to assist in plugging and unplugging, and ripping apart if that's what is neede to get more knowledge about these beasts. Tell me if it is of any interest. Heidelberg Linoscan 1200 (SCSI) ScanMagic 1200 USB (vendor=0x055f, product=0x0003, chip=MA-1017?) Of course I'd love to make the scanners work, but I'd rather have you guys learn from killing them than preserving them and have no Linux drivers for them. I also have access to a Linotype-Hell Jade2 (SCSI) but until some decent alternative scanner setup is working my girlfriend won't let go of that one (working only with MacOS 9!), so either that'l have to wait or you need to somehow assure me that the tests done on that is not too risky. Tell me if it is of any interest! - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er n?r: http://www.shibumi.org/eoti.htm
[sane-devel] Avision Backend
On 5/8/07, Robin Stewart s48...@bluebottle.com wrote: I appreciate you support and I am trying to follow your instructions but at the time I could not do so because I did not know how to access the root with the passwords that I remembered. if you intend to admin a unix or unix-like machine of any type, you MUST know and remember the root password. Here are the results. [snip] [avision] sane_init: parsing config line usb 0x04a7 0x0424 [avision] sane_init: config file line 26: trying to attach USB:`usb 0x04a7 0x0424' [avision] attach: [avision] attach: opening libusb:002:003 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 1, status: 0 [avision] attach: Inquiry gives mfg=VISIONER, model=Strobe XP 450, product revision=1.02. [avision] attach: model is not in the list of supported models! [avision] attach: You might want to report this output. [avision] attach: To: r...@exactcode.de (the Avision backend author) [snip] 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). [avision] sane_exit: ok, well, at least you can talk to the scanner as root. to get other users to talk to it, you have to do some sort of permissions modifications, which seem to depend on your OS/distro. perhaps someone else can chime in here in order to get the thing to actually work, i guess you should forward this email to rene directly, and see if he has any suggestions. allan -- The truth is an offense, but not a sin
[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet 5550/5590/7650
On 5/8/07, Dale Amon a...@vnl.com wrote: Do you have any idea why it would eject two pages after it scans one? The scanner in question is rather high level in terms of commands, that means that I couldn't (at least, I didn't see such a possibility from the traces on Windows) say 'feed the next page into document feeder'. The scanner does that automatically when ADF is selected until the feeder is empty. And, as far as I can remember, Windows software shows the same greedy behavior. I'll try to verify that in a next few days. -- Ilia Sotnikov
[sane-devel] [RFC] On libsane symbols visibility
Doing native Win32 porting and new backend adding I ran into the question about libsane symbols visibility. That's what 'make libcheck' checks. Current libsane model (or better to say, programming conventions) don't allow to export unnecessary symbols from libsane libraries. That's wise because of possible namespace pollution on a process which loads such a library. But that's also doesn't allow to traditionally develop a backend which consists of several object files because internal symbols which are necessary to be visible from one such file (for example, a backend could be split into several parts according to their meaning, which is rather typical even for existing backends) will also be exported on resulting libsane library. The problem is worse on other platforms, where some POSIX functions are not available and implemented by lib/*.c - their symbols will be exported as well. My suggestion is to mark the functions which are part of SANE API as exportable (__attribute__ ((visibility(default))) symbol attribute and its companion, -fvisibility=hidden). It will give us the necessary result - only explicitly marked symbols will be visible. In ideal case, 'make libcheck' wouldn't be necessary anymore. The above mentioned attribute and command line switch is a GCC extension. Any thoughts? -- Ilia Sotnikov
[sane-devel] Scanners available for experiments
Am Dienstag, den 08.05.2007, 13:52 +0200 schrieb Jonas Smedegaard: Tell me if it is of any interest. Heidelberg Linoscan 1200 (SCSI) This scanner may be compatible to the umax backend. When you tell me the scsi id of the scanner and you are able to compile sane-backends from sourcecode then I tell you what you have to do to do some tests. Best regards Oliver
[sane-devel] [RFC] On libsane symbols visibility
Ilia Sotnikov hos...@gmail.com wrote: My suggestion is to mark the functions which are part of SANE API as exportable (__attribute__ ((visibility(default))) symbol attribute and its companion, -fvisibility=hidden). It will give us the necessary result - only explicitly marked symbols will be visible. In ideal case, 'make libcheck' wouldn't be necessary anymore. The above mentioned attribute and command line switch is a GCC extension. Any thoughts? SANE traditionally builds with non-gcc compilers too, so this is kind of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it, YMMV) :) Backends that use multiple files usually #include them (see the snapscan backend, for instance) to workaround this limitation. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] [RFC] On libsane symbols visibility
On 5/8/07, Julien BLACHE j...@jblache.org wrote: SANE traditionally builds with non-gcc compilers too, so this is kind of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it, YMMV) :) Then for such compilers we'll definitely need to use some #ifdef's. Backends that use multiple files usually #include them (see the snapscan backend, for instance) to workaround this limitation. Yes, I saw and used that solution. What about marking symbols explicitly when compiling under native Windows and use no attributes under other platforms? Otherwise we'll need to leave with not-intended-to-but-exported symbols at least under Windows having 'make libcheck' complain about them. -- Ilia Sotnikov
[sane-devel] [RFC] On libsane symbols visibility
Ilia Sotnikov hos...@gmail.com wrote: Yes, I saw and used that solution. What about marking symbols explicitly when compiling under native Windows and use no attributes under other platforms? Otherwise we'll need to leave with not-intended-to-but-exported symbols at least under Windows having 'make libcheck' complain about them. I don't know if a clean libcheck is mandatory/enforced as far as native win32 is concerned; I think it can't be avoided if part of the portable function library is used. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] minor problem with current (20070507) CVS code on OS/2
On Tue, 8 May 2007 11:05:44 +0300, Ilia Sotnikov wrote: configure (generated by Autoconf 2.61) fails and claims not to find grep (which is bogus) Running autoconf (2.59) locally solves the problem. can someone please regenerate configure in cvs with autoconf 2.59 Please send the fragment of config.log from configure when it didn't find the grep. I hope this is the fragment you mean: ... configure:2911: checking how to run the C preprocessor configure:2951: gcc -E conftest.c configure:2957: $? = 0 configure:2988: gcc -E conftest.c conftest.c:8:28: ac_nonexistent.h: No such file or directory configure:2994: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME sane-backends | #define PACKAGE_TARNAME sane-backends | #define PACKAGE_VERSION 1.0.18-cvs | #define PACKAGE_STRING sane-backends 1.0.18-cvs | #define PACKAGE_BUGREPORT sane-devel@lists.alioth.debian.org | /* end confdefs.h. */ | #include ac_nonexistent.h configure:3027: result: gcc -E configure:3056: gcc -E conftest.c configure:3062: $? = 0 configure:3093: gcc -E conftest.c conftest.c:8:28: ac_nonexistent.h: No such file or directory configure:3099: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME sane-backends | #define PACKAGE_TARNAME sane-backends | #define PACKAGE_VERSION 1.0.18-cvs | #define PACKAGE_STRING sane-backends 1.0.18-cvs | #define PACKAGE_BUGREPORT sane-devel@lists.alioth.debian.org | /* end confdefs.h. */ | #include ac_nonexistent.h configure:3137: checking for grep that handles long lines and -e configure:3200: error: no acceptable grep could be found in G:/Dev/gcc/335csd2/usr/i386-pc-os2-emx/bin;G:/ ... If not, the complete log is available here: http://www.fbakan.de/temp/config.zip Franz
[sane-devel] [RFC] On libsane symbols visibility
On 5/8/07, Julien BLACHE j...@jblache.org wrote: Ilia Sotnikov hos...@gmail.com wrote: I don't know if a clean libcheck is mandatory/enforced as far as native win32 is concerned; I think it can't be avoided if part of the portable function library is used. As far as I understand, it's not enforced, but highly recommended/good coding style. Although, if hiding some symbols would introduce a lot of portability problems, it should be avoided, in my opinion. Deciscion: don't introduce additional complexities and let some additional symbols to be present as exported under some platforms (eg. Win32)? -- Ilia Sotnikov
[sane-devel] [RFC] On libsane symbols visibility
Ilia Sotnikov hos...@gmail.com wrote: As far as I understand, it's not enforced, but highly recommended/good coding style. Although, if hiding some symbols would introduce a lot of portability problems, it should be avoided, in my opinion. Deciscion: don't introduce additional complexities and let some additional symbols to be present as exported under some platforms (eg. Win32)? The goal is to have clean libraries in the general case, yes. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] Scanners available for experiments
On Tue, 2007-05-08 at 13:52 +0200, Jonas Smedegaard wrote: Hi, I have some scanners lying around, and reading http://www.meier-geinitz.de/sane/misc/mustek-scanners.html#UNSUPPORTED and the referenced mailinglist entry http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/011685.html I realized that instead of simply throwing out these scanners they might be usable for obduction by some of you guys. I live in Roskilde, Denmark, and realize that scanners are probably too expensive to get safely transported too far. But I could help arrange a remote lab with SSH root access to a Debian machine with the scanners attached, and me available through IRC (or better: Ekiga) to assist in plugging and unplugging, and ripping apart if that's what is neede to get more knowledge about these beasts. Tell me if it is of any interest. Heidelberg Linoscan 1200 (SCSI) ScanMagic 1200 USB (vendor=0x055f, product=0x0003, chip=MA-1017?) Of course I'd love to make the scanners work, but I'd rather have you guys learn from killing them than preserving them and have no Linux drivers for them. I also have access to a Linotype-Hell Jade2 (SCSI) but until some decent alternative scanner setup is working my girlfriend won't let go of that one (working only with MacOS 9!), so either that'l have to wait or you need to somehow assure me that the tests done on that is not too risky. Tell me if it is of any interest! - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er n?r: http://www.shibumi.org/eoti.htm Check this page for your Scanmagic usb scanner, vendor and product id is not mentioned, but mustek_usb backend supports the MA-1017 chip http://www.meier-geinitz.de/sane/mustek_usb-backend/ -- m.vr.gr. Gerard Klaver
[sane-devel] [RFC] On libsane symbols visibility
On Tuesday 08 May 2007 16:15:38 Julien BLACHE wrote: SANE traditionally builds with non-gcc compilers too, so this is kind of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it, YMMV) :) Intel compiler version 9 supports these -fvisibility compiler options, on Mac and Linux, I think. I can't remember if it also supports the attributes, but it would make sense for it to, since it has the -f options to control overall visibility. -- Bill Gallafent.
[sane-devel] [RFC] On libsane symbols visibility
I wish I can find the way to remove my address from the list without giving the pass word Thanks for help francesco --- William Gallafent will...@gallaf.net wrote: On Tuesday 08 May 2007 16:15:38 Julien BLACHE wrote: SANE traditionally builds with non-gcc compilers too, so this is kind of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it, YMMV) :) Intel compiler version 9 supports these -fvisibility compiler options, on Mac and Linux, I think. I can't remember if it also supports the attributes, but it would make sense for it to, since it has the -f options to control overall visibility. -- Bill Gallafent. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
[sane-devel] [RFC] On libsane symbols visibility
I wish I can find the way to remove my address from the list without giving the pass word Thanks for help francesco --- Ilia Sotnikov hos...@gmail.com wrote: On 5/8/07, Julien BLACHE j...@jblache.org wrote: Ilia Sotnikov hos...@gmail.com wrote: I don't know if a clean libcheck is mandatory/enforced as far as native win32 is concerned; I think it can't be avoided if part of the portable function library is used. As far as I understand, it's not enforced, but highly recommended/good coding style. Although, if hiding some symbols would introduce a lot of portability problems, it should be avoided, in my opinion. Deciscion: don't introduce additional complexities and let some additional symbols to be present as exported under some platforms (eg. Win32)? -- Ilia Sotnikov -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
[sane-devel] [RFC] On libsane symbols visibility
Francesco Pietra chiendar...@yahoo.com wrote: Hi, I wish I can find the way to remove my address from the list without giving the pass word Thanks for help I've removed your address from the sane-devel mailing-list. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
