Torxed
commented
4 years ago There's support for this in the code via the log function now, but there's no error log function currently. This is mainly a limitation in archinstall currently. So we'll need to implement a proper log-flow there, before we can pick up errors.
Once that is done, I suggest a huge popup that covers the screen with a blurred background, to make sure the user can not accidentally click on any subsequent steps until the error dialogue is confirmed and closed.
Things can crash in the background and the user won't know about it. Adding a notification message early in the catch logic would at least send something to the user and perhaps avoid "spinning progress of death".