https://bugs.kde.org/show_bug.cgi?id=508177
--- Comment #3 from Bruno Santos <[email protected]> --- The crash solved itself with the current updates, but this kind of crash and unusable system happened a few times in the last year. I think since some bug in QT 6.8, which was also mitigated with an environment variable. Is there any way to make sddm and plasmashell more robust to a small change in a QT lib? I was able to fix my system UI until an update solved the crash, but other users ended up reinstalling the whole system. I understand Testing is for... testing! But if you want to help test, and report bugs, some kind of failsafe system when QT apps are not running correctly could be interesting to have so a user could at least make updates. If sddm crashes on boot, a very simple UI (something that could work even if some QT lib is creating crashes or missing due to some packaging issue) is started that allows to apply updates. "It seems your graphical environment isn't working correctly. Do you want to try to update your system to see if a fix has been released? Login with your user and check for updates: User: Password: etc etc". It could allow for reporting a crash on boot too. If systemd keeps track of crashes, it could use this feature to allow to submit a bug report of the boot process crash. One can always use the console, nmcli up the network connection and use apt, but not every user knows how to do this, but still be interested in using Testing to contribute to test the graphical system and apps. -- You are receiving this mail because: You are watching all bug changes.
