lshw crashes on the 16.04 release

Bug #1593233 reported by benjamin button
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lshw (Ubuntu)
Fix Released
High
Unassigned

Bug Description

After the latest upgrade of lshw it stopped working. Exits with following crash output

terminate called after throwing an instance of 'std::bad_alloc'
  what(): std::bad_alloc
Aborted (core dumped)

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
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun 16 16:19:46 2016
InstallationDate: Installed on 2016-06-05 (11 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lshw
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
benjamin button (canavaroski90) wrote :
Revision history for this message
Paul White (paulw2u) wrote :

As I can see this bug on an Ubuntu installation I'm confirming the bug and removing "Xubuntu" from the bug title as all flavours are probably affected.

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
Paul White (paulw2u)
summary: - lshw crashes on Xubuntu 16.04
+ lshw crashes on the 16.04 release
Revision history for this message
Byte Commander (bytecommander) wrote :

Just reported the same bug, before I noticed that it's a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1594344

Changed in lshw (Ubuntu):
importance: Undecided → High
no longer affects: lshw (Debian)
Revision history for this message
benjamin button (canavaroski90) wrote :

I haven't seen that happening again for a long time. I presume that there is a fix has been released for that and can be marked as won't fix. Who is responsible for these kinds of things? Should I mark it as won't fix?

Revision history for this message
Paul White (paulw2u) wrote :

See this extract from the change log:

lshw (02.18-0.1) unstable; urgency=medium

  * Non-maintainer upload with permission of the maintainer.
  * New upstream release. Closes: #823639, #756921, #746616, #758550,
    #767023.
    - Refresh patches for unfortunate new upstream tarball layout.
    - debian/patches/fat-inspection.patch, debian/patches/smbios-noscan.patch:
      drop, fixed upstream.
    - Drop debian/patches/sparc.patch: no longer applies cleanly, and is
      incorrect (double header inclusion).
  * debian/patches/Avoid-crash-in-scan_dmi_sysfs-when-running-as-non-ro.patch:
    patch taken from Ubuntu to fix an upstream regression when running as
    non-root; thanks to dann frazier <email address hidden>
  * debian/patches/fix-width-handling.patch: Fix regression in detecting
    platform width.

 -- Steve Langasek <email address hidden> Mon, 15 Aug 2016 13:42:04 -0700

It looks like the issue was fixed without any reference to this bug report just a couple of months after the bug report was created.

Benjamin, I'll let you mark as "Fix released" if you're happy to close your bug report.

Revision history for this message
benjamin button (canavaroski90) wrote :

Yep, thanks for that. Closing it right now.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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