Yes, I confirm that the issue is resolved with 3.13.4.2-0ubuntu1.
Not relevant to this bug, but I do notice that the scan speed is quit
slow using simple-scan. Comparing with xsane at the same resolution
(300dpi):
- xsane: 23 seconds
- simple-scan: 2 minutes.
Thanks very much for the fast
Hi Robert,
Sorry to be vague, but I don't actually scan much so the last time I
recall doing it I was running trusty.
Yes, the proprietary brother drivers are required for wireless scanning
AIUI.
$ dpkg -l | grep brscan
ii brscan-skey 0.2.4-1
'ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl libsane.so.1
xsane' log from a successful wireless scan using xsane.
** Attachment added: ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl
libsane.so.1 xsane
I think this is fixed in simple-scan 3.13.4.2, please re-test.
--
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
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
When simple-scan is spinning, the following entry is added to the log
repeatedly until ENOSPC:
[+15,29s] DEBUG: scanner.vala:1310: sane_read (0) - (SANE_STATUS_GOOD,
0)
Further details:
$ cat /proc/$(pidof simple-scan)/stack
** Attachment added: strace snapshot of simple-scan consuming 100% CPU
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4156869/+files/bug-1344869-strace.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
