** 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
