Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52358 - [lshw] Crash when running as non-root
Attached to Project:
Community Packages
Opened by Nicolas I. (IooNag) - Tuesday, 03 January 2017, 22:19 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 05 January 2017, 13:59 GMT
Opened by Nicolas I. (IooNag) - Tuesday, 03 January 2017, 22:19 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 05 January 2017, 13:59 GMT
|
DetailsDescription:
When running lshw as a simple user, I get: $ lshw WARNING: you should run this program as super-user. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc zsh: abort (core dumped) lshw The program works fine when running as root. Moreover "strace lshw" reveals that the crash happens a few syscalls after 'open("/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) = -1 EACCES (Permission denied)'. This bug has been reported to upstream a few months ago in http://www.ezix.org/project/ticket/716 and fixed by commit https://ezix.org/src/pkg/lshw/commit/fbdc6ab15f7eea0ddcd63da355356ef156dd0d96 . Could you please backport this patch to lshw B.02.18 package? Additional info: * package version: lshw B.02.18-1 Steps to reproduce: * run lshw as a non-root user |
This task depends upon