Description of problem: Problem occours after a seemingly random amount of time from playing a (LEGALY AQUIRED) ROM on dolphin emulator. Not sure of any specifics. Version-Release number of selected component: kwin-wayland-5.27.1-2.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cmdline: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_yhWZnH --xwayland crash_function: std::default_delete<KWin::EffectWindowImpl>::operator() dso_list: /usr/bin/kwin_wayland kwin-wayland-5.27.1-2.fc37.x86_64 (Fedora Project) 1677344741 executable: /usr/bin/kwin_wayland journald_cursor: s=2a01460f6e7a46d2bc3fbe80a6ff24bb;i=58bc;b=bc17b345f53f4992b61351da01e1e47f;m=18d986341;t=5f58b6aad4e5d;x=74f8c099ce4e55e9 kernel: 6.1.13-200.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 std::default_delete<KWin::EffectWindowImpl>::operator() at /usr/include/c++/12/bits/unique_ptr.h:89 #1 std::__uniq_ptr_impl<KWin::EffectWindowImpl, std::default_delete<KWin::EffectWindowImpl> >::reset at /usr/include/c++/12/bits/unique_ptr.h:203 #2 std::unique_ptr<KWin::EffectWindowImpl, std::default_delete<KWin::EffectWindowImpl> >::reset at /usr/include/c++/12/bits/unique_ptr.h:501 #3 KWin::Window::finishCompositing at /usr/src/debug/kwin-5.27.1-2.fc37.x86_64/src/window.cpp:370 #4 KWin::X11Window::finishCompositing at /usr/src/debug/kwin-5.27.1-2.fc37.x86_64/src/x11window.cpp:1491 #5 KWin::Compositor::stop at /usr/src/debug/kwin-5.27.1-2.fc37.x86_64/src/composite.cpp:523 #7 KWin::Compositor::reinitialize at /usr/src/debug/kwin-5.27.1-2.fc37.x86_64/src/composite.cpp:628 #8 QtPrivate::QSlotObjectBase::call at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate<false> at kernel/qobject.cpp:3923 #10 QMetaObject::activate at kernel/qobject.cpp:3983
Created attachment 1946366 [details] File: backtrace
Created attachment 1946367 [details] File: cgroup
Created attachment 1946368 [details] File: core_backtrace
Created attachment 1946369 [details] File: cpuinfo
Created attachment 1946370 [details] File: environ
Created attachment 1946371 [details] File: exploitable
Created attachment 1946372 [details] File: limits
Created attachment 1946373 [details] File: maps
Created attachment 1946374 [details] File: mountinfo
Created attachment 1946375 [details] File: open_fds
Created attachment 1946376 [details] File: proc_pid_status
Created attachment 1946377 [details] File: var_log_messages
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.