However, it seems that your scanner needs more time for calibration now. Patch1 doubles wait time.
If this won't help, we need to accept a new ready flag (command 'da20' normally is waiting for 0x01 in byte 8 of the response; now we also try to accept 0x02). For this I prepared patch2. If both patches won't help, you can reopen bug #314787. It's much easier to exchange log files via the bug tracker. Cheers, Rolf Am 23.08.2014 um 15:04 schrieb HelpHelp: > Hello Luis, > > this Problem occurred with xsane too. > The last logs I have put in the email, were made with xsane. > > Is that enough? Or do you need it with scanimage? > Regards > > On 23.08.2014 15:02, Louis Lagendijk wrote: >> On Fri, 2014-08-22 at 22:59 +0200, HelpHelp wrote: >>> Hello Louis, >>> >>> your were absolutely right. I tried it out with usb, and there it is >>> the >>> same. So it might be a problem >>> with the pixma driver in general. >>> Should I open a new bug report, or could we solve the problem here? >>> >>> you can find the logs here >>> >>> sane-usb: >>> https://dl.dropboxusercontent.com/u/12003240/logs/sane-usb.log >>> sane-lan: >>> https://dl.dropboxusercontent.com/u/12003240/logs/sane.network.log >>> >>> Thank you! >>> >>> Regards >> I had a look at the previous trace again. I wonder whether this is a >> backend problem or an issue with gscan2pdf. Can you reproduce the >> problem with scanimage? >> >> The reason I suspect gscan2pdf is that the exceptions it throws suggest >> that it may not yet be setup properly before you start a scan. Can you >> please test with scanimage? >> Maybe Rolf can have a look at the traces as well >> Thanks >> Louis >> >> > > > -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
