Bug 1038400

Summary: [abrt] gsmartcontrol-0.8.7-3.fc20: std::__throw_out_of_range: Process /usr/sbin/gsmartcontrol was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: lionghostshop
Component: gsmartcontrolAssignee: Eric Smith <spacewar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bognarg, Larry, noesgaard, office, spacewar, starparodia, Wilhelm.Buchmueller
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/32f5b2a128882ff067268c4991bc7a6bd3da41a2
Whiteboard: abrt_hash:d2f95ddec714cbf16d50dd14fa7df95a49efbb3c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:24:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description lionghostshop 2013-12-05 04:14:00 UTC
Description of problem:
gsmartcontrol crash when usb haddrive is connected.

It always crash when I connect a usb harddrive to my laptop

Version-Release number of selected component:
gsmartcontrol-0.8.7-3.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.12.0-2.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 std::__throw_out_of_range at ../../../../../libstdc++-v3/src/c++11/functexcept.cc:80
 #7 _M_check at /usr/include/c++/4.8.1/bits/basic_string.h:324
 #8 substr at /usr/include/c++/4.8.1/bits/basic_string.h:2208
 #9 SmartctlParser::parse_full at smartctl_parser.cpp:215
 #10 StorageDevice::parse_basic_data at storage_device.cpp:266
 #11 StorageDevice::fetch_basic_data_and_parse at storage_device.cpp:186
 #13 (anonymous namespace)::detect_drives_linux_proc_partitions at storage_detector_linux.cpp:437
 #14 detect_drives_linux at storage_detector_linux.cpp:820
 #15 StorageDetector::detect at storage_detector.cpp:40
 #16 StorageDetector::detect_and_fetch_basic_data at storage_detector.cpp:150

Potential duplicate: bug 1036863

Comment 1 lionghostshop 2013-12-05 04:14:07 UTC
Created attachment 832980 [details]
File: backtrace

Comment 2 lionghostshop 2013-12-05 04:14:10 UTC
Created attachment 832981 [details]
File: cgroup

Comment 3 lionghostshop 2013-12-05 04:14:13 UTC
Created attachment 832982 [details]
File: core_backtrace

Comment 4 lionghostshop 2013-12-05 04:14:16 UTC
Created attachment 832983 [details]
File: dso_list

Comment 5 lionghostshop 2013-12-05 04:14:19 UTC
Created attachment 832984 [details]
File: environ

Comment 6 lionghostshop 2013-12-05 04:14:23 UTC
Created attachment 832985 [details]
File: limits

Comment 7 lionghostshop 2013-12-05 04:14:27 UTC
Created attachment 832986 [details]
File: maps

Comment 8 lionghostshop 2013-12-05 04:14:31 UTC
Created attachment 832987 [details]
File: open_fds

Comment 9 lionghostshop 2013-12-05 04:14:34 UTC
Created attachment 832988 [details]
File: proc_pid_status

Comment 10 lionghostshop 2013-12-05 04:14:37 UTC
Created attachment 832989 [details]
File: var_log_messages

Comment 11 Gábor 2014-02-03 07:02:01 UTC
Another user experienced a similar problem:

just tried to start gsmartcontrol. always reproducible

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.12.8-300.fc20.x86_64
package:        gsmartcontrol-0.8.7-3.fc20
reason:         gsmartcontrol killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 12 victor_safronov 2014-03-06 09:46:13 UTC
Another user experienced a similar problem:

GSmartControl does not start, smartctl from command line works fine.
Installed disks:
OCZ Vector 128 GB,
Samsung Spinpoint SP2514N via AgeStar issi IDE/SATA convertor.
Main board: GA-B75M-D3V, SATA mode: AHCI.


reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.13.5-200.fc20.x86_64
package:        gsmartcontrol-0.8.7-3.fc20
reason:         gsmartcontrol killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Peter Andreasen 2014-03-28 10:27:55 UTC
Another user experienced a similar problem:

I tried to run gsmartcontrol to check my harddisk. I forgot that it is a RAID1 so it has no SMART information. gsmartcontrol crashed without any message. If I run it from the command line, I get this output:

sudo gsmartcontrol /dev/sda1
<warn>  [hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
<warn>  [app] execute_smartctl(): Error while executing smartctl binary.
<warn>  [app] StorageDevice::execute_device_smartctl(): Error while executing smartctl binary.
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Vendor"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Product"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Revision"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical block size"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Device type"
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.13.6-200.fc20.x86_64
package:        gsmartcontrol-0.8.7-3.fc20
reason:         gsmartcontrol killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 14 Gábor 2014-10-03 05:09:19 UTC
Another user experienced a similar problem:

just started gsmartcontrol

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.16.3-200.fc20.x86_64
package:        gsmartcontrol-0.8.7-3.fc20
reason:         gsmartcontrol killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 15 Wilhelm.Buchmueller 2014-11-22 00:27:29 UTC
Another user experienced a similar problem:

calling with automatic device list scan with usb device 

Bus 005 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem

plugged in.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        gsmartcontrol
crash_function: std::__throw_out_of_range
executable:     /usr/sbin/gsmartcontrol
kernel:         3.17.3-200.fc20.i686+PAE
package:        gsmartcontrol-0.8.7-3.fc20
reason:         gsmartcontrol killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 16 Fedora End Of Life 2015-05-29 09:55:22 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2015-06-29 13:24:09 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.