lshw crashes with 'std::bad_alloc' and core dump if not run as root

Bug #1594344 reported by Byte Commander
This bug report is a duplicate of:  Bug #1593233: lshw crashes on the 16.04 release. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lshw (Arch Linux)
New
Undecided
Unassigned
lshw (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My System is Ubuntu 16.04, 64 bit, Unity desktop, kernel `4.4.0-24-generic`, running on an Acer Aspire E5-773G notebook.

Running `lshw` (version `02.17-1.1ubuntu3.1`) from a terminal emulator without `sudo` as normal user causes it to crash:

    $ 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)

This seems to be reproducible, even after a clean reboot etc.

Please comment if you need further information or logs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lshw 02.17-1.1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 20 13:59:16 2016
InstallationDate: Installed on 2016-05-04 (46 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lshw
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Byte Commander (bytecommander) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lshw (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.