Bug 1261905

Summary: [abrt] libkscreen-qt5: XRandRCrtc::update(): kscreen_backend_launcher killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Norman Davidson <mail432>
Component: libkscreen-qt5Assignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: kde-sig, nfd
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c82f6a9761f1eb38767bbfd4260395fce9ecd78e
Whiteboard: abrt_hash:b0e2c0952c1cd3bdf33594f36c056ca53b55be66
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:50:58 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: 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 Norman Davidson 2015-09-10 12:13:21 UTC 
Version-Release number of selected component:
libkscreen-qt5-5.3.2-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/kf5/kscreen_backend_launcher
crash_function: XRandRCrtc::update
executable:     /usr/libexec/kf5/kscreen_backend_launcher
global_pid:     3012
kernel:         4.1.6-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 XRandRCrtc::update at ../../../backends/xrandr/xrandrcrtc.cpp:98
 #1 XRandRConfig::addNewCrtc at ../../../backends/xrandr/xrandrconfig.cpp:97
 #2 XRandRConfig::XRandRConfig at ../../../backends/xrandr/xrandrconfig.cpp:47
 #3 XRandR::XRandR at ../../../backends/xrandr/xrandr.cpp:101
 #4 qt_plugin_instance at moc_xrandr.cpp:196
 #5 QPluginLoader::instance at plugin/qpluginloader.cpp:192
 #6 BackendLoader::loadBackend at ../../../src/backendlauncher/backendloader.cpp:96
Comment 1 Norman Davidson 2015-09-10 12:13:24 UTC 
Created attachment 1072140 [details]
File: backtrace
Comment 2 Norman Davidson 2015-09-10 12:13:25 UTC 
Created attachment 1072141 [details]
File: cgroup
Comment 3 Norman Davidson 2015-09-10 12:13:26 UTC 
Created attachment 1072142 [details]
File: core_backtrace
Comment 4 Norman Davidson 2015-09-10 12:13:27 UTC 
Created attachment 1072143 [details]
File: dso_list
Comment 5 Norman Davidson 2015-09-10 12:13:28 UTC 
Created attachment 1072144 [details]
File: environ
Comment 6 Norman Davidson 2015-09-10 12:13:29 UTC 
Created attachment 1072145 [details]
File: limits
Comment 7 Norman Davidson 2015-09-10 12:13:30 UTC 
Created attachment 1072146 [details]
File: maps
Comment 8 Norman Davidson 2015-09-10 12:13:31 UTC 
Created attachment 1072147 [details]
File: mountinfo
Comment 9 Norman Davidson 2015-09-10 12:13:32 UTC 
Created attachment 1072148 [details]
File: namespaces
Comment 10 Norman Davidson 2015-09-10 12:13:33 UTC 
Created attachment 1072149 [details]
File: open_fds
Comment 11 Norman Davidson 2015-09-10 12:13:35 UTC 
Created attachment 1072150 [details]
File: proc_pid_status
Comment 12 Norman Davidson 2015-09-10 12:13:35 UTC 
Created attachment 1072151 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 17:50:58 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.