[Fedora-i18n-bugs] [Bug 1689037] anaconda sometimes crashes with a signal 11 quite early in install process

https://bugzilla.redhat.com/show_bug.cgi?id=1689037

--- Comment #55 from Massimiliano  ---
I don't know if it's related to this issue, but I had a similar problem running
anaconda in my CentOS remix:

Starting installer, one moment...
anaconda 33.16.3.26-1.el8 for CentOS Stream 8 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * when reporting a bug add logs from /tmp as separate text/plain attachments
12:09:07 Not asking for VNC because we don't have a network
No protocol specified
No protocol specified
Anaconda received signal 11!.
/usr/lib64/python3.6/site-packages/pyanaconda/_isys.so(+0x12a6)[0x7fed003712a6]
/lib64/libpthread.so.0(+0x12b20)[0x7fed1cd09b20]
/lib64/libgtk-3.so.0(+0x2f7b9d)[0x7fece46f4b9d]
New LWP 6738]
...
...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007fed1cd094a2 in waitpid () from /lib64/libpthread.so.0
Saved corefile /tmp/anaconda.core.6730
[Inferior 1 (process 6730) detached]

In my case, using a GNOME Xorg session (instead of Wayland) solves the problem.
Using a Wayland session makes Anaconda always fail. KDE remix, which uses Xorg,
has no issue.
Hope this helps.