On 11 January 2011 15:43, John Goerzen <[email protected]> wrote: > That's the one that I noticed the problem with to start with.
Ah. In that case, assuming that you can also reproduce this on the command line, then this bug can be reassigned to the the sane package. If you start gscan2pdf with the --debug option, and try once the scanimage, and once the scanadf frontends, then in the debug output on the command line, you will find the scanimage and scanadf calls used. Please post them here to be sure that they are sensible, and try them directly on the command line to make sure that the scanadf version does not properly scan both sides. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
