SUMMARY When I try to switch user, my screen becomes black, and only the mouse cursor is visible, but doesnt move, system is unresponsive, not even going to tty via ctrl + alt + f1,2,3,4 etc works. Only hard reset works, by pressing the power button, which is destructive for the disks and my datas! STEPS TO REPRODUCE 1. Press on start menu 2. select switch user 3. observe the freeze / crash OBSERVED RESULT system frozen EXPECTED RESULT it shouldn't freeze the system... SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.15.10-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 16 GiB of RAM (15.6 GiB usable) Graphics Processor: NVIDIA GeForce GTX 1050 Ti Manufacturer: MSI Product Name: MS-7972 System Version: 2.0
Thanks for the bug report. Since the screen goes black, it sounds like either plasmashell or kwin may have been what crashed. As the message at the top of the summary says, 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 ?
(In reply to TraceyC from comment #1) > Thanks for the bug report. Since the screen goes black, it sounds like > either plasmashell or kwin may have been what crashed. > > As the message at the top of the summary says, 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 ? yeah the problem is, that I just made it crash again, and I don't get any coredump - at all :/ not sure how is a bug fixable without a coredump, but this is so odd, that not even a trace is left by this, that its beyond me.
(In reply to Sylens from comment #2) > yeah the problem is, that I just made it crash again, and I don't get any > coredump - at all :/ not sure how is a bug fixable without a coredump, but > this is so odd, that not even a trace is left by this, that its beyond me. Thanks for trying. Things may not be crashing, but freezing. Can you check kwin's logs when the hard freeze occurs? journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt Also, is there any chance that you could retrieve kwin's backtrace when the hard freeze occurs? You would need to ssh from another computer and attach a debugger to kwin process, e.g. sudo gdb -p $(pidof kwin_wayland) then type bt and paste the output here. Thanks.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to TraceyC from comment #3) > (In reply to Sylens from comment #2) > > yeah the problem is, that I just made it crash again, and I don't get any > > coredump - at all :/ not sure how is a bug fixable without a coredump, but > > this is so odd, that not even a trace is left by this, that its beyond me. > > Thanks for trying. Things may not be crashing, but freezing. > > Can you check kwin's logs when the hard freeze occurs? > > journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt > > Also, is there any chance that you could retrieve kwin's backtrace when the > hard freeze occurs? You would need to ssh from another computer and attach a > debugger to kwin process, e.g. > > sudo gdb -p $(pidof kwin_wayland) > > then type > > bt > > and paste the output here. Thanks. unfortunately none of those commands worked, it couldn't find any backtraces
Please run this journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt And then attach ~/log.txt to this report. Thanks.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.