*** This bug is a duplicate of bug 85488 ***
https://bugs.launchpad.net/bugs/85488
confirm this problem on my system as well:
I have tried to use my scanner ever since and I always had the problem that it
would get recognized but sometimes just would not work saying something like
"no device found" (sorry can't reproduce the problem right now). Since I got
feisty things have changed, but to the worse. Now, after scanning (also after
preview scan) the lamp does not go back to the start position, but locks up
somewhere in the middle, also warming-up times have become much longer and the
device makes some weird noise while moving. I also installed the firmware file
but this would not have any effect on the problem. Here's some technical specs:
Distro: Ubuntu Fesity Fawn i386
Computer: Amd Athlon 64, Asus a8v Deluxe mo.bo., scanner is attached to an usb
port on the mo.bo. no hubs in between.
here's the sane-find-scanner output:
found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at
libusb:005:004
and this is what it says when I use scanimage -L:
device `snapscan:libusb:005:004' is a EPSON EPSON Scanner1 flatbed scanner
"scanimage -d snapscan > test.pnm" seems to work fine (at least it did
until now)
I hope this can be of some help for getting some bugs squashed out!
Hannes Pasqualini
--
[Feisty]Regression from edgy: Unable to scan properly
https://bugs.launchpad.net/bugs/93515
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs