SUMMARY Plasma shell crashed on boot STEPS TO REPRODUCE 1. Start computer 2. Login to Plasma via sddm OBSERVED RESULT Plasmashell crashed, but recovered. EXPECTED RESULT Plasmashell not crashing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kalpa Desktop (openSUSE) Linux 6.13.7-1-default, Wayland KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION Nate asked me to file a bug, so I filed a bug. Backtrace: (gdb) bt #0 __GI_abort () at abort.c:91 #1 0x00007fb6ce0311a0 in ?? () #2 0x0000003000000018 in ?? () #3 0x00007fb6ddbff8a0 in ?? () #4 0x00007fb6ddbff7e0 in ?? () #5 0x8f12626ef5c15600 in ?? () #6 0x0000000100000005 in ?? () #7 0x00007fb6ddbff7a0 in ?? () #8 0x0000000200000002 in ?? () #9 0x0000559c73f60720 in ?? () #10 0x00007fb6ddbff810 in ?? () #11 0x0000559c72af12c0 in ?? () #12 0x0000000000000000 in ?? ()
Thank you for the bug report! Unfortunately I the backtrace is incomplete and missing debug symbols for all lines that we need to figure out exactly what's going wrong. 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!
Yes, I'm aware this backtrace isn't useful, I'm working on getting one that is.
Here's the best I've been able to get, after installing about 200 debuginfo packages. (gdb) bt #0 __GI_abort () at abort.c:91 #1 0x00007fb6ce0311a0 in ??? () at /lib64/libgallium-25.0.2.so #2 0x00007fb6ce034ec4 in ??? () at /lib64/libgallium-25.0.2.so #3 0x00007fb6cdb575d9 in ??? () at /lib64/libgallium-25.0.2.so #4 0x00007fb6cdb8b837 in ??? () at /lib64/libgallium-25.0.2.so #5 0x00007fb6e4099546 in start_thread (arg=<optimized out>) at pthread_create.c:448 #6 0x00007fb6e411d94c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thanks! Looks like it's crashing in your graphics drivers, unfortunately. If you can get debug symbols for Mesa, I'd recommend reporting a bug. See the instructions at https://docs.mesa3d.org/bugs.html