On cold start of the system or sometimes when rebooting startplasma-wayland crashes when opening session from sddm. I can see kdesplash running and before it ends, I'm thrown back to sddm-greeter on tty1 . Then if i try to log again the screen freezes because in fact the session is not closed, and I must reboot with Ctrl-Alt-Supp. If I do Ctrl-Alt-F2, then I can find my session running with no startplasma process on tty2, If I do a " ps -ea | grep way" I only have 2 kwin_wayland, and Xwayland. then if I close the session with menu exit , and go back to tty1 with Ctrl-Alt-F1, I can login again and my session is opened on tty2 as usual. I created annother user and the pb occurs randomly at the same, so it's not user linked. SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Mageia 10 (Cauldron) KDE Plasma Version:6.9.90 KDE Frameworks Version: 6.10 Qt Version: 6.8.1 ADDITIONAL INFORMATION
Created attachment 177639 [details] screen shot of session after startplasma-wayland coredump
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
Potentially 498861
(In reply to David Redondo from comment #3) > Potentially 498861 Hi, Thank you for your answer, if the pb occurs again I will send you a backtrace, but since I upgraded my system from kernel-6.6.74 to kernel-6.12.11 the pb did not reproduced anymore. I tested it more than 10 times with cold start and reboot from session an I only had one Xwayland failure with no effect on the boot nor the applications that uses it ( applets from Mageia distro). So maybe you can close the subject .