SUMMARY plasmashell crashes when hitting both mouse keys in rapid succession on a panel STEPS TO REPRODUCE Click and release both the left and the right mouse buttons rapidly when hovering over a Task Manager attached to a panel. OBSERVED RESULT The shell crashes and restarts EXPECTED RESULT The shell continues functioning SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT ADDITIONAL INFORMATION Backtrace: #0 0x00007ffff69514a2 in ??? () at /usr/lib/libQt6Quick.so.6 #1 0x00007ffff6b4cb6c in QQuickDeliveryAgentPrivate::onGrabChanged(QObject*, QPointingDevice::GrabTransition, QPointerEvent const*, QEventPoint const&) () at /usr/lib/libQt6Quick.so.6 #2 0x00007ffff53a3457 in ??? () at /usr/lib/libQt6Core.so.6 #3 0x00007ffff59bf5e4 in QPointingDevicePrivate::setExclusiveGrabber(QPointerEvent const*, QEventPoint const&, QObject*) () at /usr/lib/libQt6Gui.so.6 #4 0x00007ffff6b4b214 in QQuickDeliveryAgentPrivate::handleWindowDeactivate(QQuickWindow*) () at /usr/lib/libQt6Quick.so.6 #5 0x00007ffff53a3457 in ??? () at /usr/lib/libQt6Core.so.6 #6 0x00007ffff598386c in QGuiApplicationPrivate::setApplicationState(Qt::ApplicationState, bool) () at /usr/lib/libQt6Gui.so.6 #7 0x00007ffff597a7a2 in QGuiApplicationPrivate::processFocusWindowEvent(QWindowSystemInterfacePrivate::FocusWindowEvent*) () at /usr/lib/libQt6Gui.so.6 #8 0x00007ffff59e7d24 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Gui.so.6 #9 0x00007ffff5e05734 in ??? () at /usr/lib/libQt6Gui.so.6 #10 0x00007ffff3eb9559 in ??? () at /usr/lib/libglib-2.0.so.0 #11 0x00007ffff3f1c157 in ??? () at /usr/lib/libglib-2.0.so.0 #12 0x00007ffff3eb8a55 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #13 0x00007ffff55a985d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #14 0x00007ffff5350106 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #15 0x00007ffff534a27d in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #16 0x000055555557c15f in ??? () #17 0x00007ffff4c34e08 in ??? () at /usr/lib/libc.so.6 #18 0x00007ffff4c34ecc in __libc_start_main () at /usr/lib/libc.so.6 --Type <RET> for more, q to quit, c to continue without paging-- #19 0x000055555557c675 in ??? ()
Looks like it's all in Qt. :/
Thank you for the bug report. I'm not able to reproduce this on git-master. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #0 0x00007ffff69514a2 in ??? () at /usr/lib/libQt6Quick.so.6 #2 0x00007ffff53a3457 in ??? () at /usr/lib/libQt6Core.so.6 #9 0x00007ffff5e05734 in ??? () at /usr/lib/libQt6Gui.so.6 Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Actually in this case I'm not sure having symbols for those frames would help, since the whole backtrace is clearly in Qt with no KDE code implicated. This either needs to be marked as a duplicate of another open or fixed bug report with the same backtrace, or else investigated by a developer who can figure out what's going on.
It works now, sorry for the noise, forgot to close this. Feel free to reopen if something is wrong though.