Description of problem: crash after enabling the second screen of my system using kde system settings. Version-Release number of selected component: kf5-kwallet-5.80.0-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.kde.kwalletd5.slice/dbus-:1.2-org.kde.kwalletd5 cmdline: /usr/bin/kwalletd5 crash_function: QtWayland::wl_output::handle_geometry executable: /usr/bin/kwalletd5 journald_cursor: s=83c0a881b8a8407b9098064493e298de;i=4431;b=12069deae63c4f1d834a8e95b4498553;m=affe02e5;t=5bf0d63ab46fe;x=3f294b4aabe9a90e kernel: 5.11.11-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QtWayland::wl_output::handle_geometry at /usr/src/debug/qt5-qtwayland-5.15.2-4.fc34.x86_64/src/client/qwayland-wayland.cpp:2207 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:525 #3 wl_closure_invoke at ../src/connection.c:1018 #4 dispatch_event at ../src/wayland-client.c:1452 #5 dispatch_queue at ../src/wayland-client.c:1598 #6 wl_display_dispatch_queue_pending at ../src/wayland-client.c:1840 #7 QtWaylandClient::QWaylandDisplay::flushRequests at /usr/src/debug/qt5-qtwayland-5.15.2-4.fc34.x86_64/src/client/qwaylanddisplay.cpp:221 #8 doActivate<false> at kernel/qobject.cpp:3898 #9 QMetaObject::activate at kernel/qobject.cpp:3946
Created attachment 1768770 [details] File: backtrace
Created attachment 1768771 [details] File: core_backtrace
Created attachment 1768772 [details] File: cpuinfo
Created attachment 1768773 [details] File: dso_list
Created attachment 1768774 [details] File: environ
Created attachment 1768775 [details] File: exploitable
Created attachment 1768776 [details] File: limits
Created attachment 1768777 [details] File: maps
Created attachment 1768778 [details] File: mountinfo
Created attachment 1768779 [details] File: open_fds
Created attachment 1768780 [details] File: proc_pid_status
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.