Summary: sane reports that my scanner, which was working fine before I did some Ubuntu upgrades, now possesses 0 scanning capabilities. This is a bug on someone's part, and Ratcliffe suggested I try here. (I got no replies in the IRC channel.)
Forwarded conversation Subject: Re: [gscan2pdf-help] gscan2pdf-help post from gwern0 at gmail.comrequires approval ------------------------ From: *Jeffrey Ratcliffe* <[email protected]> Date: Wed, Feb 17, 2010 at 3:16 AM To: gscan2pdf-help at lists.sourceforge.net On Wed, Feb 17, 2010 at 01:37:07AM +0000, gscan2pdf-help-owner at lists.sourceforge.net wrote: > Out of the box, jaunty gscan2pdf failed to scan with an array of error > messages. I upgraded it and most of its deps to Karmic in the hopes > things had been fixed, but no dice. So then I did a git clone and > began working with *that*. After a great deal of fiddling with CPAN > and debuild for things the configure script did not seem to pick up or > flag as missing, I ran bin/gscan2pdf with great hopes - and it failed > on scanning with much the same error. It looks as though the SANE backend process is not finishing cleanly. Can you scan with scanimage? Regards Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkt7pc8ACgkQVDAgnE3XzJMj5ACgo+u/ui/quBjiQfg3Brzutf83 dMoAoMosjX6WEnU6sVXqB4HGEJ5EUTzK =KBi8 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ gscan2pdf-help mailing list gscan2pdf-help at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gscan2pdf-help ---------- From: *Gwern Branwen* <[email protected]> Date: Wed, Feb 17, 2010 at 9:57 AM To: Jeffrey Ratcliffe <jeffrey.ratcliffe at gmail.com> Cc: gscan2pdf-help at lists.sourceforge.net No; in fact, all of the 'frontend' (as the preferences call them) seem to be broken. Attached is screenshot & --debug for 'scanimage'. -- gwern ---------- From: *Jeffrey Ratcliffe* <[email protected]> Date: Wed, Feb 17, 2010 at 1:57 PM To: gscan2pdf-help at lists.sourceforge.net The reason that hasn't worked is that scanimage is reporting no resolutions available: --resolution dpi [0] Sets the resolution of the scanned image. The available scan area is also 0: -l 0..0mm [0] Top-left x position of scan area. -t 0..0mm [0] Top-left y position of scan area. -x 0..0mm [0] Width of scan-area. -y 0..0mm [0] Height of scan-area. What happens if you try on the command line: scanimage --device-name='epson:libusb:001:012' --mode='Binary' --source='Flatbed' > image.pnm ? The epson backend doesn't seem to be in a good state. Regards Jeff ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ---------- From: *Gwern Branwen* <[email protected]> Date: Fri, Feb 19, 2010 at 11:44 AM To: Jeffrey Ratcliffe <jeffrey.ratcliffe at gmail.com> Cc: gscan2pdf-help at lists.sourceforge.net On Wed, Feb 17, 2010 at 1:57 PM, Jeffrey Ratcliffe > --source='Flatbed' > image.pnm [11:41 AM] 248Mb$ scanimage --device-name='epson:libusb:001:012' scanimage: open of device epson:libusb:001:012 failed: Invalid argument [11:42 AM] 248Mb$ scanimage -L device `epson:libusb:001:014' is a Epson flatbed scanner [11:43 AM] 248Mb$ scanimage --device-name='epson:libusb:001:014' scanimage: sane_start: Invalid argument [11:43 AM] 248Mb$ scanimage -L device `epson:libusb:001:015' is a Epson flatbed scanner [11:43 AM] 248Mb$ rm image.pnm; scanimage --device-name='epson:libusb:001:015' --mode='Binary' --source='Flatbed' > image.pnm scanimage: attempted to set inactive option source [11:43 AM] 248Mb$ rm image.pnm; scanimage --device-name='epson:libusb:001:015' --mode='Binary' > image.pnm scanimage: sane_start: Invalid argument [11:43 AM] 248Mb$ scanimage -L device `epson:libusb:001:016' is a Epson flatbed scanner [11:43 AM] 248Mb$ rm image.pnm; scanimage --device-name='epson:libusb:001:016' > image.pnm scanimage: sane_start: Invalid argument [11:44 AM] 248Mb$ (I tried turning off & on the scanner before each scanimage -L, hence the incrementing.) -- gwern ---------- From: *Jeffrey Ratcliffe* <[email protected]> Date: Sat, Feb 20, 2010 at 9:39 AM To: Gwern Branwen <gwern0 at gmail.com> Cc: gscan2pdf-help at lists.sourceforge.net Try scanimage --device-name='epson:libusb:001:012' --help just to check the option names are correct, but assuming they are, this is a problem for the sane-devel list. Regards Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkt/9B0ACgkQVDAgnE3XzJNLdgCfTve09hebb6626AYAelpGrfhL 4OYAnRbKMNo1mcte92K7WDQB5RiQTSKU =V9lM -----END PGP SIGNATURE----- ---------- From: *Gwern Branwen* <[email protected]> Date: Mon, Feb 22, 2010 at 11:14 AM To: Jeffrey Ratcliffe <jeffrey.ratcliffe at gmail.com> Cc: gscan2pdf-help at lists.sourceforge.net On Sat, Feb 20, 2010 at 9:39 AM, Jeffrey Ratcliffe [11:11 AM] 1355Mb$ scanimage --device-name='epson:libusb:001:003' --help &> output I'm not entirely sure what you're looking for, so I've attached the entire output: [11:11 AM] 1355Mb$ scanimage --device-name='epson:libusb: 001:003' --help &> output I notice that your previous suggested commands all had the '--option=value' syntax, but the output says things like '--mode Binary|Gray|Color [Binary]'. -- gwern On Mon, Feb 22, 2010 at 11:50 AM, Jeffrey Ratcliffe < jeffrey.ratcliffe at gmail.com> wrote: > On Mon, Feb 22, 2010 at 11:14:17AM -0500, Gwern Branwen wrote: >> I'm not entirely sure what you're looking for, so I've attached the >> entire output: >> >> [11:11 AM] 1355Mb$ scanimage --device-name='epson:libusb:001:003' >> --help &> output > > Yes. There is a problem with the backend - it is reporting 0 > resolution and page size! I would start back posting this output on > sane-devel and see if you get any joy there. > >> I notice that your previous suggested commands all had the >> '--option=value' syntax, but the output says things like '--mode >> Binary|Gray|Color [Binary]'. > > That is just showing you the options - i.e. the --mode option could be > binary, gray or color, but defaults to binary if you don't specify it. > > Regards > > Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100227/6ab2a2ce/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: output Type: application/octet-stream Size: 5750 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100227/6ab2a2ce/attachment-0001.obj>
