Unfortunately, it looks like we still don't have a full stack trace for this. Since the problem is not widely reproducible, we are unlikely to be able to debug this without a stack trace.
Can you install the -dbgsym packages in the live environment before starting the installer, and generate a full backtrace locally?
Unfortunately, it looks like we still don't have a full stack trace for this. Since the problem is not widely reproducible, we are unlikely to be able to debug this without a stack trace.
Can you install the -dbgsym packages in the live environment before starting the installer, and generate a full backtrace locally?