Bug 1373894

Summary: [abrt] plasma-systemsettings: std::__atomic_base<int>::load(): systemsettings5 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: gwdredhatnom <gwd163nom>
Component: plasma-systemsettingsAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: courtney.hicks1, jgrulich, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8eb6e7f2714a381f7ef63856b830e3c818d0ff08
Whiteboard: abrt_hash:c97ead6eb15cca6df2c4a0df6fd4e043a04f62c9;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:08:07 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: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description gwdredhatnom 2016-09-07 11:35:56 UTC
Description of problem:
two os system in this machine. 
1. windows10
2. fedora24
...... corrupt again

Version-Release number of selected component:
plasma-systemsettings-5.6.4-1.fc24

Additional info:
reporter:       libreport-2.7.1
backtrace_rating: 4
cmdline:        /usr/bin/systemsettings5
crash_function: std::__atomic_base<int>::load
executable:     /usr/bin/systemsettings5
global_pid:     2954
kernel:         4.5.5-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 std::__atomic_base<int>::load at /usr/include/c++/6.0.0/bits/atomic_base.h:396
 #1 QAtomicOps<int>::load<int> at ../../src/corelib/arch/qatomic_cxx11.h:96
 #2 QBasicAtomicInteger<int>::load at ../../src/corelib/thread/qbasicatomic.h:116
 #3 QtPrivate::RefCount::deref at ../../src/corelib/tools/qrefcount.h:60
 #4 QString::~QString at ../../src/corelib/tools/qstring.h:1065
 #5 QHashData::free_helper at tools/qhash.cpp:538
 #6 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::freeData at ../../src/corelib/tools/qhash.h:555
 #7 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::~QHash at ../../src/corelib/tools/qhash.h:246
 #8 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::operator=(QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>&&) at ../../src/corelib/tools/qhash.h:252
 #9 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::clear at ../../src/corelib/tools/qhash.h:561

Comment 1 gwdredhatnom 2016-09-07 11:36:04 UTC
Created attachment 1198663 [details]
File: backtrace

Comment 2 gwdredhatnom 2016-09-07 11:36:06 UTC
Created attachment 1198664 [details]
File: cgroup

Comment 3 gwdredhatnom 2016-09-07 11:36:08 UTC
Created attachment 1198665 [details]
File: core_backtrace

Comment 4 gwdredhatnom 2016-09-07 11:36:10 UTC
Created attachment 1198666 [details]
File: dso_list

Comment 5 gwdredhatnom 2016-09-07 11:36:12 UTC
Created attachment 1198667 [details]
File: environ

Comment 6 gwdredhatnom 2016-09-07 11:36:14 UTC
Created attachment 1198668 [details]
File: exploitable

Comment 7 gwdredhatnom 2016-09-07 11:36:17 UTC
Created attachment 1198669 [details]
File: limits

Comment 8 gwdredhatnom 2016-09-07 11:36:19 UTC
Created attachment 1198670 [details]
File: maps

Comment 9 gwdredhatnom 2016-09-07 11:36:21 UTC
Created attachment 1198671 [details]
File: mountinfo

Comment 10 gwdredhatnom 2016-09-07 11:36:23 UTC
Created attachment 1198672 [details]
File: namespaces

Comment 11 gwdredhatnom 2016-09-07 11:36:26 UTC
Created attachment 1198673 [details]
File: open_fds

Comment 12 gwdredhatnom 2016-09-07 11:36:28 UTC
Created attachment 1198674 [details]
File: proc_pid_status

Comment 13 gwdredhatnom 2016-09-07 11:36:33 UTC
Created attachment 1198675 [details]
File: var_log_messages

Comment 14 Courtney 2016-10-16 03:24:44 UTC
*** Bug 1385299 has been marked as a duplicate of this bug. ***

Comment 15 Fedora End Of Life 2017-07-25 22:52:56 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '24'.

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 24 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 16 Fedora End Of Life 2017-08-08 17:08:07 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.