Application: plasmashell (6.3.2) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.11.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux trixie/sid DrKonqi: 6.3.2 [CoredumpBackend] -- Information about the crash: Travaillant depuis mon ordinateur portable, j'ai branché un 2e écran et, au moment d'appuyer sur le bouton d'allumage de l'écran, le gestionnaire de bureau plasma a planté, pour se redémarrer de manière automatisée. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x00007f89b762dd54 in QWindow::screen() const () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #6 0x00007f89b761b185 in QPlatformWindow::screen() const () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #7 0x00007f89b7ea3739 in QtWaylandClient::QWaylandWindow::calculateScreenFromSurfaceEvents() const () at /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6 #8 0x00007f89b7ea82a6 in QtWaylandClient::QWaylandWindow::handleScreensChanged() () at /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6 #9 0x00007f89b6fe4443 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6 Reported using DrKonqi
Created attachment 179587 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Working from my laptop, I plugged in a 2nd screen and, when I pressed the screen power button, the plasma desktop manager crashed, only to restart automatically.
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: #9 0x00007f89b6fe4443 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.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!
The backtrace as it is looks similar, but not identical to bug 499383