On Mon, 18 Jun 2018 at 06:22, Ed Greshko <ed.greshko@greshko.com> wrote:
On 06/18/18 16:41, Bob Goodwin wrote:
> I don't have much hope there, the problem needs to be fixed before I upgrade to F28
> but I need to establish priorities at times.
>
> The last screen-full displayed on my monitor for [root@Box10 bobg]# strace lshw -

Well, the last part of what you see looks like this...

>
> openat(AT_FDCWD, "/etc/usb.ids", O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> openat(AT_FDCWD, "/usr/local/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> openat(AT_FDCWD, "/usr/share/lshw/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> openat(AT_FDCWD, "/usr/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> openat(AT_FDCWD, "/sys/kernel/debug/usb/devices", O_RDONLY) = -1 EPERM (Operation
> not permitted)
> openat(AT_FDCWD, "/proc/bus/usb/devices", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x74} ---
> +++ killed by SIGSEGV (core dumped) +++
> Segmentation fault (core dumped)
>

While on my system it this at that point...

openat(AT_FDCWD, "/etc/usb.ids", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/local/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/usr/share/lshw/usb.ids", O_RDONLY) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/usr/share/usb.ids", O_RDONLY) = -1 ENOENT (No such file or directory)
access("/sys/kernel/debug/usb/devices", F_OK) = 0
openat(AT_FDCWD, "/sys/kernel/debug/usb/devices", O_RDONLY) = -1 EPERM (Operation not
permitted)
access("/proc/bus/usb/devices", F_OK)   = -1 ENOENT (No such file or directory)

I don't know the significance in the difference.  Many times I've found the segfault
to be due to some library issue and it is clear as to where to look.  Maybe someone
else knows more. 

lshw is often used to examine hardware when install problems are encountered so 
should not depend on any but the most basic external libraries.  It could be useful 
to try "lshw --disable usb" and to compare "lshw --version" and "ldd /usr/bin/lshw"
on working and broken systems.   

Please note that fedora depends on the collective work of users, and users have
some obligation to understand this sort of problem so others don't encounter it 
in the future.
 


--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/U7NIVFTJVGHHULVPP5ZGAF4JJVB5THSM/


--
George N. White III