[Bug 1590994] Re: [Regression] crash in scan_dmi_sysfs when running as non-root

[Chris J Arges]

Hello dann, or anyone else affected,

Accepted lshw into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lshw/02.17-1.1ubuntu3.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lshw (Ubuntu Xenial)
       Status: Confirmed => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lshw in Ubuntu.
https://bugs.launchpad.net/bugs/1590994

Title:
  [Regression] crash in scan_dmi_sysfs when running as non-root

Status in lshw:
  Unknown
Status in lshw package in Ubuntu:
  Fix Released
Status in lshw source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  lshw crashes when run as non-root:

  Though it does warn before crashing that it should be run as super-
  user, it should fail gracefully - not abort and dump core. A number of
  users have been hitting this since the regression has been introduced:

  https://errors.ubuntu.com/problem/3ef7206b4102c14c8741b44fde30b21b4a571bbe

  [Test Case]
  ubuntu at lshw:~$ lshw
  WARNING: you should run this program as super-user.
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted (core dumped)

  [Regression Risk]
  The fix I've proposed[*] only comes into play when lshw is about to crash, so regression risk should be minimal.

  [*] https://github.com/lyonel/lshw/pull/14

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/1590994/+subscriptions