When did this used to work?
I'm assuming you have the Brother proprietary drivers installed, can you
check the versions of the 'brscan', 'brscan2', 'brscan3' and 'brscan4'
packages?
Can you get a log containing the calls leading up to the loop (the attached log
is from a fresh start where no scanning was started). You can get the log from
simple-scan with:
$ simple-scan --debug
if that is easier to capture it.
You can also get the equivalent from xsane by running:
$ ltrace -l libsane.so.1 xsane
The particular response from the driver is in fact valid, we are
correctly waiting for SANE_STATUS_EOF before stopping the sane_reads. So
this might be a buggy driver that's triggered by the options that
simple-scan sets.
** Changed in: simple-scan (Ubuntu)
Status: New => Incomplete
** Changed in: simple-scan (Ubuntu)
Importance: Undecided => Medium
** Also affects: simple-scan
Importance: Undecided
Status: New
** Changed in: simple-scan
Status: New => Incomplete
** Changed in: simple-scan
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1344869
Title:
simple-scan consumes 100% cpu and fills disk with logs attempting to
scan wirelessly with Brother MFC-7860DW
To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1344869/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
