Created attachment 139908 [details] backtrace report SUMMARY: Ksplashqm will randomly crash before login credential are able to be entered on fedora 34 KDE spin using Wayland. Usually clicking on restart application will fix it, however this last time it failed to restart. Claims segmentation fault (11). no KDE add-ons enabled, no third party apps installed, happening on fresh clean install. STEPS TO REPRODUCE 1. restart computer or booting computer after a complete shutdown 2. wait for splash screen to go to login credentials OBSERVED RESULT notice of ksplashqm having segmentation fault, option to restart, cancel or report bug. click on bug report and notified that there is no address to report bug, availability to create backtrace report EXPECTED RESULT loading login screen to login to system. SOFTWARE/OS VERSIONS: Operating System: Fedora 34 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × AMD E-300 APU with Radeon(tm) HD Graphics Memory: 7.4 GiB of RAM Graphics Processor: AMD PALM ADDITIONAL INFORMATION backtrace attached
C
Created attachment 139996 [details] 2021-07-11 backtrace Backtrace for current crash of ksplashqm after update restart.
Proooooooooobably a Mesa issue that I would hope has been fixed by now. Can we ask you to please check if this is still an issue with Plasma 5.27 and the latest Mesa version? Thanks!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!