Same problem here, Lenovo Slim 7i.
First error in the log is below, (could attach complete log due to post limit size).
Jul 09 17:25:51 clr-ce5a64d638a34fe68ebc4513fd59fc62 gdm[434]: Gdm: gdm_settings_get_value: assertion 'settings->backends != NULL' failed
worked for me, thanks ! ( +/- 20 minutes to update to 39590)
Jul 09 17:25:52 clr-ce5a64d638a34fe68ebc4513fd59fc62 systemd-coredump[607]: Process 562 (gnome-shell) of user 311 dumped core.
Stack trace of thread 604:
#0 0x000055fa41e9ce10 xkb_state_led_index_is_active (libxkbcommon.so.0 + 0x20e10)
#1 0x000055fa45820b59 meta_seat_impl_sync_leds_in_impl (libmutter-12.so.0 + 0x1a8b59)
#2 0x000055fa45827ab5 evdev_add_device (libmutter-12.so.0 + 0x1afab5)
#3 0x000055fa45829d96 dispatch_libinput (libmutter-12.so.0 + 0x1b1d96)
#4 0x000055fa45d54f4e g_main_dispatch (libglib-2.0.so.0 + 0x8cf4e)
#5 0x000055fa45deeef5 g_main_context_iterate.isra.0 (libglib-2.0.so.0 + 0x126ef5)
#6 0x000055fa45d5578f g_main_loop_run (libglib-2.0.so.0 + 0x8d78f)
#7 0x000055fa4582a197 input_thread (libmutter-12.so.0 + 0x1b2197)
#8 0x000055fa45d97548 g_thread_proxy (libglib-2.0.so.0 + 0xcf548)
#9 0x000055fa45490c1a start_thread (libc.so.6 + 0x90c1a)
#10 0x000055fa4551eaf0 __clone (libc.so.6 + 0x11eaf0)
...core dump continues for longer then i can paste but ends with...
Jul 09 17:25:52 clr-ce5a64d638a34fe68ebc4513fd59fc62 gnome-session-binary[552]: Unrecoverable failure in required component org.gnome.Shell.desktop
Correct me if I am wrong, but it appears that @Brian_Francisco was unlucky to pull an install that did not correctly write to bios to point to the install disk that was selected for Clear Linux install. Then @Aqua1ung suggested going to a known working iso albeit old, and was able to install then update that install to the latest Clear Linux release. Something appears very wrong/incompatible with the Clear Linux installer. Looking at the last message on @Brian_Francisco picture of his boot screen, it was referring to a Bluetooth device.
The older ISO would NOT boot for me. I honestly canāt remember the error, but booting failed.
Use Ventoy, and boot with the Grub2 option.
I didnāt boot in grub2 mode. Had a brain fart. Downloading 37860 again. Deleted the previous one when it blew up. Is it possible to update from the newest iso file instead of downloading updates from the server? Like opensuse does?
Maybe, but I donāt know how to do that. At any rate, make sure you disable autoupdate when installing 37860: itās very important you do that, otherwise itāll surreptitiously update to the latest, and you wonāt be able to boot.
Solved
I had to install 37860 without network.
reboot
disable auto update, log into my network and then update to newest build (released 7/14) CLI.
It worked, surprisingly.
Iām not a huge fan of gnome, but itās in a partition on my laptop just for testing.
Weirdly enough it made its own 150M boot partition, didnāt use the one I already had with 3 other distroaā¦
I donāt know how you installed without network, but, like I said, you should have disabled automatic updates during the initial ISO installation, i.e. as an installation parameter. Anyway, glad it worked out. Now you can safely do a manual update, or enable automatic updates if you are so inclined.
I didnāt log in to my Wi-Fi, and I didnāt pick anything in the advanced tab.
I try to see what the distro will do that has auto-updates installed, especially since Iām only testing right now. I donāt game so I try to stay away from Nvidia @ all costs.
I donāt setup auto updates on my daily drivers ever. Thatās asking for trouble on most rolling distros.
My next attempt is putting something on my white iMac.
Hereās a nicer fix from @mikma, also explained here.
I can confirm this works, I am using lg gram 2023 16"
Added some of my own testing notes to the GitHub issue