The annoyance with Brother .deb files for scanner drivers installing in
/usr/lib64/sane has been mentioned multiple times above. The PPA now
includes a proposed fix of that for eoan, disco and bionic.
To be able to test myself, I breathed new life into my old Brother MFC-
240C. On disco it works fine, albeit after a few preparations - it's one
of those 'unsupported' devices, after all. These are the preparations in
my case:
* Install the driver brscan2-0.2.5-1.amd64.deb
* Add myself to the lp group:
sudo adduser $USER lp
* Add a libsane rule for Brother:
$ cat /lib/udev/rules.d/60-libsane-brother.rules
ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"
* Make the system know about .so files in /usr/lib64:[1]
$ cat /etc/ld.so.conf.d/and-lib64-too.conf
# for scanner driver installed by brscan2
/usr/lib64
and to update /etc/ld.so.cache:
sudo ldconfig
* Reboot
[1]: The proposed fix makes sane find files in /usr/lib64/sane, but
brscan2 also installs .so files directly in /usr/lib64, and the fix
doesn't help for those. I could have created symlinks instead, but chose
to do it this way.
Anyway, after the reboot I can scan using simple-scan or xsane. On
disco, that is.
As regards bionic I have not been able to make it work. At all. Besides
the proposed package in the PPA, I tried to build sane-backends for
bionic using the eoan source. No problem with the build and install, but
still "No scanners detected" when trying to scan. I've tried it on two
computers.
So please let me know: Can you scan on bionic - at all? And if you can,
does the proposed package in the PPA make it easier for you?
--
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/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Bionic:
In Progress
Status in sane-backends package in Debian:
Fix Released
Bug description:
[Impact]
* Starting with Ubuntu 17.10, Ubuntu changed the directory where sane
dll looks for third party drivers. This configuration effectively
broke backward compatibility for all existing third-party drivers.
* A large swath of these third party drivers (most of them) are no
longer supported by the OEM, so maintaining compatibility is
important.
* No open source replacement drivers are currently available, nor
does the community have the resources to easily replace them.
* This bug represents a substantial portion of the scanners in use.
Scanners known to be affected include, but are not limited to:
- Brother Scanners (all Brother scanners before brscan4)
- DCP-145C
- DCP-163C
- DCP-165C
- DCP-167C
- DCP-185C
- DCP-195C
- DCP-197C
- DCP-365CN
- DCP-373CW
- DCP-375CW
- DCP-377CW
- DCP-383C
- DCP-385C
- DCP-387C
- DCP-395CN
- DCP-585CW
- DCP-6690CW
- DCP-7030
- DCP-7040
- DCP-7045N
- DCP-8070D
- DCP-8080DN
- DCP-8085DN
- DCP-9010CN
- DCP-9040CN
- DCP-9042CDN
- DCP-9045CDN
- DCP-J125
- DCP-J315W
- DCP-J515W
- DCP-J715W
- MFC-250C
- MFC-255CW
- MFC-257CW
- MFC-290C
- MFC-295CN
- MFC-297C
- MFC-490CW
- MFC-495CW
- MFC-5490CN
- MFC-5890CN
- MFC-5895CW
- MFC-6490CW
- MFC-6890CDW
- MFC-7320
- MFC-7340
- MFC-7345N
- MFC-7440N
- MFC-7450
- MFC-7840N
- MFC-7840W
- MFC-790CW
- MFC-795CW
- MFC-8370DN
- MFC-8380DN
- MFC-8480DN
- MFC-8510DN
- MFC-8680DN
- MFC-8880DN
- MFC-8890DW
- MFC-9010CN
- MFC-9120CN
- MFC-9320CW
- MFC-9440CN
- MFC-9450CDN
- MFC-9840CDW
- MFC-990CW
- MFC-J220
- MFC-J265W
- MFC-J270W
- MFC-J410
- MFC-J410W
- MFC-J415W
- MFC-J615W
- MFC-J630W
- Dell MFP Laser Printer 1135n
- Epson Scanners
- All scanners supported by the libsane-epk driver
- All scanners supported by the iscan driver
- Epson Perfection V10
- Epson Perfection V1000
- Epson WorkForce GT-1500
- Epson Perfection V33
- Samsung M2070
- Xerox Workcentre 3225
* This was working in the 17.04 release. 18.10 is an LTS release, so
backporting is warranted for the 18.10 release.
[Test Case]
* Following the standard installation procedures for any of the
affected scanner drivers results in the driver files being installed
to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux-
gnu/sane. When xsane is run, the scanner is not found.
[Regression Potential]
* Regression to previous working sane package often results in the
automatic removal of core system components (documented in the
comments to this bug report), making regression an unusable option for
addressing this bug.
* The available patch is functional and stable in the 19.10 branch.
[Other Info]
* Third party sane drivers in previous version of sane were located under
/usr/lib/sane/, however, the current version of sane on Ubuntu only looks for
64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64
and /usr/lib64/sane are other directories old drivers are known to install
files to.
* The addition of symlinks alone does not appear to fix this issue,
though it may make the scanner detectable. Changes to udev rules are
also needed to allow proper communications to the scanners. A
selection of workarounds, including working (though not ideal) udev
rules for a number of scanners has been posted to the sane
troubleshooting guide:
help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
