On Thu, 18 Jul 2019 21:53:59 +0100 Ken Moffat via blfs-support 
<[email protected]> wrote:

> On Thu, Jul 18, 2019 at 06:04:13PM +0200, Stephen Berman via blfs-support 
> wrote:
>> On Thu, 18 Jul 2019 09:49:00 +0200 Christopher Gregory via blfs-support
>> <[email protected]> wrote:
>>
>> >
>> > Hello,
>> >
>> > Debian have version 3.18.12 of hplip and have 32 patches for it:
>> >
>> > http://deb.debian.org/debian/pool/main/h/hplip/hplip_3.18.12+dfsg0.orig.tar.xz
>> >
>> > The above link is the original source code.
>> >
>> > http://deb.debian.org/debian/pool/main/h/hplip/hplip_3.18.12+dfsg0-2.debian.tar.xz
>> >
>> > The above link contains the patches.  Be warned, the files extract to the
>> > directory debian.
>>
>> Thanks for these links.  I'm not sure but think I read somewhere that
>> the scanner in my device only works under Linux with hplip 3.19.  At any
>> rate, I also have openSUSE on this machine and it uses 3.19.3 and the
>> scanner works there.  Since the 3.19.6 plugin made scanimage crash, I
>> downloaded, built and installed 3.19.3, but sadly with the same result:
>> printing is fine but when I installed the plugin, scanimage segfaulted.
>> Since it works in openSUSE and the plugin is a binary from HP, there
>> must be something the plugin needs that's missing in my BLFS.  I ran
>> scanimage under gdb and got this backtrace:
>>
>
> Since it work in OpenSuSe, you could try looking at the srpm - for
> Sane, I suppose, or else for its listed dependencies - for patches or
> missing dependencies.

Yes, I will definitely try to figure out what openSUSE installs to see
what I'm missing.

>> Thread 1 "scanimage" received signal SIGSEGV, Segmentation fault.
>> _IO_fgets (buf=buf@entry=0x7fffffffb9f0 "", n=n@entry=128, fp=fp@entry=0x0)
>>     at iofgets.c:47
>> 47      iofgets.c: No such file or directory.
>
> Google suggests this happens because the result of fopen is not
> checked before using fgets to read from the file.  And iofgets.c is
> part of glibc.

I don't know what to do with that information...

>> (gdb) bt
>> #0  _IO_fgets (buf=buf@entry=0x7fffffffb9f0 "", n=n@entry=128, 
>> fp=fp@entry=0x0)
>>     at iofgets.c:47
>> #1  0x00007ffff76c22b6 in fgets (__stream=0x0, __n=128, __s=0x7fffffffb9f0 
>> "")
>>     at /usr/include/x86_64-linux-gnu/bits/stdio2.h:263
>> #2  sane_hpgt2500_init (version_code=<optimized out>,
>>     authorize=<optimized out>) at canopus.c:618
>> #3  0x00007ffff7fa7f70 in init (be=be@entry=0x4127c0) at dll.c:637
>> #4  0x00007ffff7fa8976 in sane_dll_get_devices (
>>     device_list=device_list@entry=0x7fffffffbbf8,
>>     local_only=local_only@entry=0) at dll.c:1078
>> #5  0x00007ffff7f94c35 in sane_get_devices (dl=dl@entry=0x7fffffffbbf8,
>>     local=local@entry=0) at dll-s.c:17
>> #6  0x0000000000402847 in main (argc=2, argv=0x7fffffffe038)
>>     at scanimage.c:2102
>>
>> I'm not sure I did this right and don't know how to find out what file
>> or directory couldn't be found (it looks like it's an empty file name
>> and the file pointer is a NULL pointer, which presumably caused the
>> crash).  Can anyone here give me any tips?
>>
>> Steve Berman
>
> That item #4 makes me think you are using scanimage -L (or else
> scanimage invokes that).  One oldish post re OpenSuSe which I saw a
> few minutes ago mentioned changing udev permissions.  If this is a
> usb scanner, does it show up in lsusb, and is it writable (sorry, no
> idea how to fix that if it isn't, but maybe your OpenSuse install
> has a udev rule for it).

I used scanimage -L but I also get the same segfault and backtrace with
just scanimage without a switch.  As for the udev rules, I didn't have
to manually add or adjust anything in openSUSE (maybe hplip did it), and
I don't see a rule there that applies specifically to my device model,
though there are quite a lot of HP devices listed which aren't in the
BLFS list; but in both systems, the udev MODE attribute is 0664 in all
scanner entries, so no difference there.

Somehow installing the hplip plugin must have altered a library or file
that scanimage uses, otherwise I don't see why it should crash; maybe
find can help me find out which.

Steve Berman
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to