> Hi > > I downloaded the sane-backends-1.0.18.tar.gz and compiled from source and > installed via check-install. > > This did two successful scans then stopped and made griding noises. This > seems to be a problem with the more recent Ubuntu/Dapper which seems to have > been solved in the previous version Ubuntu/Breezy and is reflected in the > Ubuntu forums. So I'm not sure what to do new, short of downgrading the > whole machine! > > regards > > Russell
Its OK now, the scanner is now working after removing the sane package from Dapper and leaving the compiled sane-backends. It also works in Breezy via a chroot. It has happily scanned many pages without a problem. I have attached a html tableing the differences in the package versions. cheers Russell -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070213/99cb3935/sane-diff.html From [email protected] Mon Feb 12 16:04:49 2007 From: [email protected] (Emmanuel Counasse) Date: Mon Feb 12 17:02:30 2007 Subject: [sane-devel] HP scanjet 2400 In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> Message-ID: <[email protected]> Hi, I have activated debug information and attached to this mail the output of : scanimage -d genesys:libusb:001:005 2> debug.txt (see : http://www.sharebigfile.com/file/80076/debug-tar-bz2.html) The scanner has start its motor (make noise) but did not do anything, so I decided to stop scanimage by pressing CTRL+C because I don't want to damage my scanner's motor. What do you think about it ? You proposed me to send me scripts, documentation and log, in think it xould be ionteresting to look inside so you can send me them in private, thanks. Best regards. ---- Emmanuel Counasse ****St?phane VOLTZ a ?crit : > Bonjour, > > la d?marche de d?veloppement est de mettre les traces de debug ? leur > maximum > (SANE_DEBUG_GENESYS=255 et SANEDEBUG_GENESYS_GL646=255), de faire un test > avec scanimage, et de voir ce qui ne va pas. Notemment, on compare la valeur > des registres de l'ASIC avec ce qu'ils devraient ?tre, sur la base de > l'analyse de logs USB prises sous windows. > Pour le HP2400, qui est un 2300 avec une r?solution mat?rielle double, > il me > semble qu'il suffira d'intervenir dans le code partout o? il y a des > r?f?rences aux constantes CCD_HP2300 et MOTOR_HP2300. > J'ai envoy? ? plusieurs reprises dans la liste sane-devel les scripts > d'analyse de log captur?es avec usbsniff, ainsi que l'?bauche de > documentation du fonctionnement du backend. Si besoin est, je peux encore les > envoyer. > J'ai le sentiment qu'il n'y a pas grand chose ? faire, mais qu'il > faudra pas > mal de test. Il ne faudra pas h?siter ? me solliciter pour des conseils ou > pour m'envoyer des traces ou du code. > Dans l'espoir que cela puisse int?resser d'autres personnes, je pense > qu'il > faudrait que ces communications se passent dans la liste "Sane-devel List" > <[email protected]>, mais si cela fait bizarre de s'?crire > an anglais sur un sujet qui potentiellement ne pourrait in?resser personne, > mais au moins c'est public et archiv?. > > Cordialement, > Stef > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070212/cdcf3f73/attachment.htm From [email protected] Tue Feb 13 00:51:12 2007 From: [email protected] (Olaf Meeuwissen) Date: Tue Feb 13 00:52:13 2007 Subject: [sane-devel] Security concern about API sane_control_option() In-Reply-To: <[email protected]> (simon zheng's message of "Fri, 09 Feb 2007 22:50:26 +0800") References: <[email protected]> <[email protected]> <[email protected]> Message-ID: <[email protected]> "simon.zheng" <[email protected]> writes: > Olaf Meeuwissen wrote: >> "simon.zheng" <[email protected]> writes: >> >> >>> I'm a new commer for SANE & XSane. Here are some >>> security questions when studying API sane_control_option(). >>> I would appreciate if anyone can give help. >>> >>> Is there any possibility sane_control_option() allows >>> you to get or set any control that would allow one >>> user to affect another user. For example: >>> >> >> sane_control_option() is there so that frontends can tell the backends >> what the user wants to do. It's a very abstract interface and exactly >> what options are available is left to the discretion of each backend. >> >> > I find a spec on SANE Standard 2 draft, > http://www.sane-project.org/sane2/0.08/doc014.html, which documents > well-known options.How about those backend-specific options? Where are > they documented? Manpage? A lot of backends have a 'sane-$backend' man page. I'd expect their options to be documented there, if at all. Please note that backends are not required to support even the well- known options. >> So any security implications are not a result of sane_control_option() >> but of the set of options a particular backend chooses to provide. >> > Right. Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
