Bouvard nostaples

Comments and changes to this ticket

• 

  onyxfish February 22nd, 2009 @ 10:18 PM

  • Tag set to “exception, networked-scanner, sane”
  • State changed from “new” to “open”

  Thanks for the ticket Ron. This is the second time I've seen this traceback in a log. It appears that some SANE devices either don't have names at all, or their names are not stored in the way I expect them to be. I have implemented some further debugging for the next version that should help me sort these issues out (I don't have a network scanner to test with so I'm working from documentation regarding how all this should work).

  In the meantime it would be very helpful if you could get the name of your device by running:

  scanimage --list-devices

  That might help me determine why my code is yelling about your device having an unusual name.

  Thanks.

  EDIT: I should have mentioned that command requires that you have the sane-utils package installed.

• You flagged this item as spam.
  

  Ron Young February 22nd, 2009 @ 11:53 PM

  I have sane-utils installed (version 1.0.14-5 -- ubuntu 8.04).

  Here is the output from scanimage:

  Script started on Sun 22 Feb 2009 09:26:55 PM PST ron@ron-amd64:~$ scanimage --list-devices device brother2:net1;dev0' is a Brother MFC-440CN scanner ron@ron-amd64:~$ exit

  Script done on Sun 22 Feb 2009 09:27:08 PM PST

• 

  onyxfish February 23rd, 2009 @ 09:54 PM

  • State changed from “open” to “hold”

  This error should be resolved by this SaneMe commit, which will part of the release that rolls out along with the next version of NoStaples. I will hold this ticket until then so it can be tested.

• 

  onyxfish March 18th, 2009 @ 10:17 AM

  • State changed from “hold” to “resolved”

  I have not seen any reports of this error against the 0.4 build, so I'm closing this ticket.

• You flagged this item as spam.
  

  Ron Young March 18th, 2009 @ 11:08 AM

  yes, 0.4 parses the scanner device correctly. (There are some other issues regarding changing resolution that I haven't had time to fully document in a bug report...)

• 

  onyxfish March 18th, 2009 @ 11:15 AM

  No problem Ron, I appreciate you following up. I have a couple other open tickets for 0.5 that may cover your other problems with resolution. ( #34 and #37) There are a wide variety of ways that SANE specifies/constrains resolutions and I'm still working on refining the code to elegantly take into account all the variations. This actually wasn't an area I expected to be quite so problematic, but I'm focused on having it fixed up for the next release.