On Thu, Jul 18, 2019 at 11:50:03PM +0200, Stephen Berman wrote:
> On Thu, 18 Jul 2019 21:53:59 +0100 Ken Moffat via blfs-support
> <[email protected]> wrote:
>
> 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...
>
Me neither! I think it means that the binary wants to open
something and assumes it must be present. But given the weirdnesses
of devices attached to usb ports (e.g. my epson usb printer claims
to have something else - usb storage, I think), it might want to
write to it (e.g. group write permission).
Christopher replied with a list of what hp expects to be installed
(although suggesting that Qt >= 3.3 is needed doesn't give a lot of
confidence for current versions of everything), I would check that
list against what you have in both LFS and OpenSuSe. And since we
none of us have any idea what the binary is likely to do, perhaps
check ownership of those files, the binary, and general system files
on both systems.
People have been known to use package management approaches which
give every package a different owner, I'm sure there might be other
approaches that can also cause ownership/permission problems in odd
corner cases.
ĸen
--
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
-- Jefferson Airplane, White Rabbit
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
