http://bugzilla.novell.com/show_bug.cgi?id=559697
http://bugzilla.novell.com/show_bug.cgi?id=559697#c19
--- Comment #19 from norbert müller
Still expecting debug logs from libusb0 done with the same scanner paramaters as done with the unsuccessful scan.
In comment #7, I already gave the best debug log I could get: Somehow, libusb-0_1-4-0.1.12-142.1.x86_64.rpm does not produce more logging information than given there. Neither in combination with libusb-1_0-0-1.0.2-2.2.x86_64.rpm (which is a non-debug-version afaik) nor with libusb-1_0-0-1.0.6-8.1.x86_64.rpm (which together with libusb-0_1-4-0.1.13 gave a reasonable error log) I suspect that libusb-0_1-4-0.1.12-142.1.x86_64.rpm simply might not be a (full) debugging version. BTW, I also tried libusb-0_1-4-0.1.12-140.1.x86_64.rpm from http://download.opensuse.org/repositories/hardware:/libusb0/openSUSE_11.2/x8..., but I got the same poor logs. I could not find a debugging version of libusb-1_0-0-1.0.2 anywhere. If you could provide me with such a version, I will give it a try.
... When no data are read, some magic in the driver is applied. It probably handles the step back before continuing.
It happened at 21:45:30. Less than 2 seconds later scanner stopped to work.
Did you press Ctrl+C at 21:45:31 or only scanner stopped to work in this moment?
In that case, the scan stopped and reported I/O error. Only in the case mentioned in comment #15, I finally had to stop with Ctrl-C (but a lot later than the reported behaviour). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.