Comment 431 for bug 85488

At the time of writing, gutsy does not appear to contain the fixes from Debian's "sane-backends", unless the fix was merged in separate from the entire new version...

Debian: 1.0.19~cvs20070730-1
http://packages.debian.org/unstable/source/sane-backends
http://packages.debian.org/changelogs/pool/main/s/sane-backends/sane-backends_1.0.19~cvs20070730-1/changelog

Ubuntu: 1.0.19~cvs20070505-3ubuntu1
http://packages.ubuntu.com/gutsy/source/sane-backends
http://changelogs.ubuntu.com/changelogs/pool/main/s/sane-backends/sane-backends_1.0.19~cvs20070505-3ubuntu1/changelog

Until this occurs, the only way that this will be "fixed" is if the kernel has been fixed for your device. Did you try Tribe 3? According to https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/85488/comments/351 , https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/85488/comments/380 , and https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/85488/comments/384 , it appears the "quirk listing" for your device _should_ have made it into the 2.6.22-9.19 kernel, and it appears also to be in the latest git, but my Gutsy machine says that the latest (again, at the time of writing) is 2.6.22-10.33, so I'm not 100% sure about other changes between that last message and now.