> But in the meantime, has anyone gone and figured out what changed
> in xscanimage to break the original, non-infinite-loop behavior?
The problem with the umax-backend has been, that SET_OPTION is called by xscanimage
now although an options hasn't changed. I set RELOAD_OPTIONS without testing
that and so the endless-loop was born.
I made a diff to xscanimage to see what changed between sane-0.66 and sane-0.67,
but there didn't change anything. ?!
Bye
Oliver
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com