Application: plasmashell (5.25.4)

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.18.16-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 36 (Thirty Six)"
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
Currently I have 4 monitors connected to my system, 3 at my desk and one located a distance away. They are set up such that when my right-most monitor is turned on, the three on my desk are enabled while the remote monitor is disabled and vice-versa. I am currently using X11 rather than Wayland despite using Fedora36 as any attempts to use wayland result in a much worse crash. To reproduce the crash all I need to do is lock the computer and leave it for long enough for the screens to go into sleep mode. Upon attempting to log in I will rarely be able to log in successfully, but more often than not I am presented with a button that says "
unlock" but does nothing when pressed. To get logged in I then need to manually turn off the right-most screen and then turn it on again, which allows me to attempt to log in again on a different monitor, however this time it will let me in. Whether or not I log in on the first time I will see a notification from drkonqi that plasmashell has crashed, but the vast majority of the time drkonqi closes itself before I can save any information and fails to save any reference of the crash. It appears as though drkonqi closing coincides with plasmashell relaunching, but with this most recent crash drkonqi did not close. If I attempt to use wayland the system becomes unstable and I must switch to a terminal session and forcefully close any running programs on the session that has frozen before rebooting the system. All of my monitors are from different manufactureres, with my desk screens being manufactured by Dell, acer, and samsug, in order, left to right, while my leftmost screen is rotated 90 degrees to the left. The screens also have different resolutions, from left to right being 1080, 1440, and 2160. I am currently using an AMD Radeon VII as a GPU and have the 3 desktop monitors connected via display port. I attempted to ensure that all relevant debug symbols were installed when generating the trace, but still received a warning that some were missing, but I would be happy to provide any other information if necessary.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f66a80e8bd3 in QtPrivate::QFunctorSlotObject<ImageColors::update()::{lambda()#1}::operator()() const::{lambda()#2}, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () at /usr/lib64/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so
#5  0x00007f66d6a258c6 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#6  0x00007f66d683c155 in QFutureWatcherBase::event(QEvent*) () at /lib64/libQt5Core.so.5
#7  0x00007f66d76b2d22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#8  0x00007f66d69f2228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#9  0x00007f66d69f5594 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#10 0x00007f66d6a43467 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#11 0x00007f66d4d7bfaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#12 0x00007f66d4dd12c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#13 0x00007f66d4d79940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#14 0x00007f66d6a42f5a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#15 0x00007f66d69f0c7a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#16 0x00007f66d69f8d42 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#17 0x00005588a795b165 in main ()
[Inferior 1 (process 371019) detached]

Reported using DrKonqi