sts-sponsors team mailing list archive

[Launchpad Bug Tracker <1471983@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug by Eric Desrochers (slashd):

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)

** Affects: lshw (Ubuntu)
     Importance: Medium
         Status: Fix Released

** Affects: lshw (Ubuntu Trusty)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: In Progress

** Affects: lshw (Ubuntu Vivid)
     Importance: Medium
         Status: Won't Fix

** Affects: lshw (Ubuntu Wily)
     Importance: Medium
         Status: Fix Released

** Affects: lshw (Ubuntu Xenial)
     Importance: Undecided
         Status: Fix Released

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


** Tags: fault lshw seg-fault segmentation usb
-- 
USB HDD makes lshw seg-fault when run as root
https://bugs.launchpad.net/bugs/1471983
You received this bug notification because you are a member of STS Sponsors Team, which is subscribed to the bug report.