[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

This bug was fixed in the package lshw - 02.17-1.1ubuntu3.3

---
lshw (02.17-1.1ubuntu3.3) xenial; urgency=medium

  * Fix situation where lshw segfaults, when there is an external
USB 3.0 drive connected to the system. (LP: #1471983)
- d/p/fix-701-SCSI-inquiry-fails-on-IA64.patch:
  use uint8_t instead of char where unsigned is needed.

 -- Dan Streetman   Thu, 19 Oct 2017
10:19:02 -0400

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

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

This bug was fixed in the package lshw - 02.16-2ubuntu1.4

---
lshw (02.16-2ubuntu1.4) trusty; urgency=medium

  * Fix situation where lshw segfaults, when there is an external
USB 3.0 drive connected to the system. (LP: #1471983)
- d/p/presumably-fix-653.patch: use local var
- d/p/fix-701-SCSI-inquiry-fails-on-IA64.patch:
  use uint8_t instead of char where unsigned is needed.

 -- Dan Streetman   Thu, 19 Oct 2017
10:19:02 -0400

** Changed in: lshw (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

## VERIFICATION TRUSTY ##

The lshw binary package found in trusty-proposed (Version:
02.16-2ubuntu1.4) works well and now properly report informations of a
known problematic USB 3.0 drive[1] (reported by a user).

I also confirmed it was segfaulting with "02.16-2ubuntu1.3" when a USB
3.0 drive was connected and no longer segfault with proposed pkg
"02.16-2ubuntu1.4"


[1] - Patriot Supersonic Rage (32GB) USB 3.0 flash drive.

- Eric

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

## VERIFICATION XENIAL ##

The lshw binary package found in xenial-proposed (Version: 02.17-1.1ubuntu3.3) 
works well and properly report informations of a known problematic USB 3.0 
drive[1] (reported by a user):
Patriot Supersonic Rage (32GB) USB 3.0 flash drive.

and so far also work well with other USB devices that I have tested such
as a Logitech webcam[2].

[1 - lshw output - Patriot USB 3.0
...
*-usb
   description: Mass storage device
   product: Patriot Memory
   physical id: 1
   bus info: usb@2:1
   logical name: scsi3
   version: 1.00
   serial: 0701788EAE02AE03
   capabilities: usb-3.10 scsi emulated scsi-host
   configuration: driver=usb-storage maxpower=504mA 
speed=5000Mbit/s
 *-disk
  description: SCSI Disk
  product: Patriot Memory
  physical id: 0.0.0
  bus info: scsi@3:0.0.0
  logical name: /dev/sda
  version: PMAP
  size: 29GiB (31GB)
  capabilities: removable
  configuration: ansiversion=6 logicalsectorsize=512 
sectorsize=512
...

[2] - Logitech webcam
..
 *-usb:0
   description: Video
   product: HD Pro Webcam C920
   vendor: Logitech, Inc.
   physical id: 4
   bus info: usb@1:4
   version: 0.11
   serial: D23B587F
   capabilities: usb-2.00
   configuration: driver=snd-usb-audio maxpower=500mA 
speed=480Mbit/s
..

- Eric


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Tags added: sts-sru-needed

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Andy Whitcroft]

Hello Ben, or anyone else affected,

Accepted lshw into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lshw/02.16-2ubuntu1.4
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 on 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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 Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

# The package is now found in xenial-proposed but the LP bug haven't been 
updated. #
# I'm doing it manually on behalf of SRU verification team #

Hello Ben Dover, or anyone else affected,

Accepted python-neutronclient into xenial-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/lshw/02.17-1.1ubuntu3.3 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 on 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

- Eric


** Tags added: verification-needed verification-needed-xenial

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

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

Sponsored for both trusty and xenial


** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and system will store a 'lshw' crash file 
under /var/crash.
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream
  to fix this problem, and the fix is part of 'lshw' Ubuntu package since
  2015, Wily. I don't know why Trusty never been SRU'd at the same time,
  but it's never too late to fix it now that we have users facing this
  problem in Trusty/14.04 (LTS)
  
-  * It's been ~3 years now since the patch has been first introduced in
+  * It's been ~3 years now since the patch has been first introduced in
  lshw upstream, and since then no known regression or else has been
  reporter against this specific commit.
  
-  * Debian has the fix.
+  * Debian has the fix.
  
   * The code changed by this patch handles querying the serial number, so
  regression in this area may cause incorrect or missing serial number(s)
  to be reported by lshw.
  
  [Other Info]
  
   * Upstream commit :
   https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
+ https://ezix.org/src/pkg/lshw/commit/7b57987bb21d8c178c9beba1f5a574eb0af18e54
  
  * Bug:
  http://www.ezix.org/project/ticket/653
+ http://www.ezix.org/project/ticket/701
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and system will store a 'lshw' crash file 
under /var/crash.
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream
  to fix this problem, and the fix 

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Dan Streetman]

additional upstream commit 7b57987bb21d8c178c9beba1f5a574eb0af18e54
requested by apw, as the type of the len var should be uint8_t not char;
the serial number string len may be > 127

that commit is needed in trusty and xenial.  debdiffs updated.

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Dan Streetman]

** Patch added: "lp1471983-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4976127/+files/lp1471983-xenial.debdiff

** Patch removed: "lp1471983-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4966920/+files/lp1471983-trusty.debdiff

** Changed in: lshw (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Dan Streetman]

** Patch added: "lp1471983-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4976126/+files/lp1471983-trusty.debdiff

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Changed in: lshw (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: lshw (Ubuntu Xenial)
   Status: Fix Released => In Progress

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

Sponsored, the package is now waiting in the Trusty upload queue for the
SRU verification team approval before it starts building in trusty-
proposed.

Thanks Dan !

** Tags added: sts-sponsor-done-slashd

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and system will store a 'lshw' crash file 
under /var/crash.
  
  [Regression Potential]
  
-  * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
-    I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
-  * The code changed by this patch handles querying the serial number, so 
regression in this area may cause incorrect or missing serial number(s) to be 
reported by lshw.
+  * Risk is low, the upstream commit has been specifically made upstream
+ to fix this problem, and the fix is part of 'lshw' Ubuntu package since
+ 2015, Wily. I don't know why Trusty never been SRU'd at the same time,
+ but it's never too late to fix it now that we have users facing this
+ problem in Trusty/14.04 (LTS)
+ 
+  * It's been ~3 years now since the patch has been first introduced in
+ lshw upstream, and since then no known regression or else has been
+ reporter against this specific commit.
+ 
+  * Debian has the fix.
+ 
+  * The code changed by this patch handles querying the serial number, so
+ regression in this area may cause incorrect or missing serial number(s)
+ to be reported by lshw.
  
  [Other Info]
  
   * Upstream commit :
   https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
  
  * Bug:
  http://www.ezix.org/project/ticket/653
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
     I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
-  * The code changed by this patch handles querying the serial number, so 
regression in this area may cause incorrect or missing serial number(s) to be 
reported by lshw.
- 
+  * The code changed by this patch handles querying the serial number, so 
regression in this area may cause incorrect or missing serial number(s) to be 
reported by lshw.
  
  [Other Info]
  
   * Upstream commit :
-    
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
- or
-  https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
- 
+  https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
  
  * Bug:
  http://www.ezix.org/project/ticket/653
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
-  * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
+  * Client HW inventory won't happen and system will store a 'lshw' crash file 
under /var/crash.
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu 

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Dan Streetman]

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [2] - landscape-client
  landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
     I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
+  * The code changed by this patch handles querying the serial number, so 
regression in this area may cause incorrect or missing serial number(s) to be 
reported by lshw.
+ 
  
  [Other Info]
  
   * Upstream commit :
     
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
+ or
+  https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
+ 
  
  * Bug:
  http://www.ezix.org/project/ticket/653
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

** Patch added: "lp1471983-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966920/+files/lp1471983-trusty.debdiff

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Dan Streetman]

eric graciously offered for me to take this bug for more SRU experience,
thanks eric!

** Changed in: lshw (Ubuntu Trusty)
 Assignee: Eric Desrochers (slashd) => Dan Streetman (ddstreet)

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

debdiff V2 - lshw for Trusty/14.04 LTS

** Patch added: "lshw-trusty-lp1471983_V2.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966834/+files/lshw-trusty-lp1471983_V2.debdiff

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
- * In the Landscape context, 'lshw' is use for Landscape clients HW inventory 
... if an USB External Drive[1] is connected on a Trusty Landscape client, lshw 
will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
+ * In the Landscape context, 'lshw' is use for Landscape clients[2] HW 
inventory ... if an USB External Drive[1] is connected on a Trusty Landscape 
client, lshw will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
+ 
+ [2] - landscape-client
+ landscape/manager/hardwareinfo.py:command = "/usr/bin/lshw"
  
  [Test Case]
  
  Scenario #1:
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
- 
  
  Scenario #2:
   * Install Ubuntu Trusty/14.04 LTS
   * Install landscape-client
   * Register the computer to the Landscape (Dedicated server or hosted)
   * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
  
  [Regression Potential]
  
   * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
     I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
  
  [Other Info]
  
   * Upstream commit :
     
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
  
  * Bug:
  http://www.ezix.org/project/ticket/653
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Tags added: sts

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

debdiff - lshw for Trusty/14.04 LTS

** Patch added: "lshw-trusty-lp1471983.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966702/+files/lshw-trusty-lp1471983.debdiff

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Description changed:

  [Impact]
  
  Scenario #1:
- * When there is an external USB External Drive[1] is connected to system, 
lshw command segfaults.
+ * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
  * In the Landscape context, 'lshw' is used for client HW inventory ... if an 
USB External Drive[1] is connected on a Trusty Landscape client, lshw will 
segfault, thus Landcape inventory for this computer won't be reported/updated.
  
- [1] - In this case : 
+ [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [Test Case]
  
-  * Install Ubuntu Trusty/14.04 LTS
-  * Install lshw
-- sudo apt-get install lshw -y
-  * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
-  * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
+  * Install Ubuntu Trusty/14.04 LTS
+  * Install lshw
+    - sudo apt-get install lshw -y
+  * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
+  * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
  
-  * Install Ubuntu Trusty/14.04 LTS
-  * Install landscape-client
-  * Register the computer to the Landscape (Dedicated server or hosted)
-  * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
+  * Install Ubuntu Trusty/14.04 LTS
+  * Install landscape-client
+  * Register the computer to the Landscape (Dedicated server or hosted)
+  * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
  
+ [Regression Potential]
  
- [Regression Potential] 
- 
-  * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
-I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
+  * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
+    I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
  
  [Other Info]
-  
-  * Upstream commit :
-
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
+ 
+  * Upstream commit :
+    
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
  
  * Bug:
  http://www.ezix.org/project/ticket/653
  
  [Original Description]
  The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
  As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
  When I unplug the HDD enclosure, lshw then runs fine as root.
  This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
  I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
  terminate called after throwing an instance of 'std::length_error'
    what(): basic_string::_S_create
  "
  
  I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
  (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

** Description changed:

  [Impact]
  
  Scenario #1:
  * When there is an external USB External Drive[1] connected to the system, 
'lshw' command segfaults.
  
  Scenario #2:
- * In the Landscape context, 'lshw' is used for client HW inventory ... if an 
USB External Drive[1] is connected on a Trusty Landscape client, lshw will 
segfault, thus Landcape inventory for this computer won't be reported/updated.
+ * In the Landscape context, 'lshw' is use for Landscape clients HW inventory 
... if an USB External Drive[1] is connected on a Trusty Landscape client, lshw 
will segfault, thus Landcape inventory for this computer won't be 
reported/updated.
  
  [1] - In this case :
  Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
  
  [Test Case]
  
   * Install Ubuntu Trusty/14.04 LTS
   * Install lshw
     - sudo apt-get install lshw -y
   * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
   * Execute 'lshw' or any other tools that uses 

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Description changed:

- The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0' 
- As seen here http://www.amazon.co.uk/dp/B00BH83LYG/ 
+ [Impact]
+ 
+ Scenario #1:
+ * When there is an external USB External Drive[1] is connected to system, 
lshw command segfaults.
+ 
+ Scenario #2:
+ * In the Landscape context, 'lshw' is used for client HW inventory ... if an 
USB External Drive[1] is connected on a Trusty Landscape client, lshw will 
segfault, thus Landcape inventory for this computer won't be reported/updated.
+ 
+ [1] - In this case : 
+ Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
+ 
+ [Test Case]
+ 
+  * Install Ubuntu Trusty/14.04 LTS
+  * Install lshw
+- sudo apt-get install lshw -y
+  * Connect the USB 3.0 external drive to the system from where 'lshw' will be 
executed.
+  * Execute 'lshw' or any other tools that uses 'lshw' behind the scene. 
(Example : Landscape computer inventory, ...)
+ 
+  * Install Ubuntu Trusty/14.04 LTS
+  * Install landscape-client
+  * Register the computer to the Landscape (Dedicated server or hosted)
+  * Client HW inventory won't happen and /var/crash will stores lshw.crash 
file under /var/crash
+ 
+ 
+ [Regression Potential] 
+ 
+  * Risk is low, the upstream commit has been specifically made upstream to 
fix this problem, and the fix is part of 'lshw' Ubuntu package since 2015, Wily.
+I don't know why Trusty never been SRU'd at the same time, but it's never 
too late to fix it now that we have user facing this problem in Trusty/14.04 
(LTS)
+ 
+ [Other Info]
+  
+  * Upstream commit :
+
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
+ 
+ * Bug:
+ http://www.ezix.org/project/ticket/653
+ 
+ [Original Description]
+ The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
+ As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
  
  When the enclosure is plugged in, the lshw command runs fine as a plain
  user, but when run as root with either 'sudo su', 'sudo -i' or just
  'sudo' (I tried all to be sure), lshw starts the normal process of
  scanning through the stuff it scans, but instead of outputting any
  information, it seg-faults with the message "Segmentation Fault".
  
- When I unplug the HDD enclosure, lshw then runs fine as root. 
- This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04). 
+ When I unplug the HDD enclosure, lshw then runs fine as root.
+ This problem occurs both with USB 3.0 and USB 2.0, and has been tested on an 
AMD 64-bit machine running Xubuntu 14.04 (upgraded from 12.04).
  
- I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different; 
+ I also tested on an older Intel 32-bit machine running Xubuntu 14.04 and got 
the same problem, except this time the message was different;
  "
- terminate called after throwing an instance of 'std::length_error' 
-   what(): basic_string::_S_create
+ terminate called after throwing an instance of 'std::length_error'
+   what(): basic_string::_S_create
  "
  
- I have pasted an extract from dmesg (from the AMD 64-bit machine) here: 
+ I have pasted an extract from dmesg (from the AMD 64-bit machine) here:
  http://pastebin.com/mTfJV04k
  of which mentions lshw with some information about the USB device.
  
- (this is my first ever bug report, so apologies in advanced if I made any 
mistakes) 
+ (this is my first ever bug report, so apologies in advanced if I made any 
mistakes)
  (Package version lshw 02.16-2ubuntu1.2)

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Eric Desrochers]

** Also affects: lshw (Ubuntu Artful)
   Importance: Medium
   Status: Fix Released

** Also affects: lshw (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: lshw (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: lshw (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

** Changed in: lshw (Ubuntu Trusty)
   Status: Confirmed => In Progress

** Changed in: lshw (Ubuntu Trusty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Michael Terry]

I've uploaded the wily patch to wily.  Thanks for it!

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/lshw

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

This bug was fixed in the package lshw - 02.17-1.1ubuntu3

---
lshw (02.17-1.1ubuntu3) wily; urgency=medium

  * [d048d30] Fix lshw crash issue on system with some USB-3 sticks
(LP: #1471983)

 -- Chen-Han Hsiao (Stanley)   Sun, 11 Oct
2015 21:35:54 +0800

** Changed in: lshw (Ubuntu Wily)
   Status: Confirmed => Fix Released

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

** Branch linked: lp:~swem/ubuntu/wily/lshw/lp1471983

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

** Branch linked: lp:~swem/ubuntu/vivid/lshw/lp1471983

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Brian Murray]

I don't see very many crash reports regarding lshw on the Error Tracker
so I'm setting the importance of this to Medium.

** Changed in: lshw (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: lshw (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: lshw (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Marc Deslauriers]

Hi, thanks for the debdiff!

Two comments:

1- Could you please list both patches in the changelog along with a small 
description of what they accomplish?
2- While the "use-a-different-approach-for-scanning-SCSI-generic-d.patch" 
change seems to be included in 2.17 currently in vivid and wily, the 
"presumably-fix-653.patch" change is not. Could you please prepare debdiffs for 
Vivid and Wily?

Thanks!

** Also affects: lshw (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lshw (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: lshw (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: lshw (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: lshw (Ubuntu Vivid)
   Status: New => Confirmed

** Changed in: lshw (Ubuntu Wily)
   Status: New => Confirmed

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Chen-Han Hsiao (Stanley)]

I also encounter this issue in Ubuntu OEM project.

This bug is fixed in
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a

The issue in upstream: [lshw segfaults, with some 16GB USB-3 sticks from
Patriot] http://www.ezix.org/project/ticket/653

I've made a patch to fix it.

** Bug watch added: Ezix Trac #653
   http://ezix.org/project/ticket/653

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

[Launchpad Bug Tracker]

** Branch linked: lp:~swem/ubuntu/trusty/lshw/lp1471983

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

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs