Many 3rd party scanner drivers are broken by a sane change

Bug #1728012 reported by PeterPall on 2017-10-27
596
This bug affects 114 people
Affects Status Importance Assigned to Milestone
sane-backends (Debian)
Fix Released
Unknown
sane-backends (Ubuntu)
High
Unassigned
Bionic
High
Gunnar Hjalmarsson

Bug Description

To the sponsor: Please upload to bionic using the attached sane-backends_lp1728012_bionic.debdiff.

[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.04 is an LTS release, so backporting is warranted for the 18.04 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.

* Install the libsane1, libsane-common and sane-utils packages from bionic-proposed and confirm that it now finds drivers in /usr/lib/sane.

[Regression Potential]

 * The proposed change is based on an upstream commit, and the patch is functional and stable in both 19.04 and 19.10. Low regression risk.

[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

PeterPall (peterpall) wrote :
description: updated
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sane-backends (Ubuntu):
status: New → Confirmed
Jeremy Bicha (jbicha) on 2017-10-27
Changed in sane-backends (Ubuntu):
importance: Undecided → High

I can confirm that the Epson Perfection V300 is also affected

Using libsane1 1.0.27-1~experimental2ubuntu2.1 allows me to install the drivers without conflicts.

But the scanner is not recognized. Neither by scanimage, simple-scan or iscan

lsusb shows that the scanner is attached

lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 04b8:0131 Seiko Epson Corp. GT-F720 [GT-S620/Perfection V30/V300 Photo]
Bus 003 Device 005: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
Bus 003 Device 004: ID 08bb:2707 Texas Instruments
Bus 003 Device 003: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 003 Device 002: ID 24f0:0137
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Kubuntu 17.04
Fail to use Epson Perfection V30

$ lsusb |grep -i epson

Bus 003 Device 005: ID 04b8:0131 Seiko Epson Corp. GT-F720 [GT-S620/Perfection V30/V300 Photo]

$ apt list --installed |grep -e esci -e iscan -e libsane -e sane-utils

esci-interpreter-gt-f720/now 0.1.1-2 amd64 [installed,local]
iscan/now 2.30.2-2 amd64 [installed,local]
iscan-data/now 1.36.0-1 all [installed,local]
libsane-common/now 1.0.27-1~experimental2ubuntu2.1 all [installed,local]
libsane-extras/artful,now 1.0.22.5 amd64 [installed]
libsane-extras-common/artful,artful,now 1.0.22.5 all [installed,automatic]
libsane-hpaio/artful,now 3.17.7+repack0-3 amd64 [installed]
libsane1/now 1.0.27-1~experimental2ubuntu2.1 amd64 [installed,local]
sane-utils/now 1.0.27-1~experimental2ubuntu2.1 amd64 [installed,local]

$ scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

Xerox Workcentre 3225 with the drivers version 1.00.25:00.05 that used to work very well with Zesty's libsane still not functional.
My malfunction hasn't changed a bit with the 1.0.27-1~experimental2ubuntu2.1 package.
Like before xsane crashes with the following message:
  Not a JPEG file: starts with 0x00 0x00
and/or hangs with scanning status.
mariusz:~> dpkg -l | grep sane
ii libkf5sane-data 17.04.3-0ubuntu1 all scanner library (data files)
ii libkf5sane5 17.04.3-0ubuntu1 amd64 scanner library (runtime)
ii libksane-data 4:17.04.3-0ubuntu1 all scanner library (data files) - transitional package
ii libksane0 4:15.08.3-1ubuntu2 amd64 scanner library (runtime)
ii libsane-common 1.0.27-1~experimental2ubuntu2.1 all API library for scanners -- documentation and support files
ii libsane-extras:amd64 1.0.22.5 amd64 API library for scanners -- extra backends
ii libsane-extras-common 1.0.22.5 all API library for scanners -- documentation and support files
rc libsane-hpaio:amd64 3.16.7+repack0-1ubuntu1 amd64 HP SANE backend for multi-function peripherals
ii libsane1:amd64 1.0.27-1~experimental2ubuntu2.1 amd64 API library for scanners
ii sane 1.0.14-12build1 amd64 scanner graphical frontends
ii sane-utils 1.0.27-1~experimental2ubuntu2.1 amd64 API library for scanners -- utilities
ii xsane 0.999-5ubuntu2 amd64 featureful graphical frontend for SANE (Scanner Access Now Easy)
ii xsane-common 0.999-5ubuntu2 all xsane architecture independent files

I could use some/any guidance for providing more details to anyone if reverting back to working libsane is not an option.

Forgot to mention that I use or rather attempt to use the scanner over the TCP.

Michael Hill (wrendriff) wrote :

Add to list of scanner "broken" - Epson Perfection V300 Photo.

dependency errors occurring after upgrade from Ubuntu 17.04 to 17.10 are
iscan depending on libsane (>=1.0.11-3)
esci-interpreter-gt-f720 depends on iscan (>=2.16.1)

luca.mg (luca-mg) wrote :

Cross posting from https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352?comments=all

On artful, libsane1 1.0.27-1~experimental2ubuntu2.1, in short: the Epson 4490 Photo scanner doesn't work, the Brother MDC-1910W scanner only works as root; both were fully working on zesty. In details:

Epson 4490 Photo as user
sane-find-scanner detects a bunch of USB devices including the scanner, but has not enough permission
scanimage -l no SANE devices found
iscan, simple-scan, and xsane do not work

Epson 4490 Photo as root
sane-find-scanner ok
scanimage -l no SANE devices found
iscan, simple-scan, and xsane do not work

Brother MFC-1910W as user
sane-find-scanner detects a bunch of USB devices including the scanner, but has not enough permission
scanimage -l no SANE devices found
simple-scan and xsane do not work

Brother MFC-1910W as root
sane-find-scanner ok
scanimage -l ok
simple-scan ok
xsane ok

Bo Lundberg (bo-lundberg) wrote :

Epson 2400 photo doesn't work in Iscan (can't send to scanner). Works fine with xsane.

Yves D. Mercier (ymerj) wrote :

Epson v370 photo doesn't work either. Purchased only 3 months ago, it was fully functionnal in zesty. Now totally unusable in artful even with libsane1 1.0.27-1~experimental2ubuntu2.1

Today I managed to bring back my dead Epson V300 alive :-)

1. Install libsane1 1.0.27-1~experimental2ubuntu2.1

2. Install iscan-gt-f720-bundle-1.0.1.x64.deb.tar.gz

3. Copy (or move) the files from /usr/lib/sane (libsane-epkowa.la, libsane-epkowa.so.1, libsane-epkowa.so.1.0.15 in my case) to /usr/lib/x86_64-linux-gnu/sane

4. reboot.

Guess this works with all Iscan depend scanners from Epson

Just for the record

scanimage -L
device `epkowa:interpreter:003:007' is a Epson Perfection V300 flatbed scanner
device `imagescan:esci:networkscan://192.168.50.24:1865' is a Epson XP-540

Iscan, simple-scan, Xsane are working as expected.

BRScan users can you try what happens when copy the files (libsane-brother*) from /usr/lib64/sane/ to /usr/lib/x86_64-linux-gnu/sane.

Maybe the fix for brother scanners is as easy as the one for the epson ones ...

Yves D. Mercier (ymerj) wrote :

Sorry to say that staedtler-przyborski solution did not work for me (epson V370 photo). Deb file is different in my case (iscan-perfection-v370-bundle-1.0.1.x64.deb.tar.gz)

Yves D. Mercier (ymerj) wrote :

Update: Just tried it as root. I works.

Thats interesting. I don't need to be root to scan.

So whats different is the question ? I don't believe it's the different plugin. Iscan is identical I suppose.

Just for completeness:

 apt list --installed |grep -e esci -e iscan -e libsane -e sane-utils

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

esci-interpreter-gt-f720/now 0.1.1-2 amd64 [Installiert,lokal]
iscan/now 2.30.2-2 amd64 [Installiert,lokal]
iscan-data/now 1.36.0-1 all [Installiert,lokal]
libsane-common/now 1.0.27-1~experimental2ubuntu2.1 all [Installiert,lokal]
libsane-hpaio/artful,now 3.17.7+repack0-3 amd64 [installiert]
libsane1/now 1.0.27-1~experimental2ubuntu2.1 amd64 [Installiert,lokal]
sane-utils/now 1.0.27-1~experimental2ubuntu2.1 amd64 [Installiert,lokal]

Are on x-org or wayland ? Can you try what happens if you switch to X-org ?

X-Org or wayland doens't matter. My scanner works with both (verfied).

Do you have a file named 79-udev-epson.rules in /etc/udev/rules.d ?

Mine has the following content:

# chmod device EPSON group
# ACTION=="add", ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666"
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

A Test here showed:

without 79-udev-epson.rules in /etc/udev/rules.d

only 'sudo scanimage -L works'

with 79-udev-epson.rules in /etc/udev/rules.d

no root needed, a simple 'scanimage -L' is sufficient

maybe for the brscan scanners also only the udev rule is missing

try to add
# Brother scanners
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="0255", MODE="0660", GROUP="scanner", ENV{libsane_matched}="yes"

to e.g. /lib/udev/rules.d/60-libsane1.rules

Yves D. Mercier (ymerj) wrote :

I did not have the 79-udev-epson.rules file, so I created one with the content you posted. My scanner works now. No root needed. Many thanks.

My Brother MFC-J220 works now with the 1.0.27-1~experimental2ubuntu2.1 packages.

The brscan3 driver installs files in /usr/lib64 and /usr/lib64/sane.
I linked them by
'sudo ln -sfr /usr/lib64/libbrscandec* /usr/lib/x86_64-linux-gnu'
and
'sudo ln -sfr /usr/lib64/sane/libsane-brother* /usr/lib/x86_64-linux-gnu/sane'

Thanks to staedtler-przyborski for the hint.

@ Hans Schwimmbeck

Great, so we have a fix for brother brscan3 scanners too.

Ah yes, linking is definitely a better way than copying (you may forgive me, my workaround was only a first try).

Now we only need to know if, brscan, brscan2 and brscan4 scanners can be fixed too by linking directories

For Xerox Workcentre 3225 I have mentioned in this and the original sane bug the solution is:
1. Link the files in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane,
2. Add the user that needs to use the scanner to the "lp" group.
Otherwise the "Not a JPEG file: starts with 0x00 0x00" issue persists.

Thanks Mariusz. Can you please specify which files are in /usr/lib/sane (just to make the command below more precise) ?

To summarize we have now the following workarounds (all 64-bit):

1. Brother brscan3

a) 'sudo ln -sfr /usr/lib64/libbrscandec* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/lib64/sane/libsane-brother* /usr/lib/x86_64-linux-gnu/sane'

2. Epson Iscan

a) 'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane'
b) generate '/etc/udev/rules.d/79-udev-epson.rules'
content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

3. Xerox Workcentre 3225

a) 'sudo ln -sfr /usr/lib/sane/* /usr/lib/x86_64-linux-gnu/sane'
b) 'sudo adduser $USER lp'

PeterPall (peterpall) wrote :

You are a genius! My MFC8510 and my Epson WorkForce GT-1500 now work fine...
...now we should forward this info to the sane programmers (perhaps they can make the program look in both the old and the new locations), to Debian - and to the manufacturers: Symlinks isn't hard to create in the postinstall scripts. Perhaps they will add the necessary lines.

> ls -la /usr/lib/sane/
total 40
drwxr-xr-x 2 root root 4096 Oct 27 12:10 .
drwxr-xr-x 147 root root 36864 Oct 17 15:30 ..
lrwxrwxrwx 1 root root 31 Oct 27 12:10 libsane-smfp.so -> /usr/lib/sane/libsane-smfp.so.1
lrwxrwxrwx 1 root root 35 Oct 27 12:10 libsane-smfp.so.1 -> /usr/lib/sane/libsane-smfp.so.1.0.1
lrwxrwxrwx 1 root root 50 Oct 27 12:10 libsane-smfp.so.1.0.1 -> /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1

Xerox has an "universal", script based driver installer available at http://download.support.xerox.com/pub/drivers/WC3225/drivers/linux/en_GB/Xerox_WorkCentre_3225_Linux-Driver.tar.gz

PPDs and about 5 installed binaries, French locale and a bunch of scripts for arm, i386, and x86_64.

In the meanwhile I had a look on different brscan drivers ...

Unfortunately brscan4 has a complete different structure (so at least one real user is needed)

Summary is now:

1. Brother brscan, brscan2, brscan 3

a) 'sudo ln -sfr /usr/lib64/libbr* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/lib64/sane/libsane-brother* /usr/lib/x86_64-linux-gnu/sane'

2. Epson Iscan

a) 'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane'
b) generate '/etc/udev/rules.d/79-udev-epson.rules'
content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

3. Xerox Workcentre 3225

a) 'sudo ln -sfr /usr/lib/sane/libsane-smfp* /usr/lib/x86_64-linux-gnu/sane'
b) 'sudo adduser $USER lp'

I forgot to mention that also needed is something like /etc/udev/rules.d/59-local.rules.
In my upgraded installation it has not changed since 16.04 and looks like this:
---------------
# Brother MFC-J220
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="0259", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

---------------

Of course 'idProduct' has to match the local scanner model, 'lsusb' and 'sane-find-scanner' are your friends.

Dear Hans could you please test if a more generic solution like the one provided by Epson would also work for local attached Brother Scanners ?

A possible Example:

# chmod device BROTHER group
ATTRS{manufacturer}=="BROTHER", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="*", MODE="0777"

Thanks

luca.mg (luca-mg) wrote :

I can confirm that the Epson Perfection 4490 Photo scanner, iscan-gt-x750-bundle-1.0.0.x64 based, works by creating symlinks of the /usr/lib/sane/libsane-epkowa* files into the /usr/lib/x86_64-linux-gnu/sane directory by issuing the command 'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane' as said above; no need to tinker with the udev rules files in my case. This doesn't look like a bug fix to me, it's a workaround, needing a user tweak, libsane1 should look for third party sane drivers (once called backends IIRC) in the "legacy" directories as well as in the new ones, for backward compatibility.

luca.mg (luca-mg) wrote :

The Brother MFC-1910W printer-fax-scanner, brscan4 based, does not work with the symlink trick, the scanner is detected by sane-find-scanner, but is not listed by scanimage -l, and will only work after enabling the root account and issuing the 'su root' and 'xsane' commands in a terminal; a simple sudo xsane won't work. Although it seems to me a permission issue, creating appropriate (to the best of my knowledge!) udev rules files in the /etc/udev/rules.d directory and/or in /lib/udev/rules.d directory has no positive outcome, nor editing the the /lib/udev/rules.d/60-libsane1.rules file; my attempts were using the lines

## Brother MFC-1910W
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="035d", MODE="0666", GROUP="scanner", ENV{libsane_matched}="yes"

with several flavours of the MODE= option (0660 0666 0664 0777 and the like).
Again: if only libsane1 will also look for sane backends in the "legacy" locations other than the new ones perhaps this insane mess would be sorted out.

I don't like MODE="0777" in the Epson derived example.

This works for me and _should_ work for all brscan3 devices:

# Brother brscan3 devices
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="*", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

luca.mg (luca-mg) wrote :

Thank You for Your time Hans, I do not like 0777 as well, but I was shooting in the dark. As stated, I tried
## Brother MFC-1910W
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="035d", MODE="0666", GROUP="scanner", ENV{libsane_matched}="yes" (or 0660 0664 0777 modes)

which should be the equivalent of Your
# Brother brscan3 devices
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="*", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

no joy.

luca.mg (luca-mg) wrote :

PS I'm on brscan 4.

I have no glue why Epson has chosen '0777', maybe it's because they upload a firmware to their scanners ...

Actual summary:

1.Brother:

brscan4 no luck until now (btw. the installer already seems to respect /usr/lib/x86_64-linux-gnu/sane)

brscan, brscan2, brscan3

a) 'sudo ln -sfr /usr/lib64/libbr* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/lib64/sane/libsane-brother* /usr/lib/x86_64-linux-gnu/sane'
c) generate '/etc/udev/rules.d/59-udev-local.rules'
content:
# Brother brscan devices
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="*", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

2. Epson Iscan

a) 'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane'
b) generate '/etc/udev/rules.d/79-udev-epson.rules'
content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

3. Xerox Workcentre 3225

a) 'sudo ln -sfr /usr/lib/sane/libsane-smfp* /usr/lib/x86_64-linux-gnu/sane'
b) 'sudo adduser $USER lp'

@luca.mg

Are you aware of these informations ?

http://stepsilon.com/ubuntu/install-scanner-brother-dcp-7055-ubuntu

"The Brother Linux scanner driver works only with a superuser by default, as noted on the brother solutions site.

If you want to allow normal users to also use the scanner, this is the solution:

Download following deb package. Open a terminal and paste following line

       wget www.brother.com/pub/bsc/linux/dlf/brother-udev-rule-type1-1.0.0-1.all.deb"

Can you please try ?

luca.mg (luca-mg) wrote :

Hi staedtler-przyborski, and thank You for taking the time to further investigate the matter. Yes indeed, I did try to install the brother-udev-rule-type1 package You kindly linked, also tinkering with the various settings, and tested with a later release too, even if both weren't needed in zesty, nor in xenial (I guess that the package was required with earlier ubuntu releases), but it doesn't make any difference: the scanner is found by sane-find-scanner, but is not detected by scanimage -l, and it only works running xsane from the terminal after the 'su root' command, while 'sudo xsane' won't work at all. I'm quite sure that it's a permission issue, but I'm out of ideas as to how to fix it, and using the scanner as root is not a feasible option.

@luca.mg

Im sorry to hear that.

BTW. Are you on wayland or xorg. If wayland, have you tried with xorg ?

luca.mg (luca-mg) wrote :

@staedtler-przyborski
I'm on xorg... I forgot to mention: the Brother scanner only works as root AND with xsane, simple-scan doesn't work at all.

tags: added: patch
175 comments hidden view all 255 comments
luca.mg (luca-mg) wrote :

Hi Michael, are You installing as root or sudo?

luca.mg (luca-mg) wrote :

Hi all, Brother MFC-1910W, new Ubuntu Mate 19.04 install, Brother drivers from https://support.brother.com/g/b/downloadend.aspx?c=as_ot&lang=en&prod=mfc1910w_eu_as&os=128&dlid=dlf006893_000&flang=4&type3=625&dlang=true at first the scanner was not detected, my previous workaround involving libsane-extras is not an option anymore, since the package has been pulled out. What I did is:

1) created the file /etc/udev/hwdb.d/brother4.hwdb with the lines
usb:v04F9p035D*
 libsane_matched=yes

2) created the file /etc/sane.d/dll.d/brother4 with the line
brother4

the scanner works with no further tinkering, creating symlinks and the like.
HTH Luca

luca.mg (luca-mg) wrote :

Hi again, Epson Perfection 4490 Photo, new Ubuntu Mate 19.04 install, iscan-bundle-1.0.0.x64.deb.tar.gz driver, make sure to add the line 'epkowa'to the /etc/sane.d/dll.conf file first; xsane gave a 'Access to resource has been denied' message as a regular user, same with 'sudo xsane' from a terminal, what I did is:

1) from a terminal enter 'sudo passwd root' and create a password for the root user, when done
2) enter 'su root' and provide the newly created password, when root
3) run 'xsane' despite the warnings AND scan a page (a previous attempt without scanning didn't work), after that, believe it or not, the scanner works, I do not really understand why and how, but this is it, though YMMV.

Regards, Luca

Michael (m-doble) wrote :

Dear Luca, I'm new to linux but to answer your question, I think I used the commandes SUDO. But what's the difference between root and sudo?

luca.mg (luca-mg) wrote :

Hi Michael, sudo is enough for driver installation, if You did not sudo that is why install failed. Root is the real system administrator, not needed for this task.

REegards, Luca

PeterPall (peterpall) wrote :

If the scanner can be found only by the superuser that might indicate that an udev rule that allows scanner access for ordinary users is missing. Or that this udev rule gives scanner access to an user group you happen not to be part of...

luca.mg (luca-mg) wrote :

Hi Peter, if the above is addressed to me, the Epson scanner works for regular users after the first scan as root, I do not get the reason why, but this is it.
Thank You for stepping in.

PeterPall (peterpall) wrote :

Then perhaps uploading the firmware to the scanner can only be done as root, for some reason.
Does the output of susb -v change after scanning for the first time?

Download full text (3.4 KiB)

Just a reminder to those of us using Brother DCP or MFP's: I repeatedly
find that the only way to properly install the printer and scanner drivers
is to use the "Installer Script"(i.e. 09/13/2018
(2.2.1-1)) provided on the model downloads page(see below) and to follow
the directions given _explicitly_(to-the-letter, no exceptions)! I've tried
to install a recently updated scanner driver(i.e. 01/21/2019
(0.4.7-1)) by itself as an upgrade to the currently installed one and even
re-ran the setup command(i.e. Brsaneconfig4 -a name=(name your device)
model=(model name) ip=xx.xx.xx.xx) for my network(Wi-Fi) DCP-L2550DW, but
it does not work that way. I can't stress, enough, the apparent need to
re-run the "Installer Script", exactly as shown--below, in order for
everything to work!

How to Install

Step1. Download the tool.(linux-brprinter-installer-*.*.*-*.gz)

The tool will be downloaded into the default "Download" directory.
(The directory location varies depending on your Linux distribution.)
e.g. /home/(LoginName)/Download

Step2. Open a terminal window.

Step3. Go to the directory you downloaded the file to in the last step. By
using the cd command.

e.g. cd Downloads

Step4. Enter this command to extract the downloaded file:

*Command: gunzip linux-brprinter-installer-*.*.*-*.gz*

e.g. gunzip linux-brprinter-installer-2.1.1-1.gz

Step5. Get superuser authorization with the "*su*" command or "*sudo su*"
command.

Step6. Run the tool:

*Command: bash linux-brprinter-installer-*.*.*-* Brother machine name *
e.g. bash linux-brprinter-installer-2.1.1-1 MFC-J880DW

Step7. The driver installation will start. Follow the installation screen
directions.

 When you see the message "Will you specify the DeviceURI ?",

 For USB Users: Choose N(No)
 For Network Users: Choose Y(Yes) and DeviceURI number.

The install process may take some time. Please wait until it is complete.

On Tue, May 7, 2019 at 7:41 AM PeterPall <email address hidden> wrote:

> Then perhaps uploading the firmware to the scanner can only be done as
> root, for some reason.
> Does the output of susb -v change after scanning for the first time?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
> Confirmed
>
> Bug description:
> Many scanners can no more be used since sane has changed something:
> The 3rd-party plug-in the vendor provides as .deb package will still
> install. But the scanner is no more recognized.
>
> Scanners that are affected are(besides others):
> - Epson Perfection V10
> - Epson Perfection V1000
> - Epson WorkForce GT-1500
> - Brother MFC-8510DN
> - Epson Perfection V33
>
> It is to note that the probability that the scanner manufacturers fix
> things others broke is below 100%.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: libsane1 1.0.27-1~experimental2ubuntu2
> Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
> ApportVersion: 2.20.7-0ubuntu3.1
> Architecture: amd64
> Date: Fri Oct 27 12:35:52 201...

Read more...

luca.mg (luca-mg) wrote :

@ PeterPall: regarding the Epson scanner, yes it could be the firmware upload, the first root scan took time, I thought it was the scanner warming up longer than usual and not catching up, but I allowed time and it finally went through, so You may very well be right. I did not run lsusb -v, just a plain lsub, but before the root scan the scanner was detected as an epkowa driven unknown model, after the root scan it is detected with the proper model name.

@ Chris Rainey: regarding the Brother MFP, I can confirm that I ran the installer script and not the available deb packages.

Chris Rainey (ckrzen) wrote :

@luca.mg: have you checked for firmware updates? My Brother DCP-L2550DW can
update from the web interface in the system tools/administration tab and
there have been a few updates in the last year.

On Tue, May 7, 2019 at 2:45 PM luca.mg <email address hidden> wrote:

> @ PeterPall: regarding the Epson scanner, yes it could be the firmware
> upload, the first root scan took time, I thought it was the scanner
> warming up longer than usual and not catching up, but I allowed time and
> it finally went through, so You may very well be right. I did not run
> lsusb -v, just a plain lsub, but before the root scan the scanner was
> detected as an epkowa driven unknown model, after the root scan it is
> detected with the proper model name.
>
> @ Chris Rainey: regarding the Brother MFP, I can confirm that I ran the
> installer script and not the available deb packages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
> Confirmed
>
> Bug description:
> Many scanners can no more be used since sane has changed something:
> The 3rd-party plug-in the vendor provides as .deb package will still
> install. But the scanner is no more recognized.
>
> Scanners that are affected are(besides others):
> - Epson Perfection V10
> - Epson Perfection V1000
> - Epson WorkForce GT-1500
> - Brother MFC-8510DN
> - Epson Perfection V33
>
> It is to note that the probability that the scanner manufacturers fix
> things others broke is below 100%.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: libsane1 1.0.27-1~experimental2ubuntu2
> Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
> ApportVersion: 2.20.7-0ubuntu3.1
> Architecture: amd64
> Date: Fri Oct 27 12:35:52 2017
> EcryptfsInUse: Yes
> SourcePackage: sane-backends
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
>

PeterPall (peterpall) wrote :

Then the answer is simple: extend the udev file with the usb if of the scanner without firmware so use will give you write access to this device, too. Once that is done sane can upload the firmware, the scanner can identify itself as the model you have bought and you can scan. Seems like we should collect the Epson usb IDs somewhere...

luca.mg (luca-mg) wrote :

@ Chris Rainey: no such a thing in my system.

@ PeterPall: the scanner works properly now, it only didn't on the very first time using it. Weird, isn't it?

PeterPall (peterpall) wrote :

@Luca-mg: What your computer sees is the following:
 - You attach a device whose USB ID doesn't match any udev rule => the device is accessible for the root user only.
 - then you as the root user start a program that uploads something to the device.
 - the device disconnects and
 - a new device connects, this time using an USB ID there is an udev rule for. This rule tells the device is a scanner. You are in the group "scanner" => You can use it without root rights.

What you need is an udev rule that tells the system that the USB ID your device has before its firmware is uploaded is a scanner, too. As soon as udev knows that this device is a scanner it will give you the necessary rights to upload the firmware without being root.

Gunnar Hjalmarsson (gunnarhj) wrote :

To the extent this bug is similar to the linked Debian bug, it was fixed in Ubuntu 19.04, so I marked it as "Fix Released". OTOH, in that case there is a need to backport the fix to Ubuntu 18.04, and therefore I added a bionic bug task.

Changed in sane-backends (Ubuntu):
status: Confirmed → Fix Released
Changed in sane-backends (Ubuntu Bionic):
assignee: nobody → Gunnar Hjalmarsson (gunnarhj)
importance: Undecided → High
status: New → In Progress
Changed in sane-backends (Debian):
status: Unknown → Fix Released
description: updated
Gunnar Hjalmarsson (gunnarhj) wrote :

I have uploaded a proposed fix of sane-backends to this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

If you are on 18.04 and affected by this bug, it would be great if you could install from the PPA, test to find out if it makes a difference, and report your observations in a comment here.

tags: added: regression-release
Gunnar Hjalmarsson (gunnarhj) wrote :

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?

Download full text (6.5 KiB)

I am having issues myself, but I think mine are related to running ubuntu
in a VM on Windows.

I got IT to set aside an unused desktop pc for me to load and run it on
(they say its now on my desk...). Should have results tomorrow or Tuesday.

On Sun, Jun 30, 2019 at 6:20 PM Gunnar Hjalmarsson <
<email address hidden>> wrote:

> 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 subscribed to the bug
> report.
> 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 ...

Read more...

Gunnar Hjalmarsson (gunnarhj) wrote :

I submitted <https://bugs.debian.org/931297> about the /usr/lib64/sane thing.

renbag (renbag) wrote :

@Gunnar Hjalmarsson:
in bionic I had to install libusb-0.1-4 to be able to scan with my MFC-440CN (brscan2), because it ships libusb-1.0-0 by default.

Gunnar Hjalmarsson (gunnarhj) wrote :

@renbag: Tried that, but didn't help for me.

Actually it would have been weird if it had made a difference, since sane-backends has been built with libusb-1.0-0-dev for a long time, which make libsane/libsane1 and sane-utils depend on libusb-1.0-0.

I can scan with my MFC-240C on both 16.04 and 19.04.

With that said, and if you are still on bionic, it would be great if you could install from the PPA and let us know how it goes.

Gunnar Hjalmarsson (gunnarhj) wrote :

I made a new attempt with bionic, and yes!!

@renbag: You were absolutely correct, and it's brscan2 that requires the presence of libusb-0.1-4. I think this explains it:

$ ldd /usr/lib64/sane/libsane-brother2.so.1.0.7 | grep libusb
 libusb-0.1.so.4 => /lib/x86_64-linux-gnu/libusb-0.1.so.4 (0x00007f79f3e57000)

libusb-0.1.so.4 was used when libsane-brother2.so.1.0.7 was compiled, in other words, and Brother should ideally have stated the libusb-0.1-4 package (which installs that .so file) as a depend in the brscan2 .deb package.

So now I have been able to confirm that the proposed package for bionic in the PPA makes a difference. Would still appreciate more feedback before starting to look for a sponsor who can upload.

renbag (renbag) wrote :

I confirm that the packages in the proposed PPA allow to scan with a Brother MFC-440CN (brscan2).
I tried booting directly from a bionic USB stick and followed the steps listed on comment #232 (except adding a libsane rule, which is not needed in my case) and additionally installed libusb-0.1-4.
Thanks to Gunnar for the fix!

Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks @renbag. With your help I'm now confident enough to proceed with the principal bionic change.

As regards support for the /usr/lib64/sane directory, I would like to know if that change will be accepted in Debian before acting; please see <https://bugs.debian.org/931297#20>. So right now I'm waiting for an answer to my question in that message.

Gunnar Hjalmarsson (gunnarhj) wrote :

I decided to break out the /usr/lib64/sane thing to bug #1835220, so we can proceed with the more important bionic fix.

description: updated
description: updated

Hello PeterPall, or anyone else affected,

Accepted sane-backends into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane-backends/1.0.27-1~experimental3ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in sane-backends (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Gunnar Hjalmarsson (gunnarhj) wrote :

Since I have an old Brother device whose drivers are installed via brscan2, the proposed change (which adds support for drivers located in /usr/lib/sane) doesn't really apply to me. But I worked around that.

The general preparations according to comment #232 are there, and in addition to that I installed the libusb-0.1-4 package. However, I dropped the ldconfig trick to make .so files in /usr/lib64 shared libraries.

Now to the workaround. I added some symlinks to pretend that the driver files are located in /usr/lib and /usr/lib/sane:

$ ls -l /usr/lib/libbr* /usr/lib/sane
lrwxrwxrwx 1 root root 28 jul 3 21:57 /usr/lib/libbrcolm2.so -> ../lib64/libbrcolm2.so.1.0.1
lrwxrwxrwx 1 root root 31 jul 3 21:57 /usr/lib/libbrscandec2.so -> ../lib64/libbrscandec2.so.1.0.0
lrwxrwxrwx 1 root root 13 jul 3 21:57 /usr/lib/sane -> ../lib64/sane

With that setup I first tested scanning with the sane-backends packages in bionic-release. Result (simple-scan):

"No scanners detected"

Then I installed version 1.0.27-1~experimental3ubuntu2.1 of libsane1, libsane-common, and sane-utils from bionic-proposed. After that I could scan using either simple-scan or xsane.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Benjamin Terweiden (avoca) wrote :

Samsung Xpress M2070
After installing the drivers (sudo sh install.sh)

this fixed it:
cd /usr/lib/x86_64-linux-gnu/sane

sudo ln -s /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1 /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1

Download full text (4.9 KiB)

Hello I'm new to Linux Mint. Can any one help me with getting the scanner of Brother DCP750 to work ?
With much thanks,
Michael

Le 10 juil. 2019 19:35, Benjamin Terweiden <email address hidden> a écrit :

Samsung Xpress M2070
After installing the drivers (sudo sh install.sh)

this fixed it:
cd /usr/lib/x86_64-linux-gnu/sane

sudo ln -s /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1
/usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1

--
You received this bug notification because you are subscribed to the bug
report.
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:
  Fix Committed
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  To the sponsor: Please upload to bionic using the attached sane-
  backends_lp1728012_bionic.debdiff.

  [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 ...

Read more...

Łukasz Zemczak (sil2100) wrote :

Normally I'd say we should wait for verification using a test case that does not involve any workarounds, but seeing the actual bug-fix I think it might be safe to release it with the testing it got already. This seems to be a logical change.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sane-backends - 1.0.27-1~experimental3ubuntu2.1

---------------
sane-backends (1.0.27-1~experimental3ubuntu2.1) bionic; urgency=medium

  * debian/patches/0125-multiarch_dll_search_path.patch:
    - Reactivated and refreshed to allow driver from non-multiarch
      directories (Closes: #910103, LP: #1728012).
      It was fixed in disco, and this is the related Debian commit:
      https://jff.email/cgit/sane-backends.git/commit/?id=a94d3a93

 -- Gunnar Hjalmarsson <email address hidden> Wed, 03 Jul 2019 15:53:00 +0200

Changed in sane-backends (Ubuntu Bionic):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for sane-backends has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Gunnar Hjalmarsson (gunnarhj) wrote :

So finally this has been fixed also in 18.04. I want to thank Steven Santos who called my attention to the problem as well as the solution.

Download full text (5.7 KiB)

Hi Lukasz,

I am an Ubuntu user but *not* a technician so please bear with me. Your
e-mail says "The verification of the Stable Release Update for
sane-backends has
completed successfully and the package has now been released to -updates."
 Do you know what release will contain the fix and when the release will
occur?
(I updated my system a couple of minutes ago and the scanner is still not
working.) Should I have checkmarked Pre-released updates Bionic-proposed
in the Developer Options tab of the update settings - see picture? (The
release I'm using is 18.04.02) Thanks!

[image: image.png]

On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak <email address hidden>
wrote:

> The verification of the Stable Release Update for sane-backends has
> completed successfully and the package has now been released to
> -updates. Subsequently, the Ubuntu Stable Release Updates Team is being
> unsubscribed and will not receive messages about this bug report. In
> the event that you encounter a regression using the package from
> -updates please report a new bug using ubuntu-bug and tag the bug report
> regression-update so we can easily find any regressions.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1822360).
> 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:
> Fix Released
> Status in sane-backends package in Debian:
> Fix Released
>
> Bug description:
> To the sponsor: Please upload to bionic using the attached sane-
> backends_lp1728012_bionic.debdiff.
>
> [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
> -...

Read more...

Gunnar Hjalmarsson (gunnarhj) wrote :

Hi Phil,

Łukasz will probably not see your question. But this fix is about Ubuntu 18.04, and no, the "Pre-released updates" option does not need to be checked - the "Recommended updates" option in the "Updates" tab is sufficient (and that one is checked by default).

To confirm that you got the fix you can open a terminal window and run this command:

dpkg-query -W libsane1 libsane-common sane-utils

The version you should have is 1.0.27-1~experimental3ubuntu2.1

Also, please note that there are multiple possible reasons why your scanner refuses to scan. This fix addresses one particular issue which was a regression compared to Ubuntu 16.04.

To get help with your particular problem, please use e.g. Ask Ubuntu or some other support resource as mentioned here:

https://ubuntu.com/support/community-support

This is a bug report intended to report, investigate and keep track of bugs. It's not a support channel.

Hi,

I received the update yesterday. Success!!!
Could scan without issues and my scanner got recognized with all features
working fine!
Thanks a lot, kudos

Manuel SCHULTE
*Managing Director, Olympus Consulting sprl*
*gsm :* +32(0)498 881 718
*mail :* <email address hidden>
*web :* http://www.olympusconsulting.eu/

Le lun. 22 juil. 2019 à 01:55, Gunnar Hjalmarsson <
<email address hidden>> a écrit :

> Hi Phil,
>
> Łukasz will probably not see your question. But this fix is about Ubuntu
> 18.04, and no, the "Pre-released updates" option does not need to be
> checked - the "Recommended updates" option in the "Updates" tab is
> sufficient (and that one is checked by default).
>
> To confirm that you got the fix you can open a terminal window and run
> this command:
>
> dpkg-query -W libsane1 libsane-common sane-utils
>
> The version you should have is 1.0.27-1~experimental3ubuntu2.1
>
> Also, please note that there are multiple possible reasons why your
> scanner refuses to scan. This fix addresses one particular issue which
> was a regression compared to Ubuntu 16.04.
>
> To get help with your particular problem, please use e.g. Ask Ubuntu or
> some other support resource as mentioned here:
>
> https://ubuntu.com/support/community-support
>
> This is a bug report intended to report, investigate and keep track of
> bugs. It's not a support channel.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728012
>
> Title:
> Many 3rd party scanner drivers are broken by a sane change
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
>

Download full text (7.1 KiB)

Worked for me...
~$ uname -a
Linux hades 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
~$ lsb_release -a
LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

Manuel SCHULTE
*Managing Director, Olympus Consulting sprl*
*gsm :* +32(0)498 881 718
*mail :* <email address hidden>
*web :* http://www.olympusconsulting.eu/

Le dim. 21 juil. 2019 à 23:35, Phil <email address hidden> a écrit :

> Hi Lukasz,
>
> I am an Ubuntu user but *not* a technician so please bear with me. Your
> e-mail says "The verification of the Stable Release Update for
> sane-backends has
> completed successfully and the package has now been released to -updates."
> Do you know what release will contain the fix and when the release will
> occur?
> (I updated my system a couple of minutes ago and the scanner is still not
> working.) Should I have checkmarked Pre-released updates Bionic-proposed
> in the Developer Options tab of the update settings - see picture? (The
> release I'm using is 18.04.02) Thanks!
>
>
> [image: image.png]
>
>
>
> On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak <<email address hidden>
> >
> wrote:
>
> > The verification of the Stable Release Update for sane-backends has
> > completed successfully and the package has now been released to
> > -updates. Subsequently, the Ubuntu Stable Release Updates Team is being
> > unsubscribed and will not receive messages about this bug report. In
> > the event that you encounter a regression using the package from
> > -updates please report a new bug using ubuntu-bug and tag the bug report
> > regression-update so we can easily find any regressions.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1822360).
> > 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:
> > Fix Released
> > Status in sane-backends package in Debian:
> > Fix Released
> >
> > Bug description:
> > To the sponsor: Please upload to bionic using the attached sane-
> > backends_lp1728012_bionic.debdiff.
> >
> > [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
...

Read more...

Miles Wolbe (k-miles) wrote :

Ran into the same scanner issue today with a Brother MFC-6490CW under Ubuntu 18.04 (factory installed by Dell and fully updated before attempting printer/scanner install). Found pdc's post on askubuntu.com ( https://askubuntu.com/a/1054065/314730 ) first, which linked to staedtler-przyborski's symlink answer ( https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/comments/25 ). Worked a treat - thanks so much!

Gunnar Hjalmarsson (gunnarhj) wrote :

@Miles: Yes, bug #1835220 is still open, unfortunately. Good that you found your way.

Phil (phlcsp) wrote :
Download full text (12.6 KiB)

Just wanted you to know the scan function on my OfficeEdge Pro5500 is
working again! I installed the following driver from Lexmark Support
(Australia).

lexmark_network-scan-linux-glibc2_04082019_x86_64.deb

Regards

On Mon, Jul 22, 2019 at 4:31 PM Manuel <email address hidden> wrote:

> Worked for me...
> ~$ uname -a
> Linux hades 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019
> x86_64 x86_64 x86_64 GNU/Linux
> ~$ lsb_release -a
> LSB Version:
> core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
> Distributor ID: Ubuntu
> Description: Ubuntu 18.04.2 LTS
> Release: 18.04
> Codename: bionic
>
> Manuel SCHULTE
> *Managing Director, Olympus Consulting sprl*
> *gsm :* +32(0)498 881 718
> *mail :* <email address hidden>
> *web :* http://www.olympusconsulting.eu/
>
>
> Le dim. 21 juil. 2019 à 23:35, Phil <email address hidden> a écrit :
>
> > Hi Lukasz,
> >
> > I am an Ubuntu user but *not* a technician so please bear with me. Your
> > e-mail says "The verification of the Stable Release Update for
> > sane-backends has
> > completed successfully and the package has now been released to
> -updates."
> > Do you know what release will contain the fix and when the release will
> > occur?
> > (I updated my system a couple of minutes ago and the scanner is still not
> > working.) Should I have checkmarked Pre-released updates Bionic-proposed
> > in the Developer Options tab of the update settings - see picture? (The
> > release I'm using is 18.04.02) Thanks!
> >
> >
> > [image: image.png]
> >
> >
> >
> > On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak <
> <email address hidden>
> > >
> > wrote:
> >
> > > The verification of the Stable Release Update for sane-backends has
> > > completed successfully and the package has now been released to
> > > -updates. Subsequently, the Ubuntu Stable Release Updates Team is
> being
> > > unsubscribed and will not receive messages about this bug report. In
> > > the event that you encounter a regression using the package from
> > > -updates please report a new bug using ubuntu-bug and tag the bug
> report
> > > regression-update so we can easily find any regressions.
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1822360).
> > > 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:
> > > Fix Released
> > > Status in sane-backends package in Debian:
> > > Fix Released
> > >
> > > Bug description:
> > > To the sponsor: Please upload to bionic using the attached sane-
> > > backends_lp1728012_bionic.debdiff.
> > >
> > > [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...

Displaying first 40 and last 40 comments. View all 255 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.