Bug 1262620

Summary: [abrt] libkscreen-qt5: XRandRConfig::applyKScreenConfig(): kscreen_backend_launcher killed by SIGSEGV
Product: [Fedora] Fedora Reporter: lub <lubka.kramarekova>
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
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a065c8fbf0737d009d2ea5b24c6cc38e1d1ededb
Whiteboard: abrt_hash:d3e2995486ac4ad948cd5ffa0702666bbd3fc537
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:52:43 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 lub 2015-09-13 15:47:11 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: XRandRConfig::applyKScreenConfig
executable:     /usr/libexec/kf5/kscreen_backend_launcher
global_pid:     1418
kernel:         4.1.5-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 XRandRConfig::applyKScreenConfig at ../../../backends/xrandr/xrandrconfig.cpp:224
 #1 XRandR::setConfig at ../../../backends/xrandr/xrandr.cpp:213
 #2 BackendDBusWrapper::setConfig at ../../../src/backendlauncher/backenddbuswrapper.cpp:89
 #3 setConfig at backendadaptor.cpp:57
 #4 BackendAdaptor::qt_static_metacall at backendadaptor.moc:116
 #5 BackendAdaptor::qt_metacall at backendadaptor.moc:158
 #6 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:978
 #7 QDBusConnectionPrivate::activateCall at qdbusintegrator.cpp:892
 #8 QDBusConnectionPrivate::activateObject at qdbusintegrator.cpp:1462
 #9 QDBusActivateObjectEvent::placeMetaCall at qdbusintegrator.cpp:1580
Comment 1 lub 2015-09-13 15:47:17 UTC 
Created attachment 1072919 [details]
File: backtrace
Comment 2 lub 2015-09-13 15:47:18 UTC 
Created attachment 1072920 [details]
File: cgroup
Comment 3 lub 2015-09-13 15:47:19 UTC 
Created attachment 1072921 [details]
File: core_backtrace
Comment 4 lub 2015-09-13 15:47:21 UTC 
Created attachment 1072922 [details]
File: dso_list
Comment 5 lub 2015-09-13 15:47:22 UTC 
Created attachment 1072923 [details]
File: environ
Comment 6 lub 2015-09-13 15:47:23 UTC 
Created attachment 1072924 [details]
File: limits
Comment 7 lub 2015-09-13 15:47:26 UTC 
Created attachment 1072925 [details]
File: maps
Comment 8 lub 2015-09-13 15:47:27 UTC 
Created attachment 1072926 [details]
File: mountinfo
Comment 9 lub 2015-09-13 15:47:28 UTC 
Created attachment 1072927 [details]
File: namespaces
Comment 10 lub 2015-09-13 15:47:29 UTC 
Created attachment 1072928 [details]
File: open_fds
Comment 11 lub 2015-09-13 15:47:30 UTC 
Created attachment 1072929 [details]
File: proc_pid_status
Comment 12 lub 2015-09-13 15:47:32 UTC 
Created attachment 1072930 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 17:52:43 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.