Hello again, I've built the version from Testing locally and with this I've found that the problem has been a more priorised link /usr/lib64/sane/libsane.so.1 which becomes created to a /usr/lib64/sane/libsane-brother3.so.1.0.7. The brother3.so is from a manually installed deb-file for my Brother network printer.
But I've no idea why the libsane.so.1 link is created during installation of libsane1 package to this ...brother3.so... After deleting the wrong link, it uses the correct /usr/lib/x86_64-linux-gnu/libsane.so.1 from libsane1 package and the scanimage tool works. Instead of deleting the link I've replaced it now with a new link targeting the correct /usr/lib/x86_64-linux-gnu/libsane.so.1. In the hope it stays in place for the future. Is it possible that the libsane-brother3.so.1.0.7 is found with a glob like libsane*so.* and wrongly linked during libsane-common, libsane1 or sane-utils package install?
