Bug 1744757 - [abrt] powertop: std::char_traits<char>::assign(): powertop killed by SIGSEGV
Summary: [abrt] powertop: std::char_traits<char>::assign(): powertop killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: powertop
Version: 31
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:813f9f3024165bedaf89df3703a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 19:45 UTC by dario
Modified: 2020-11-24 16:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:51:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.58 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: cgroup (399 bytes, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: core_backtrace (1.49 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: cpuinfo (1.50 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: dso_list (1.42 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: environ (4.73 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: exploitable (82 bytes, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: limits (1.29 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: maps (10.89 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: mountinfo (4.03 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: open_fds (1.18 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details
File: proc_pid_status (1.29 KB, text/plain)
2019-08-22 19:45 UTC, dario
no flags Details

Description dario 2019-08-22 19:45:33 UTC
Description of problem:
I run the command - `powertop2tuned -n laptop`
Command returned:
```
Running PowerTOP, please wait...
PowerTOP returned error code: -11
```

Version-Release number of selected component:
powertop-2.10-2.fc30

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        /usr/sbin/powertop --html=/tmp/powertop --time=1
crash_function: std::char_traits<char>::assign
executable:     /usr/sbin/powertop
journald_cursor: s=c8483558d58d414db8bc5e683e62ec0d;i=66b9;b=524d472b9fbd4af6ba987eb662210f9a;m=a5d06e7;t=590b995c142a7;x=3e70c0387fa2c415
kernel:         5.2.9-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 std::char_traits<char>::assign at /usr/include/c++/9/bits/char_traits.h:300
 #1 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_set_length at /usr/include/c++/9/bits/basic_string.h:217
 #2 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_replace at /usr/include/c++/9/bits/basic_string.tcc:468
 #3 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::assign at /usr/include/c++/9/bits/char_traits.h:335
 #4 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator= at /usr/include/c++/9/bits/basic_string.h:705
 #5 report_display_cpu_cstates at cpu/cpu.cpp:564
 #6 one_measurement at main.cpp:264
 #7 make_report at main.cpp:299

Comment 1 dario 2019-08-22 19:45:37 UTC
Created attachment 1607110 [details]
File: backtrace

Comment 2 dario 2019-08-22 19:45:39 UTC
Created attachment 1607111 [details]
File: cgroup

Comment 3 dario 2019-08-22 19:45:40 UTC
Created attachment 1607112 [details]
File: core_backtrace

Comment 4 dario 2019-08-22 19:45:41 UTC
Created attachment 1607113 [details]
File: cpuinfo

Comment 5 dario 2019-08-22 19:45:42 UTC
Created attachment 1607114 [details]
File: dso_list

Comment 6 dario 2019-08-22 19:45:44 UTC
Created attachment 1607115 [details]
File: environ

Comment 7 dario 2019-08-22 19:45:45 UTC
Created attachment 1607116 [details]
File: exploitable

Comment 8 dario 2019-08-22 19:45:47 UTC
Created attachment 1607117 [details]
File: limits

Comment 9 dario 2019-08-22 19:45:48 UTC
Created attachment 1607118 [details]
File: maps

Comment 10 dario 2019-08-22 19:45:50 UTC
Created attachment 1607119 [details]
File: mountinfo

Comment 11 dario 2019-08-22 19:45:51 UTC
Created attachment 1607120 [details]
File: open_fds

Comment 12 dario 2019-08-22 19:45:52 UTC
Created attachment 1607121 [details]
File: proc_pid_status

Comment 13 Ben Cotton 2020-11-03 16:52:52 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 14 Ben Cotton 2020-11-24 16:51:38 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.


Note You need to log in before you can comment on or make changes to this bug.