Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1158384

Summary: [abrt] kde-workspace: KScreen::Mode::size(): systemsettings killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Filak <jfilak>
Component: libkscreenAssignee: Jan Grulich <jgrulich>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jberan, jgrulich, than
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f6c2e83d28eaa98d167413248de3bd1aaeea9f51
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-09 12:39:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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: machineid
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jakub Filak 2014-10-29 09:36:30 UTC 
Description of problem:
I connected another monitor while 'Display and Monitor' had focus.

Version-Release number of selected component:
kde-workspace-4.10.5-18.el7

Additional info:
reporter:       libreport-2.1.11.13.el7.7.g0b86
backtrace_rating: 4
cmdline:        /usr/bin/systemsettings -caption 'System Settings' --icon preferences-system
crash_function: KScreen::Mode::size
executable:     /usr/bin/systemsettings
kernel:         3.10.0-190.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            18601

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 KScreen::Mode::size at /usr/src/debug/libkscreen-1.0.1/src/mode.cpp:83
 #1 KScreen::Config::canBeApplied at /usr/src/debug/libkscreen-1.0.1/src/config.cpp:110
 #2 KCMKScreen::outputChanged at /usr/src/debug/kscreen-1.0.1/kcm/src/kcm_kscreen.cpp:302
 #3 QMetaObject::activate at kernel/qobject.cpp:3547
 #5 QDeclarativeVMEMetaObject::metaCall at qml/qdeclarativevmemetaobject.cpp:639
 #6 QDeclarativeObjectMethodScriptClass::callMethod at qml/qdeclarativeobjectscriptclass.cpp:988
 #7 QDeclarativeObjectMethodScriptClass::callPrecise at qml/qdeclarativeobjectscriptclass.cpp:948
 #8 QDeclarativeObjectMethodScriptClass::call at qml/qdeclarativeobjectscriptclass.cpp:917
 #9 QScript::DeclarativeObjectDelegate::call at bridge/qscriptdeclarativeobject.cpp:154
 #10 QTJSC::NativeFuncWrapper::operator() at ../3rdparty/javascriptcore/JavaScriptCore/runtime/CallData.cpp:46

Potential duplicate: bug 1082677
Comment 1 Jakub Filak 2014-10-29 09:36:32 UTC 
Created attachment 951687 [details]
File: backtrace
Comment 2 Jakub Filak 2014-10-29 09:36:33 UTC 
Created attachment 951688 [details]
File: cgroup
Comment 3 Jakub Filak 2014-10-29 09:36:35 UTC 
Created attachment 951689 [details]
File: core_backtrace
Comment 4 Jakub Filak 2014-10-29 09:36:36 UTC 
Created attachment 951690 [details]
File: dso_list
Comment 5 Jakub Filak 2014-10-29 09:36:38 UTC 
Created attachment 951691 [details]
File: environ
Comment 6 Jakub Filak 2014-10-29 09:36:39 UTC 
Created attachment 951692 [details]
File: exploitable
Comment 7 Jakub Filak 2014-10-29 09:36:40 UTC 
Created attachment 951693 [details]
File: limits
Comment 8 Jakub Filak 2014-10-29 09:36:41 UTC 
Created attachment 951694 [details]
File: machineid
Comment 9 Jakub Filak 2014-10-29 09:36:43 UTC 
Created attachment 951695 [details]
File: maps
Comment 10 Jakub Filak 2014-10-29 09:36:44 UTC 
Created attachment 951696 [details]
File: open_fds
Comment 11 Jakub Filak 2014-10-29 09:36:45 UTC 
Created attachment 951697 [details]
File: proc_pid_status
Comment 12 Jakub Filak 2014-10-29 09:36:46 UTC 
Created attachment 951698 [details]
File: var_log_messages
Comment 14 Than Ngo 2014-10-29 10:52:23 UTC 
it looks like the crash is in libkscreen, reassign to correct component
Comment 18 Jan Grulich 2017-05-09 12:39:24 UTC 

*** This bug has been marked as a duplicate of bug 1365318 ***