Description of problem: Clean install Fedora-Workstation-Live-x86_64-32-20200221.n.0.iso and reboot, g-i-s is crashing soon after the desktop first appears. Version-Release number of selected component: gnome-initial-setup-3.35.91-1.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-985.slice/user/gnome-initial-setup.service cmdline: /usr/libexec/gnome-initial-setup crash_function: __strcmp_sse2_unaligned executable: /usr/libexec/gnome-initial-setup journald_cursor: s=6b00d758353c4979916352cd79f2759a;i=854;b=2bb28b02a49c43dead53cb6577634fe7;m=1310e2a;t=59f35c069b14e;x=683e407790dc00a5 kernel: 5.6.0-0.rc2.git0.1.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 985 Truncated backtrace: Thread no. 1 (8 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:32 #1 set_input at ../gnome-initial-setup/pages/keyboard/cc-input-chooser.c:528 #2 cc_input_chooser_set_input at ../gnome-initial-setup/pages/keyboard/cc-input-chooser.c:897 #3 preselect_input_source at ../gnome-initial-setup/pages/keyboard/gis-keyboard-page.c:379 #4 localed_proxy_ready at ../gnome-initial-setup/pages/keyboard/gis-keyboard-page.c:422 #5 g_task_return_now at ../gio/gtask.c:1214 #6 g_task_return at ../gio/gtask.c:1283 #8 g_task_return_boolean at ../gio/gtask.c:1803
Created attachment 1665141 [details] File: backtrace
Created attachment 1665142 [details] File: core_backtrace
Created attachment 1665143 [details] File: cpuinfo
Created attachment 1665144 [details] File: dso_list
Created attachment 1665145 [details] File: environ
Created attachment 1665146 [details] File: exploitable
Created attachment 1665147 [details] File: limits
Created attachment 1665148 [details] File: maps
Created attachment 1665149 [details] File: mountinfo
Created attachment 1665150 [details] File: open_fds
Created attachment 1665151 [details] File: proc_pid_status
The installation failed on bug 1804953, but since only bootloader stuff was broken, I fixed it manually. Since it's not a strictly clean installation, I won't yet propose it as a blocker until it's reproduced from a successful install.
It was booted with enforcing=0 at the time of the crash.
Created attachment 1665152 [details] journal
BIOS qemu-kvm, does not crash. So it may be a transient crash. Doubt the bootloader stuff has anything to do with this.
Tried rebooting ~10 times, and g-i-s came up each time, no crash. ¯\_(ツ)_/¯
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.