Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I'm using USB2, and the git repo checkout was Monday late evening, less than an hour before I sent my last email. I already destroyed the test environment I used on Monday which is why I can't tell you the exact time or commit hash that was checked out. I can try again tomorrow morning if there have been relevant changes in the repo since Monday night. -Jonas On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com wrote That kind of error implies that we are having a usb problem, where perhaps a command is being lost, or the data toggle is not being reset. How old is your git repo checkout? Are you using USB 3 ports? allan On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I just did a few successful scans! The patch does indeed make the scanner work, with two caveats: 1) Only every other call to scanimage results in a successful scan, the 2nd, 4th, 6th, etc scan fails the same way as before. 2) Even during successful scans the debug output contains an 'Error during device I/O', although I'm not sure if this is even a problem. Debug output from a successful scan (1st, 3rd, 5th, ... call to scanimage): https://gist.github.com/jonemo/489414e8bc5590998890 Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41 I also tried scanning at 600dpi and it worked successfully (every other time). -Jonas -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
There have been no recent changes that would improve the situation. Can you run scanimage -L repeatedly without error? or maybe scanimage --help? allan On Thu, Mar 19, 2015 at 2:06 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I'm using USB2, and the git repo checkout was Monday late evening, less than an hour before I sent my last email. I already destroyed the test environment I used on Monday which is why I can't tell you the exact time or commit hash that was checked out. I can try again tomorrow morning if there have been relevant changes in the repo since Monday night. -Jonas On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com wrote That kind of error implies that we are having a usb problem, where perhaps a command is being lost, or the data toggle is not being reset. How old is your git repo checkout? Are you using USB 3 ports? allan On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I just did a few successful scans! The patch does indeed make the scanner work, with two caveats: 1) Only every other call to scanimage results in a successful scan, the 2nd, 4th, 6th, etc scan fails the same way as before. 2) Even during successful scans the debug output contains an 'Error during device I/O', although I'm not sure if this is even a problem. Debug output from a successful scan (1st, 3rd, 5th, ... call to scanimage): https://gist.github.com/jonemo/489414e8bc5590998890 Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41 I also tried scanning at 600dpi and it worked successfully (every other time). -Jonas -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] dbus error with scanbd
On 18.03.2015 00:03, ylafont wrote: Will have to check that one out. i Compared the file from version 1.4.1 the current version (1.4.2) has a second part on that line that it doe not like. policy user=saned* ! Arch Linux user=quot;daemonquot; /* You only experience this with 1.4.2 but not 1.4.1? Debian still has 1.4.1 so it must be unrelated, then? -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] dbus error with scanbd
Am 17.03.2015 um 17:03 schrieb ylafont: Will have to check that one out. i Compared the file from version 1.4.1 the current version (1.4.2) has a second part on that line that it doe not like. policy user=saned* ! Arch Linux user=quot;daemonquot; /* Looks like the xml-comment isn't well formed. Please try: !-- Arch Linux user=daemon -- or delete this comment at all. -- Wilhelm w.me...@unix.net -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Both scanimage -L and scanimage --help show the same behavior: Works once,
fails second time. Debug outputs:
scanimage -L: https://gist.github.com/jonemo/c0e508baf4533d79a2ea
scanimage --help: https://gist.github.com/jonemo/6879f07a590d8a5f3fe2
-Jonas
On Thu, 19 Mar 2015 05:26:34 -0700 m. allan noahkitno...@gmail.com wrote
There have been no recent changes that would improve the situation.
Can you run scanimage -L repeatedly without error? or maybe scanimage
--help?
allan
On Thu, Mar 19, 2015 at 2:06 AM, Jonas Neubert jonas.neub...@gmail.com
wrote:
I'm using USB2, and the git repo checkout was Monday late evening, less
than an hour before I sent my last email. I already destroyed the test
environment I used on Monday which is why I can't tell you the exact time
or commit hash that was checked out. I can try again tomorrow morning if
there have been relevant changes in the repo since Monday night.
-Jonas
On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com
wrote
That kind of error implies that we are having a usb problem, where
perhaps a command is being lost, or the data toggle is not being
reset. How old is your git repo checkout? Are you using USB 3 ports?
allan
On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert
jonas.neub...@gmail.com wrote:
I just did a few successful scans! The patch does indeed make the
scanner work, with two caveats:
1) Only every other call to scanimage results in a successful scan,
the 2nd, 4th, 6th, etc scan fails the same way as before.
2) Even during successful scans the debug output contains an 'Error
during device I/O', although I'm not sure if this is even a problem.
Debug output from a successful scan (1st, 3rd, 5th, ... call to
scanimage): https://gist.github.com/jonemo/489414e8bc5590998890
Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to
scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41
I also tried scanning at 600dpi and it worked successfully (every
other time).
-Jonas
--
well, I stand up next to a mountain- and I chop it down with the edge
of my hand
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject unsubscribe your_password
to sane-devel-requ...@lists.alioth.debian.org
