Bug 1313871

Summary: [abrt] libkscreen-qt5: XRandRCrtc::crtc(): kscreen_backend_launcher killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Peter Gervase <pgervase>
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: 25CC: kde-sig
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3baccd1cf8d7900cdb8e038baa20e55a8a16deae
Whiteboard: abrt_hash:d27e2f2a4cd784c0a9c6262ae173dacd86a41432;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 11:01:05 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 Peter Gervase 2016-03-02 14:00:35 UTC
Description of problem:
I powered on my system and tried to login with KDE. The screen had the little progress bar for a second or two and then went to all black. I control alt backspace and was then able to login with mate. After logging in, I saw there were a number of crashed applications:
libkscreen-qt5
then kactivitymanagerd
then plasma-workspace
then kf5-init
then plasma-workspace


Version-Release number of selected component:
libkscreen-qt5-5.5.4-2.fc24

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/libexec/kf5/kscreen_backend_launcher
crash_function: XRandRCrtc::crtc
executable:     /usr/libexec/kf5/kscreen_backend_launcher
global_pid:     15790
kernel:         4.5.0-0.rc5.git0.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 XRandRCrtc::crtc at /usr/src/debug/libkscreen-5.5.4/backends/xrandr/xrandrcrtc.cpp:39
 #1 XRandRConfig::changeOutput at /usr/src/debug/libkscreen-5.5.4/backends/xrandr/xrandrconfig.cpp:566
 #2 XRandRConfig::applyKScreenConfig at /usr/src/debug/libkscreen-5.5.4/backends/xrandr/xrandrconfig.cpp:276
 #3 XRandR::setConfig at /usr/src/debug/libkscreen-5.5.4/backends/xrandr/xrandr.cpp:213
 #4 BackendDBusWrapper::setConfig at /usr/src/debug/libkscreen-5.5.4/src/backendlauncher/backenddbuswrapper.cpp:85
 #5 BackendAdaptor::setConfig at /usr/src/debug/libkscreen-5.5.4/x86_64-redhat-linux-gnu/src/backendlauncher/backendadaptor.cpp:51
 #6 BackendAdaptor::qt_static_metacall at /usr/src/debug/libkscreen-5.5.4/x86_64-redhat-linux-gnu/src/backendlauncher/backendadaptor.moc:112
 #7 BackendAdaptor::qt_metacall at /usr/src/debug/libkscreen-5.5.4/x86_64-redhat-linux-gnu/src/backendlauncher/backendadaptor.moc:154
 #8 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:958
 #9 QDBusConnectionPrivate::activateCall at qdbusintegrator.cpp:861

Potential duplicate: bug 1227666

Comment 1 Peter Gervase 2016-03-02 14:00:38 UTC
Created attachment 1132338 [details]
File: backtrace

Comment 2 Peter Gervase 2016-03-02 14:00:39 UTC
Created attachment 1132339 [details]
File: cgroup

Comment 3 Peter Gervase 2016-03-02 14:00:40 UTC
Created attachment 1132340 [details]
File: core_backtrace

Comment 4 Peter Gervase 2016-03-02 14:00:41 UTC
Created attachment 1132341 [details]
File: dso_list

Comment 5 Peter Gervase 2016-03-02 14:00:42 UTC
Created attachment 1132342 [details]
File: environ

Comment 6 Peter Gervase 2016-03-02 14:00:42 UTC
Created attachment 1132343 [details]
File: exploitable

Comment 7 Peter Gervase 2016-03-02 14:00:43 UTC
Created attachment 1132344 [details]
File: limits

Comment 8 Peter Gervase 2016-03-02 14:00:44 UTC
Created attachment 1132345 [details]
File: maps

Comment 9 Peter Gervase 2016-03-02 14:00:45 UTC
Created attachment 1132346 [details]
File: mountinfo

Comment 10 Peter Gervase 2016-03-02 14:00:46 UTC
Created attachment 1132347 [details]
File: namespaces

Comment 11 Peter Gervase 2016-03-02 14:00:47 UTC
Created attachment 1132348 [details]
File: open_fds

Comment 12 Peter Gervase 2016-03-02 14:00:48 UTC
Created attachment 1132349 [details]
File: proc_pid_status

Comment 13 Peter Gervase 2016-03-02 14:00:49 UTC
Created attachment 1132350 [details]
File: var_log_messages

Comment 14 Jan Kurik 2016-07-26 04:29:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 15 Fedora End Of Life 2017-11-16 14:55:47 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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-12-12 11:01:05 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.