[sane-devel] XSANE fails to detect any scanner.

Jörn-Ingo Weigert jiweigert at gmail.com
Tue May 8 00:08:40 BST 2018

Aveek Basu <aveek.basu at lexmark.com> schrieb am Mo., 7. Mai 2018, 14:08:

> Hi Olaf \ Suzuki \ Jörn,
> Thanks for all your response. Below are our observations with respect to
> Ubuntu 16.04(x64), 16.10(x64), 17.10(x86) & 17.10(x64). Also mentioned
> are the workarounds which make things working:

Hello Aveek,
either creating a softlink, or manually copying the related lexmark-scanner
libraries into the system-specific sane folder would do the trick, yes.
However, the best way would be, if your install script would be kicked out
and you use the package scripts for pre- and post installation as
favourites and forced by Debian based system using .deb-packaging
management (dpkg / apt).

Doing this by a manually created install.sh is really a bad idea, if it is
not constantly maintained.

If you are forced by management to use your install-script, then I would
recommend, that you update it with a function to find out the correct
lib-path to install your driver. An example to do this are listed on the
website I send before.

Regarding to libusb-0.1:
Afaik Sane has changed from libusb to libusb-1.x in Sane 1.0.27.
Giving the workaround to parallel install the old version may help but
could produce side effects which are not wanted.

> What I understand from your earlier notes, there has been some changes in
> the way how Debian based distributions arrange their libraries to add "multiarch"
> support. So does this simply mean we need to handle it out from our scan
> driver?
In the way to update your install script or use the regular install scripts
as update your dependencies for libusb to use the actual version, yes.

> Aveek

Kind regards,
Jörn-Ingo Weigert

> On Sun, May 6, 2018 at 9:33 AM, Olaf Meeuwissen <paddy-hack at member.fsf.org
> > wrote:
>> Hi Aveek, Toshiya, Oliver, list,
>> suzuki toshiya writes:
>> > Checking Ubuntu-16.04.04 LTS, drivers are located in
>> > /usr/lib/x86_64-linux-gnu/sane/, not /usr/lib64, as far
>> > as I use the binary packages by Ubuntu.
>> Correct.  Debian based distributions have rearranged where libraries
>> (and header files) are installed to add "multiarch" support.
>> See https://wiki.debian.org/Multiarch for details.
>> > So, it looks correct. I'm afraid that your system
>> > mixes i386 binaries & amd64 binaries, or, something
>> > built by yourself. could you post more about your
>> > system?
>> > Aveek Basu wrote:
>> >> Hi
>> >>
>> >> This is Aveek from Lexmark - Driver Product Engineering team. It has
>> >> recently come to our notice that XSANE fails to detect our scanners
>> I expect the same result with *any* SANE frontend, not just XSane.
>> >> XSANE tries to read the driver files from /usr/lib/sane whereas the
>> >> files are present in /usr/lib64/sane. Due to this, XSANE is not able
>> >> to detect any scanner.
>> >>
>> >> This issue is being observed from Ubuntu 16.04. Could you please help
>> >> us understand if it is a bug or a change in behaviour.
>> You should see the same in Ubuntu 14.04 and perhaps even in 12.04 as
>> that is when the first multiarch changes started.
>> I'm pretty sure this is a bug in your binary packages.
>> Hope this helps,
>> --
>> Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
>>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>>  Support Free Software                        https://my.fsf.org/donate
>>  Join the Free Software Foundation              https://my.fsf.org/join
> --
> Regards,
> Aveek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20180507/07668efb/attachment.html>

More information about the sane-devel mailing list