*** This bug is a duplicate of bug 192176 ***
https://bugs.launchpad.net/bugs/192176
I recently bought a MFC-L2710DW and had the same issue, although I
didn't have the second "brother4" device that worked. Here is how I
fixed it:
The problem was that the scanner was detected by the "airscan" and/or
"escl" drivers, and these (are they the same?) produce the artifacts and
don't offer all resolutions. We want to use the "brother4" scanner
instead.
In /etc/sane.d/dll.conf *and* in /etc/sane.d/dll.d/* I commented out
any "escl" and "airscan" entries.
In /etc/sane.d/dll.d/, I added a file "brother4" with the line
"brother4" in it.
Then, because my scanner wasn't found by scanimage -L, I added it
manually using this command:
sudo brsaneconfig4 -a name="Brother_Scanner" model="MFC-L2710DW"
ip=192.168.x.y
After this, scanimage -L listed this scanner
$ scanimage -L
device `brother4:net1;dev0' is a Brother Brother_Scanner MFC-L2710DW
And I got all resolutions and no artifacts when scanning.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1940754
Title:
Scanned images are deteriorated by compression artifacts with Brother
MFC-L2710DW
Status in sane-backends package in Ubuntu:
New
Bug description:
I have a Brother MFC-L2710DW printer with integrated flatbed scanner.
There are two major problems when scanning with sane:
The first problem is that the quality of all scanned images is very
poor due to 8x8 pixel JPG compression artefacts. The root coarse seems
to be the backend, as the result is the same independently if the
image is acquired through xsane or scanimage.
The second problem is that sane only scans up to 300 dpi. 1200 dpi is
not offered at all and for 600 dpi the error message "Failed to start
scanner: Invalid argument" is displayed. Interestingly the message is
displayed after the scanner has completed the scan, but the data seems
not to be received or understood by sane.
The scanner works fine in Ubuntu with the commercial software vuescan,
which rules out a firmware bug or malfunctioning of the scanner
itself.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libsane 1.0.29-0ubuntu5.2
ProcVersionSignature: Ubuntu 5.11.0-16.17~20.04.5-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 21 23:00:21 2021
InstallationDate: Installed on 2015-11-05 (2116 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: sane-backends
UpgradeStatus: Upgraded to focal on 2020-09-10 (345 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1940754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
