Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-21-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: I clicked on the KDE Application Launcher widget icon on the Task Manager widget. Then Brave crashed and Plasma crashed. I was playing a YouTube video during the episode. I had several applications running and none of them were affected. I do not know if any applications besides Plasma or Brave were affected. It's possible that Brave was updated and I didn't get around to restarting it ('m notorious for that). Also, I killed kscreensaver_g when it locked up while trying to unlock my computer. I do not know if this is related. I do not know if any other bugs are like this, but I did look through the list. Some bugs were similar but I decided to create a new bug because my course of action just before Plasma crashed is unique. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #4 0x00007f1a728d8598 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x00007f1a77f8254d in QOpenGLContext::create() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 [...] #10 0x00007f1a776a8134 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #11 0x00007f1a777287dc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 Reported using DrKonqi
Created attachment 170880 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
The backtrace suggests it's possible you updated the system without rebooting afterwards. If not, then be advised that Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding!