| 2015-07-06 21:10:16 |
Ben Dover |
bug |
|
|
added bug |
| 2015-09-03 07:44:15 |
Launchpad Janitor |
branch linked |
|
lp:~swem/ubuntu/trusty/lshw/lp1471983 |
|
| 2015-09-03 07:56:21 |
Chen-Han Hsiao (Stanley) |
bug watch added |
|
http://ezix.org/project/ticket/653 |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
bug task added |
|
lshw (Ubuntu Trusty) |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
nominated for series |
|
Ubuntu Wily |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
bug task added |
|
lshw (Ubuntu Wily) |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-09-15 12:51:36 |
Marc Deslauriers |
bug task added |
|
lshw (Ubuntu Vivid) |
|
| 2015-09-15 12:51:43 |
Marc Deslauriers |
lshw (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2015-09-15 12:51:45 |
Marc Deslauriers |
lshw (Ubuntu Vivid): status |
New |
Confirmed |
|
| 2015-09-15 12:51:47 |
Marc Deslauriers |
lshw (Ubuntu Wily): status |
New |
Confirmed |
|
| 2015-10-05 17:41:53 |
Brian Murray |
lshw (Ubuntu Wily): importance |
Undecided |
Medium |
|
| 2015-10-05 17:41:55 |
Brian Murray |
lshw (Ubuntu Vivid): importance |
Undecided |
Medium |
|
| 2015-10-05 17:41:57 |
Brian Murray |
lshw (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2015-10-06 14:45:15 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2015-10-11 13:33:04 |
Launchpad Janitor |
branch linked |
|
lp:~swem/ubuntu/vivid/lshw/lp1471983 |
|
| 2015-10-11 13:47:22 |
Launchpad Janitor |
branch linked |
|
lp:~swem/ubuntu/wily/lshw/lp1471983 |
|
| 2015-10-14 17:35:40 |
Michael Terry |
bug |
|
|
added subscriber Michael Terry |
| 2015-10-14 18:34:18 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/wily-proposed/lshw |
|
| 2015-10-14 19:10:41 |
Launchpad Janitor |
lshw (Ubuntu Wily): status |
Confirmed |
Fix Released |
|
| 2017-10-09 15:11:49 |
Eric Desrochers |
nominated for series |
|
Ubuntu Artful |
|
| 2017-10-09 15:11:49 |
Eric Desrochers |
bug task added |
|
lshw (Ubuntu Artful) |
|
| 2017-10-09 15:11:49 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-10-09 15:11:49 |
Eric Desrochers |
bug task added |
|
lshw (Ubuntu Xenial) |
|
| 2017-10-09 15:12:00 |
Eric Desrochers |
lshw (Ubuntu Xenial): status |
New |
Fix Released |
|
| 2017-10-09 15:12:06 |
Eric Desrochers |
lshw (Ubuntu Vivid): status |
Confirmed |
Won't Fix |
|
| 2017-10-09 15:12:10 |
Eric Desrochers |
lshw (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2017-10-09 15:12:15 |
Eric Desrochers |
lshw (Ubuntu Trusty): assignee |
|
Eric Desrochers (slashd) |
|
| 2017-10-10 12:16:18 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors Team |
| 2017-10-10 13:24:22 |
Eric Desrochers |
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) |
[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).
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) |
|
| 2017-10-10 13:31:02 |
Eric Desrochers |
description |
[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).
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) |
[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.
[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).
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) |
|
| 2017-10-10 13:31:21 |
Eric Desrochers |
description |
[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.
[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).
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) |
[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.
[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).
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) |
|
| 2017-10-10 13:31:50 |
Eric Desrochers |
description |
[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.
[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).
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) |
[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.
[1] - In this case :
Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
[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) |
|
| 2017-10-10 13:55:00 |
Eric Desrochers |
attachment added |
|
lshw-trusty-lp1471983.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966702/+files/lshw-trusty-lp1471983.debdiff |
|
| 2017-10-10 14:27:38 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation usb |
fault lshw seg-fault segmentation sts usb |
|
| 2017-10-10 15:55:20 |
Eric Desrochers |
description |
[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.
[1] - In this case :
Patriot 32GB Supersonic Rage Series USB 3.0 Flash Drive
[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) |
[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)
[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) |
|
| 2017-10-10 16:24:18 |
Eric Desrochers |
attachment added |
|
lshw-trusty-lp1471983_V2.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966834/+files/lshw-trusty-lp1471983_V2.debdiff |
|
| 2017-10-10 17:41:42 |
Dan Streetman |
lshw (Ubuntu Trusty): assignee |
Eric Desrochers (slashd) |
Dan Streetman (ddstreet) |
|
| 2017-10-10 18:24:25 |
Dan Streetman |
description |
[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)
[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) |
[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) |
|
| 2017-10-10 18:26:44 |
Dan Streetman |
attachment added |
|
lp1471983-trusty.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966920/+files/lp1471983-trusty.debdiff |
|
| 2017-10-10 19:15:29 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2017-10-11 14:15:58 |
Eric Desrochers |
description |
[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) |
[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://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) |
|
| 2017-10-11 14:20:02 |
Eric Desrochers |
description |
[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://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) |
[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.
[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) |
|
| 2017-10-18 12:26:28 |
Eric Desrochers |
description |
[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.
[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) |
[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 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) |
|
| 2017-10-18 12:36:41 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation sts usb |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb |
|
| 2017-10-18 15:56:48 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2017-10-19 14:15:39 |
Eric Desrochers |
lshw (Ubuntu Xenial): assignee |
|
Dan Streetman (ddstreet) |
|
| 2017-10-19 14:15:44 |
Eric Desrochers |
lshw (Ubuntu Xenial): status |
Fix Released |
In Progress |
|
| 2017-10-19 15:19:12 |
Dan Streetman |
attachment added |
|
lp1471983-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4976126/+files/lp1471983-trusty.debdiff |
|
| 2017-10-19 15:19:31 |
Dan Streetman |
attachment added |
|
lp1471983-xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4976127/+files/lp1471983-xenial.debdiff |
|
| 2017-10-19 15:19:42 |
Dan Streetman |
attachment removed |
lp1471983-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1471983/+attachment/4966920/+files/lp1471983-trusty.debdiff |
|
|
| 2017-10-19 15:21:37 |
Dan Streetman |
lshw (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-10-19 16:14:32 |
Eric Desrochers |
description |
[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 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) |
[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 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
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) |
|
| 2017-10-19 16:14:59 |
Eric Desrochers |
description |
[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 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
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) |
[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 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 commits :
https://ezix.org/src/pkg/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a
https://ezix.org/src/pkg/lshw/commit/7b57987bb21d8c178c9beba1f5a574eb0af18e54
* Bugs:
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) |
|
| 2017-10-19 16:15:36 |
Eric Desrochers |
bug |
|
|
added subscriber SRU Verification |
| 2017-10-20 12:29:58 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb verification-needed verification-needed-xenial |
|
| 2017-10-20 12:30:08 |
Eric Desrochers |
lshw (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-10-20 14:20:52 |
Andy Whitcroft |
lshw (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2017-10-20 14:20:54 |
Andy Whitcroft |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-10-20 14:20:57 |
Andy Whitcroft |
tags |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb verification-needed verification-needed-xenial |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb verification-needed verification-needed-trusty verification-needed-xenial |
|
| 2017-10-20 15:16:46 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd usb verification-needed verification-needed-trusty verification-needed-xenial |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd sts-sru-needed usb verification-needed verification-needed-trusty verification-needed-xenial |
|
| 2017-10-23 19:11:43 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd sts-sru-needed usb verification-needed verification-needed-trusty verification-needed-xenial |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd sts-sru-needed usb verification-done-xenial verification-needed verification-needed-trusty |
|
| 2017-10-29 22:53:08 |
Eric Desrochers |
tags |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd sts-sru-needed usb verification-done-xenial verification-needed verification-needed-trusty |
fault lshw seg-fault segmentation sts sts-sponsor-done-slashd sts-sru-needed usb verification-done verification-done-trusty verification-done-xenial |
|
| 2017-10-30 16:08:07 |
Launchpad Janitor |
lshw (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-10-30 16:08:13 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-10-30 16:08:48 |
Launchpad Janitor |
lshw (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
