Description of problem: I restarted my system after having it connected to the docking station. After logging on the system crashed. Version-Release number of selected component: libkscreen-qt5-5.8.4-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/kf5/kscreen_backend_launcher crash_function: XRandRScreen::toKScreenScreen executable: /usr/libexec/kf5/kscreen_backend_launcher global_pid: 4149 kernel: 4.8.14-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 XRandRScreen::toKScreenScreen at /usr/src/debug/libkscreen-5.8.4/backends/xrandr/xrandrscreen.cpp:67 #1 XRandRConfig::toKScreenConfig at /usr/src/debug/libkscreen-5.8.4/backends/xrandr/xrandrconfig.cpp:117 #2 XRandR::config at /usr/src/debug/libkscreen-5.8.4/backends/xrandr/xrandr.cpp:205 #3 XRandR::<lambda()>::operator() at /usr/src/debug/libkscreen-5.8.4/backends/xrandr/xrandr.cpp:120 #4 QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, XRandR::XRandR()::<lambda()> >::call at /usr/include/qt5/QtCore/qobjectdefs_impl.h:501 #5 QtPrivate::Functor<XRandR::XRandR()::<lambda()>, 0>::call<QtPrivate::List<>, void> at /usr/include/qt5/QtCore/qobjectdefs_impl.h:558 #6 QtPrivate::QFunctorSlotObject<XRandR::XRandR()::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) at /usr/include/qt5/QtCore/qobject_impl.h:198 #7 QtPrivate::QSlotObjectBase::call at ../../src/corelib/kernel/qobject_impl.h:101 #8 QMetaObject::activate at kernel/qobject.cpp:3723 #10 QTimer::timeout at .moc/moc_qtimer.cpp:198 Potential duplicate: bug 1303657
Created attachment 1234316 [details] File: backtrace
Created attachment 1234317 [details] File: cgroup
Created attachment 1234318 [details] File: core_backtrace
Created attachment 1234319 [details] File: dso_list
Created attachment 1234320 [details] File: environ
Created attachment 1234321 [details] File: exploitable
Created attachment 1234322 [details] File: limits
Created attachment 1234323 [details] File: maps
Created attachment 1234324 [details] File: mountinfo
Created attachment 1234325 [details] File: namespaces
Created attachment 1234326 [details] File: open_fds
Created attachment 1234327 [details] File: proc_pid_status
Created attachment 1234328 [details] File: var_log_messages
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.
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.