<div dir="ltr">See the attached email. 18.04 fix in the ppa needs testing.<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Gunnar Hjalmarsson</strong> <span dir="auto"><<a href="mailto:1728012@bugs.launchpad.net">1728012@bugs.launchpad.net</a>></span><br>Date: Wed, Jun 26, 2019 at 12:26 PM<br>Subject: [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change<br>To: <<a href="mailto:steven@simplycircus.com">steven@simplycircus.com</a>><br></div><br><br>I have uploaded a proposed fix of sane-backends to this PPA:<br>
<br>
<a href="https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends" rel="noreferrer" target="_blank">https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends</a><br>
<br>
If you are on 18.04 and affected by this bug, it would be great if you<br>
could install from the PPA, test to find out if it makes a difference,<br>
and report your observations in a comment here.<br>
<br>
-- <br>
You received this bug notification because you are subscribed to the bug<br>
report.<br>
<a href="https://bugs.launchpad.net/bugs/1728012" rel="noreferrer" target="_blank">https://bugs.launchpad.net/bugs/1728012</a><br>
<br>
Title:<br>
Many 3rd party scanner drivers are broken by a sane change<br>
<br>
Status in sane-backends package in Ubuntu:<br>
Fix Released<br>
Status in sane-backends source package in Bionic:<br>
In Progress<br>
Status in sane-backends package in Debian:<br>
Fix Released<br>
<br>
Bug description:<br>
[Impact]<br>
<br>
* Starting with Ubuntu 17.10, Ubuntu changed the directory where sane<br>
dll looks for third party drivers. This configuration effectively<br>
broke backward compatibility for all existing third-party drivers.<br>
<br>
* A large swath of these third party drivers (most of them) are no<br>
longer supported by the OEM, so maintaining compatibility is<br>
important.<br>
<br>
* No open source replacement drivers are currently available, nor<br>
does the community have the resources to easily replace them.<br>
<br>
* This bug represents a substantial portion of the scanners in use.<br>
<br>
Scanners known to be affected include, but are not limited to:<br>
<br>
- Brother Scanners (all Brother scanners before brscan4)<br>
- DCP-145C<br>
- DCP-163C<br>
- DCP-165C<br>
- DCP-167C<br>
- DCP-185C<br>
- DCP-195C<br>
- DCP-197C<br>
- DCP-365CN<br>
- DCP-373CW<br>
- DCP-375CW<br>
- DCP-377CW<br>
- DCP-383C<br>
- DCP-385C<br>
- DCP-387C<br>
- DCP-395CN<br>
- DCP-585CW<br>
- DCP-6690CW<br>
- DCP-7030<br>
- DCP-7040<br>
- DCP-7045N<br>
- DCP-8070D<br>
- DCP-8080DN<br>
- DCP-8085DN<br>
- DCP-9010CN<br>
- DCP-9040CN<br>
- DCP-9042CDN<br>
- DCP-9045CDN<br>
- DCP-J125<br>
- DCP-J315W<br>
- DCP-J515W<br>
- DCP-J715W<br>
- MFC-250C<br>
- MFC-255CW<br>
- MFC-257CW<br>
- MFC-290C<br>
- MFC-295CN<br>
- MFC-297C<br>
- MFC-490CW<br>
- MFC-495CW<br>
- MFC-5490CN<br>
- MFC-5890CN<br>
- MFC-5895CW<br>
- MFC-6490CW<br>
- MFC-6890CDW<br>
- MFC-7320<br>
- MFC-7340<br>
- MFC-7345N<br>
- MFC-7440N<br>
- MFC-7450<br>
- MFC-7840N<br>
- MFC-7840W<br>
- MFC-790CW<br>
- MFC-795CW<br>
- MFC-8370DN<br>
- MFC-8380DN<br>
- MFC-8480DN<br>
- MFC-8510DN<br>
- MFC-8680DN<br>
- MFC-8880DN<br>
- MFC-8890DW<br>
- MFC-9010CN<br>
- MFC-9120CN<br>
- MFC-9320CW<br>
- MFC-9440CN<br>
- MFC-9450CDN<br>
- MFC-9840CDW<br>
- MFC-990CW<br>
- MFC-J220<br>
- MFC-J265W<br>
- MFC-J270W<br>
- MFC-J410<br>
- MFC-J410W<br>
- MFC-J415W<br>
- MFC-J615W<br>
- MFC-J630W <br>
<br>
- Dell MFP Laser Printer 1135n<br>
<br>
- Epson Scanners<br>
- All scanners supported by the libsane-epk driver<br>
- All scanners supported by the iscan driver<br>
- Epson Perfection V10<br>
- Epson Perfection V1000<br>
- Epson WorkForce GT-1500<br>
- Epson Perfection V33<br>
<br>
- Samsung M2070<br>
<br>
- Xerox Workcentre 3225<br>
<br>
* This was working in the 17.04 release. 18.10 is an LTS release, so<br>
backporting is warranted for the 18.10 release.<br>
<br>
[Test Case]<br>
<br>
* Following the standard installation procedures for any of the<br>
affected scanner drivers results in the driver files being installed<br>
to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux-<br>
gnu/sane. When xsane is run, the scanner is not found.<br>
<br>
[Regression Potential]<br>
<br>
* Regression to previous working sane package often results in the<br>
automatic removal of core system components (documented in the<br>
comments to this bug report), making regression an unusable option for<br>
addressing this bug.<br>
<br>
* The available patch is functional and stable in the 19.10 branch.<br>
<br>
[Other Info]<br>
* 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.<br>
<br>
* The addition of symlinks alone does not appear to fix this issue,<br>
though it may make the scanner detectable. Changes to udev rules are<br>
also needed to allow proper communications to the scanners. A<br>
selection of workarounds, including working (though not ideal) udev<br>
rules for a number of scanners has been posted to the sane<br>
troubleshooting guide:<br>
<a href="http://help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks" rel="noreferrer" target="_blank">help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks</a><br>
<br>
To manage notifications about this bug go to:<br>
<a href="https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions</a><br>
</div></div>