Hide Forgot
Description of problem: opened apper - searched packages in apper (to see if it had been implemented back into KDE yet) - received error that backend was not supported - got another error that kwin crashed from ABRT Version-Release number of selected component: kwin-5.5.4-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kwin_x11 crash_function: QGuiApplication::platformNativeInterface executable: /usr/bin/kwin_x11 global_pid: 959 kernel: 4.3.3-303.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 QGuiApplication::platformNativeInterface at kernel/qguiapplication.cpp:1482 #1 QX11Info::display at /usr/src/debug/qtx11extras-opensource-src-5.5.1/src/x11extras/qx11info_x11.cpp:337 #2 KCrash::defaultCrashHandler at ../../src/kcrash.cpp:452 #4 QSocketNotifier::setEnabled at kernel/qsocketnotifier.cpp:240 #5 QInotifyFileSystemWatcherEngine::~QInotifyFileSystemWatcherEngine at io/qfilesystemwatcher_inotify.cpp:247 #7 QObjectPrivate::deleteChildren at kernel/qobject.cpp:1946 #8 QObject::~QObject at kernel/qobject.cpp:1024 #9 KWin::Decoration::DecorationPalette::~DecorationPalette at /usr/src/debug/kwin-5.5.4/decorations/decorationpalette.h:35 #10 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release at /usr/include/c++/5.3.1/bits/shared_ptr_base.h:150 #11 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count at /usr/include/c++/5.3.1/bits/shared_ptr_base.h:659
Created attachment 1119882 [details] File: backtrace
Created attachment 1119883 [details] File: cgroup
Created attachment 1119884 [details] File: core_backtrace
Created attachment 1119885 [details] File: dso_list
Created attachment 1119886 [details] File: environ
Created attachment 1119887 [details] File: exploitable
Created attachment 1119888 [details] File: limits
Created attachment 1119889 [details] File: maps
Created attachment 1119890 [details] File: mountinfo
Created attachment 1119891 [details] File: namespaces
Created attachment 1119892 [details] File: open_fds
Created attachment 1119893 [details] File: proc_pid_status
Created attachment 1119894 [details] File: var_log_messages
Similar problem has been detected: This comes up durring every reboot reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kwin_x11 -session 10d0737472000147507117900000022050023_1475152936_709928 crash_function: QGuiApplication::platformNativeInterface executable: /usr/bin/kwin_x11 global_pid: 2541 kernel: 4.7.4-100.fc23.x86_64 package: kwin-5.7.5-1.fc23 reason: kwin_x11 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.